Public bug reported: Binary package hint: linux-image-2.6.24-15-generic
After dist-upgrading from Gutsy i386 to Hardy beta, my encrypted-root system no longer boots. Instead it displays an error "cryptsetup: source device /dev/hda2 not found" I guessed (correctly) that the device paths for IDE were changed to /dev/sd?? and so re-worked my initramfs to point to /dev/sda2 instead. But now cryptsetup says source /dev/sda2 not found. Four or five minutes later I'll get a busybox shell and can see that /dev/sda is there, but apparently the HD device nodes are being created too late. This is not a LUKS setup, using plain dmcrypt instead. This arrangement worked fine under Gutsy. If I manually execute a 'cryptsetup create cr-root /dev/sda2 -v -c aes- cbc-essiv:sha256 -h sha1 -s 128' command in the busybox, then 'exit', the system will boot. Changing /etc/crypttab to use sda2 then re-building with 'update- initramfs -c -k $(uname -r)' has not helped. Another user is getting this error. See this thread for discussion: http://ubuntuforums.org/showthread.php?p=4624349 Here is my crypttab: # <target name> <source device> <key file> <options> cr-root /dev/sda2 none cipher=aes-cbc-essiv:sha256,hash=sha1,size=128 swap /dev/sda1 /dev/random swap,cipher=aes-cbc-essiv:sha256 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- cryptsetup: source device not found during boot https://bugs.launchpad.net/bugs/213279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
