[mythtv-users] LVM Problem -- Please Help

chris at cpr.homelinux.net chris at cpr.homelinux.net
Tue Aug 15 06:26:07 UTC 2006

On Mon, Aug 14, 2006 at 03:52:19PM -0700, Tom+Dale wrote:
> >> I was suspicious about the new drive because it was clicking loudly, so I
> >> shut down cleanly and disconnected it.

This can be caused by a lot of problems, not all of which are 
fatal.  Since it's a new drive you just added to your machine, the 
power supply has to be at least considered.  If the clicking sound 
is only once every 1 or 2 seconds then it could be caused by the 
drive power-cycling.  Try unplugging *all* of your other hard 
drives (so the machine won't try to boot) and see if the clicking 
goes away.  If so then you need to buy a bigger power supply.  
Another cause of clicking is a failure of the drive's controller 
card.  On my old Western Digital drives that usually resulted in a 
click rate of around 4Hz.  If the clicking is very spread out or 
doesn't start right away when the power is turned on then it could 
be a thermal issue.

> >> The system reports a missing physical volume of UUID ### and then reports
> >> an unknown physical volume with the same UUID.

I use mdadm instead of lvm, but the rules are probably similar: if 
you specify an actual device name for an array component then the 
array will not recognize that component if the device name is 
changed.  The trivial work-around in mdadm is to change the config 
file so that it searches for components using only the uuid.

> 1) Is the error about not finding /dev/sda a definitive reason as to why the
> other commands failed (pvcreate -u...  & vgcfgrestore -tn ...)?  It seems to me
> that the drive needed a successful pvcreate in order to be added to the volume
> group, but I confess that I don't remember precisely how things transpired.  So
> if linux doesn't see it right away, does that mean it's dead?

To answer the first part of that question: yes.  If Linux did not 
find a device at /dev/sda then almost any command that refers to 
/dev/hda will fail.  As for the last part: no.  Just because Linux 
didn't see the drive doesn't mean it's dead.  There are lots of 
reasons why Linux might not see a drive, ranging from BIOS settings 
to missing kernel modules.

> 2) If the drive was not dead, should linux have picked up the /dev/sda on boot
> once it was re-connected, despite my earlier mistake of booting once without it
> connected?

Yes.  Assuming the drive is in fact not dead and that you're still 
running the same kernel (with SATA support loaded) and the cables 
are all correct, then you should be able to see it mentioned in 
/var/log/messages as part of the boot messages.

More information about the mythtv-users mailing list