Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I've installed Debian (lenny) on a machine at home. It was set up during install to have a /boot partition, then the rest was encrypted, then had an LVM ontop of that, then all the other partitons inside LVM.

After install completed and on first boot it asked for password to un-encrypt(same password for both drives) then it showed an error which said LVM could not find a physical device with a particular UUID or something similar.

LVM install is over two HDs. One is 120GB and one 40GB. 120GB is Master on its IDE cable and this has /boot on it. 40GB is slave on the other IDE cable.

Is there anything that could be done to rescue this install? Or diagnose problem? It took ages to get installed due to time spent enrypting drives and I'd rather not go through that again. :(

Thanks.. Ian

share|improve this question
    
Is this still an issue? You can propablyskip the disk wipe the second time through. –  Zoredache Apr 22 '10 at 15:59

3 Answers 3

It was set up during install to have a /boot partition, then the rest was encrypted, then had an LVM ontop of that, then all the other partitons inside LVM.

The encryption should be on the LVM-partition level, not the hard drive's partition.

share|improve this answer

When the LVM tools start up, they look for a set of PVs (physical volumes) and the volume groups built out of them, and the logical volumes built inside the VGs.

If you've encrypted your whole 40GB drive (i.e. /dev/hdb1 is encrypted) the problem is most likely that the LVM is starting before the decryption happens - so it goes looking for the PV signature (the UUID it's complaining about), and doesn't find one, because at that point, /dev/hdb1 looks like random junk, not a PV.

Your best bet for rescuing the data would be to pass in your decryption key and then do a pvscan/vgchange -a y/lvchange -a y sequences, since the pvscan will work once the drives are accessible again.

In the future, as Avery notes, encrypt the logical volumes, not the physical drives!

share|improve this answer

when your creating a /boot participations it has to be ext3 or ext4 because in production it good for recovery !

share|improve this answer
    
/boot is ext3 so thats not it and it has nothing to do with the LVM error –  ianfuture Mar 31 '10 at 12:02
    
yes it is because it not loading grub your LVM –  Rajat Mar 31 '10 at 12:35
    
and you try out nothing ham in that !! –  Rajat Mar 31 '10 at 12:36
    
@ Rajat sorry i can't understand the point you are trying to make. do you have a more detailed answer? –  ianfuture Mar 31 '10 at 13:56

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.