hey again, On 25/02/2010 Jonas Meurer wrote: > On 05/11/2009 Max Vozeler wrote: > > We recently changed d-i to use UUID in crypttab entries, > > which is likely to be causing this problem. > > > > Jonas, do you think the initramfs script can be adapted to > > allow UUID or should partman-crypto go back to /dev/mapper > > for the root backing device for now? > > > > (No time to look deeper into it right now, sorry.) > > i take a deeper look now, and figued out what the real problem is here: > > in case that the setup is LUKS on LVM, the cryptroot initramfs script > needs to determine the volume group to start in order to make the > underlying logical volume available before unlocking it with cryptsetup. > > this is done by parsing the cryptsetup source device. for example the > source device "/dev/mapper/vg00-root" leads to volume group "vg00" being > activated. > > when the UUID is given instead, no information about the volume group > can be extracted. > > i don't know what the propper fix is yet. i might change the cryptroot > hook script to always transfer UUID to path for /conf/conf.d/cryptroot > in initramfs. but then i don't see a reason to use UUIDs in initramfs at > all. any other solution that i see now (e.g. to detect LUKS over LVM in > cryptroot hook and save the volume group name in /conf/conf.d/cryptroot) > would require intrusive changes to the cryptroot implementation.
i just tried to reproduce the bug, and failed. can you confirm, that this bug no longer applies? otherwise please give exact information about your system: /etc/fstab, /etc/crypttab, and from inside the initramfs: /conf/conf.d/cryptroot. greetings, jonas
signature.asc
Description: Digital signature
