You are not logged in.
Hey,
I got into serious problems after the latest update (this morning). The update included initscripts and filesystem. I changed /etc/crypttab according to the changes, merged rc.conf and rc.conf.pacnew (basically removed a lot of stuff from rc.conf), added the removed settings to the appropriate config files (e.g. hostname to /etc/hostname).
[edit]
My system setup:
/boot on /dev/sda1
/ on /dev/sda2
luks-encrypted /dev/sda3
/dev/cryptpool/varlv on /var
/dev/cryptpool/homelv on /home
The volume group exists, the logical volumes exist, I can mount them, everything works, except I can't boot because the volume group is not activated during boot.
[/edit]
I then rebooted, which failed because it didn't open the lvm group on my luks drive (which was decrypted). If I understood it right, up until today, the filesystems hook checked for luks devices, decrypted them and then activated the lvm group. I did have the lvm hook but it never did anything (no groups found). So I guess, now the filesystems hook doesn't activate the lvm groups anymore, which leads to boot failure.
So I tried something different: I added the encrypt hook before the lvm2 hook, so hooks are now: (base udev autodetect pata scsi sata usb usbinput encrypt lvm2 resume filesystems).
If I boot, it tells me /dev/sda2 is not a luks device, therefore decryption in the encrypt hook fails and the lvm2 hook doesn't activate any groups. The filesystems hook detects the luks device, asks me for a password but doesn't activate the lvm group.
My question: Is the encrypt hook for encrypted root only or do I have to use it no matter what partition is encrypted? So far it worked without the hook, but it's not working anymore.
If the answer is yes: How to I force filesystems to do a vgchange AFTER decrypting my luks device? the lvm2 hook of course can't find anything because the lvm is still encrypted at that moment.
Thanks for any hints
PS: Using the old rc.conf and crypttab didn't change anything, it's still not booting.
Last edited by morxa (2012-07-28 12:23:38)
Offline
You might encounter this bug.
Offline
thanks, that's indeed the bug I've encountered.
Offline
initscripts 2012.08.1-1 in testing works great that solved all my problems.
Thanks arch developers your the best!
Offline