LUKS and LVM sequence at boot and shutdown incorrect
My laptop hard drive configuration: sda1 - win7 sda2 - /boot sda3 - LVM on top of LUKS partition - (separate LVs for /, /home, and SWAP) sda5 - FAT32 for the most part everything seems to be working fine except the order of modules/components when Debian boots up. When I boot Debian, it first looks for the LVM VG and LV, and then the LUKS container. - I encrypted the PV, I thought the order should be the other way around. So when it boots, message on the screen says it failed to load the VG and the LVs and then gives me an option to enter my pass-phrase. Because I have LVM on top of LUKS I thought it would first open the LUKS container and then load the LVM container. I have the same problem when shutting down. It closes the LUKS container and then throws up an error saying it cannot find VG and LVs (or something similar). Of course it will not find hte VG once the LUKS container is closed. Not sure how this happened. Can anyone explain how to fix this. Thanks -- Kind regards, Yudi
Re: LUKS and LVM sequence at boot and shutdown incorrect
On Fri, Aug 19, 2011 at 10:50:12AM CEST, yudi v yudi@gmail.com said: My laptop hard drive configuration: sda1 - win7 sda2 - /boot sda3 - LVM on top of LUKS partition - (separate LVs for /, /home, and SWAP) sda5 - FAT32 for the most part everything seems to be working fine except the order of modules/components when Debian boots up. When I boot Debian, it first looks for the LVM VG and LV, and then the LUKS container. - I encrypted the PV, I thought the order should be the other way around. So when it boots, message on the screen says it failed to load the VG and the LVs and then gives me an option to enter my pass-phrase. Because I have LVM on top of LUKS I thought it would first open the LUKS container and then load the LVM container. I have the same problem when shutting down. It closes the LUKS container and then throws up an error saying it cannot find VG and LVs (or something similar). Of course it will not find hte VG once the LUKS container is closed. Not sure how this happened. Can anyone explain how to fix this. Did you try to use the early option in cryptsetup ? It make sthe luks part being done earlier at boot time (in the cryptdisks-early boot script). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110819085641.gj32...@rail.eu.org
Re: LUKS and LVM sequence at boot and shutdown incorrect
Did you try to use the early option in cryptsetup ? It make sthe luks part being done earlier at boot time (in the cryptdisks-early boot script). did not know that, thanks for pointing it out. I did not read anything about it in the installation documentation. I thought the installer will be smart enough to figure out that it needs to open the LUKS container to get to the LVs. I will definitely read up on this issue. -- Kind regards, Yudi
Re: LUKS and LVM sequence at boot and shutdown incorrect
On Fri, Aug 19, 2011 at 11:23:42AM CEST, yudi v yudi@gmail.com said: Did you try to use the early option in cryptsetup ? It make sthe luks part being done earlier at boot time (in the cryptdisks-early boot script). did not know that, thanks for pointing it out. I did not read anything about it in the installation documentation. I thought the installer will be smart enough to figure out that it needs to open the LUKS container to get to the LVs. I will definitely read up on this issue. Thinking about it there surely is something to do about the initrd.img, which is in use when you boot (because / is not yet mounted). I do not know much about it, it surely is worth reading about. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110819101857.gk32...@rail.eu.org
Re: LUKS and LVM sequence at boot and shutdown incorrect
Thinking about it there surely is something to do about the initrd.img, I thought so too. looks like I need to build a new initrd.img. -- Kind regards, Yudi
