<br><br><b><i>chris@cpr.homelinux.net</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On Mon, Aug 14, 2006 at 03:52:19PM -0700, Tom+Dale wrote:<br>> >> I was suspicious about the new drive because it was clicking loudly, so I<br>> >> shut down cleanly and disconnected it.<br><br>This can be caused by a lot of problems, not all of which are <br>fatal. Since it's a new drive you just added to your machine, the <br>power supply has to be at least considered. If the clicking sound <br>is only once every 1 or 2 seconds then it could be caused by the <br>drive power-cycling. Try unplugging *all* of your other hard <br>drives (so the machine won't try to boot) and see if the clicking <br>goes away. If so then you need to buy a bigger power supply. <br>Another cause of clicking is a failure of the drive's controller <br>card. On my old Western Digital drives that usually resulted
in a <br>click rate of around 4Hz. If the clicking is very spread out or <br>doesn't start right away when the power is turned on then it could <br>be a thermal issue.<br><br>> >> The system reports a missing physical volume of UUID ### and then reports<br>> >> an unknown physical volume with the same UUID.<br><br>I use mdadm instead of lvm, but the rules are probably similar: if <br>you specify an actual device name for an array component then the <br>array will not recognize that component if the device name is <br>changed. The trivial work-around in mdadm is to change the config <br>file so that it searches for components using only the uuid.<br><br>> 1) Is the error about not finding /dev/sda a definitive reason as to why the<br>> other commands failed (pvcreate -u... & vgcfgrestore -tn ...)? It seems to me<br>> that the drive needed a successful pvcreate in order to be added to the volume<br>> group, but I confess that I don't
remember precisely how things transpired. So<br>> if linux doesn't see it right away, does that mean it's dead?<br><br>To answer the first part of that question: yes. If Linux did not <br>find a device at /dev/sda then almost any command that refers to <br>/dev/hda will fail. As for the last part: no. Just because Linux <br>didn't see the drive doesn't mean it's dead. There are lots of <br>reasons why Linux might not see a drive, ranging from BIOS settings <br>to missing kernel modules.<br><br>> 2) If the drive was not dead, should linux have picked up the /dev/sda on boot<br>> once it was re-connected, despite my earlier mistake of booting once without it<br>> connected?<br><br>Yes. Assuming the drive is in fact not dead and that you're still <br>running the same kernel (with SATA support loaded) and the cables <br>are all correct, then you should be able to see it mentioned in <br>/var/log/messages as part of the boot
messages.<br><br></blockquote>Thanks for the help, Chris. I had not mentioned earlier that this is a new motherboard and power supply, too. I have checked the BIOS at boot, and learned that the SATA drive does not show up unless I probe for it. I know that is different than when it was installed the very first time. Also, the probe returns what must be a guess, because it is incorrectly identifying the drive. When it was installed on Friday, the system recognized it correctly with the drive model number and size whereas now it comes up with something else entirely. Looking at the boot messages, I see that the _volume_ reports a failure to mount, but I don't see the drive mentioned.<br>>><br>>> 3) If the drive is okay, and /dev/sda were being recognized, how would I go<br>>> about re-linking the UUID to the physical volume?<br>>><br>>> 4) Can an identical replacement drive be put in and given the UUID in
order<br>>> to recover data from the rest of the logical volume?<br>>><br>>><br>I have made arrangements to RMA this drive (NewEgg really has excellent customer service). So my other questions weigh heavily on my mind (i.e., will I lose ~200GB of data from the still functioning drives that were part of this LVM? Or will I be able to put in an identical, functioning replacement and give it a UUID that the LVM likes in order to access my original drives?<br><br>Thanks again<br><p> 
<hr size=1>Yahoo! Messenger with Voice. <a href="http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com">Make PC-to-Phone Calls</a> to the US (and 30+ countries) for 2¢/min or less.