hello steve, On 25/10/2009 steve wrote: > After recent upgrade kernel version 2.6.30-2 fails to boot with this message: > > Enter passphrase for /dev/hda3: <correctr passwd entered> > device-mapper: ioctl: unable to remove open device temporary-cryptsetup-677 > device-mapper: remove ioctl failed: Device or resource busy > Key slot 0 unlocked. > ...[several other messages which I didn't capture] ... > and eventually I end up at the busybox prompt. > > Two other kernels, 2.6.30-1 and 2.6.26-2-686 still boot OK. > I'm not sure this is a cryptsetup error but it seems the only relevant > package that was recently upgraded. > > /dev/mapper/hda3_crypt exists and looks correct after the failure.
unfortunately i'm unable to reproduce the bug. i tested cryptsetup 2:1.1.0~rc2-1 and linux-image-2.6.31-1-amd64 2.6.31-1 on more than ten different setups (luks on lvm, lvm on luks, luks on raid, luks on lvm on raid, ...) and didn't see any problems. maybe the issue is related to the 686 arch kernel, but i doubt that it has any different configuration than the amd64 one. does the issue happen all the time or only sometimes? the 'remove ioctl failed: Device or resource busy' warning is a known issue and can be ignored, but the message about temporary-cryptsetup-677 device shouldn't occur. 'key slot 0 unlocked.' indicated that the device has been unlocked successfully in the end, thus i don't understand why the boot breaks at all. it would be great if you could provide more information, in particular the messages between 'key slot 0 unlocked' and busybox emergency shell. greetings, jonas
signature.asc
Description: Digital signature
