Activity log for bug #1072180

Date Who What changed Old value New value Message
2012-10-27 19:24:13 GOo bug added bug
2012-10-27 19:24:13 GOo attachment added initramfs debug https://bugs.launchpad.net/bugs/1072180/+attachment/3415759/+files/initramfs.debug2
2012-10-27 19:32:47 GOo description After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. Workaround: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #/etc/crypttab ubuntu-root_crypt UUID=0b1f585c-5dee-43a5-9106-b3bbd8a173b5 /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/ubuntu-root luks,keyscript=passdev,loud ubuntu-swap_crypt /dev/mapper/ubuntu-swap /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,swap data-var_crypt UUID=fb8c9458-bc86-4346-aca3-e845993f326f /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-var luks,keyscript=passdev data-homes_crypt UUID=172d9ce6-7aa6-4a2b-8e83-f7ea59b65fea /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-homes luks,keyscript=passdev data-media_crypt UUID=1739a5b3-8a38-4fac-9e73-df0181e62b29 /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-media luks,keyscript=passdev #/etc/fstab proc /proc proc nodev,noexec,nosuid 0 0 /dev/mapper/ubuntu-root_crypt / ext4 relatime,commit=30,errors=remount-ro 0 1 UUID=e6cb942e-1f09-4564-838c-280af283042e /mnt/keydev ext2 noauto,ro 0 0 UUID=dd4525cd-8bc4-4ba8-8a14-f743cf8e66f4 /boot ext4 defaults 0 2 /dev/mapper/data-homes_crypt /home ext4 relatime,commit=30 0 2 /dev/mapper/data-media_crypt /mnt/media xfs relatime 0 2 /dev/mapper/data-var_crypt /var ext4 relatime,commit=30 0 2 /dev/mapper/ubuntu-swap_crypt none swap sw 0 0 #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 #dmsetup table --showkeys data-media_crypt: 0 586774520 crypt aes-cbc-essiv:sha256 099ce453b1f2557392433459c59b6983ad0f64b36c5ed58d2facbe3f7e5210a5 0 252:4 2056 data-media: 0 586776576 linear 9:2 523452800 data-homes_crypt: 0 261732344 crypt aes-cbc-essiv:sha256 f44ce80c9db536906cb8bd92e79331131fab9e97b05c0cc6765dc8e9a47ad8cb 0 252:2 2056 data-var: 0 261718016 linear 9:2 261734784 data-var: 261718016 419430400 linear 9:2 1110229376 data-homes: 0 261734400 linear 9:2 384 ubuntu-swap_crypt: 0 16777216 crypt aes-cbc-essiv:sha256 99eeeb1c19bacb41a35baabd23cb25f2d7866625da294b46086e63577b6ed05e 0 252:1 0 ubuntu-swap: 0 16777216 linear 9:3 63678464 ubuntu-root: 0 63676416 linear 9:3 2048 ubuntu-root_crypt: 0 63674360 crypt aes-cbc-essiv:sha256 0ee66e5902f0002017319f11025128c4e05a69556c0f13ddd48d45a630f8d6e9 0 252:0 2056 data-var_crypt: 0 681146360 crypt aes-cbc-essiv:sha256 e7331607be03b1776ac97dfedee43dcdbd345c4c93e2d05839836c22d2c08d91 0 252:3 2056 #lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sda2 8:2 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sda3 8:3 0 435G 0 part └─md2 9:2 0 869.9G 0 raid10 ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home ├─data-var (dm-3) 252:3 0 324.8G 0 lvm │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var └─data-media (dm-4) 252:4 0 279.8G 0 lvm └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdb 8:16 0 465.8G 0 disk ├─sdb1 8:17 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sdb2 8:18 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sdb3 8:19 0 435G 0 part └─md2 9:2 0 869.9G 0 raid10 ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home ├─data-var (dm-3) 252:3 0 324.8G 0 lvm │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var └─data-media (dm-4) 252:4 0 279.8G 0 lvm └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdc 8:32 1 968.8M 0 disk └─sdc1 8:33 1 964.8M 0 part sde 8:64 0 465.8G 0 disk ├─sde1 8:65 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sde2 8:66 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sde3 8:67 0 435G 0 part └─md2 9:2 0 869.9G 0 raid10 ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home ├─data-var (dm-3) 252:3 0 324.8G 0 lvm │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var └─data-media (dm-4) 252:4 0 279.8G 0 lvm └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdf 8:80 1 30.6M 0 disk └─sdf1 8:81 1 30.6M 0 part /mnt/keydev sdg 8:96 0 465.8G 0 disk ├─sdg1 8:97 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sdg2 8:98 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sdg3 8:99 0 435G 0 part └─md2 9:2 0 869.9G 0 raid10 ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home ├─data-var (dm-3) 252:3 0 324.8G 0 lvm │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var └─data-media (dm-4) 252:4 0 279.8G 0 lvm └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdh 8:112 0 149.1G 0 disk └─sdh1 8:113 0 59.6G 0 part └─md3 9:3 0 59.6G 0 raid1 ├─ubuntu-root (dm-0) 252:0 0 30.4G 0 lvm │ └─ubuntu-root_crypt (dm-5) 252:5 0 30.4G 0 dm / └─ubuntu-swap (dm-1) 252:1 0 8G 0 lvm └─ubuntu-swap_crypt (dm-9) 252:9 0 8G 0 dm [SWAP] sdi 8:128 0 59.6G 0 disk └─sdi1 8:129 0 59.6G 0 part └─md3 9:3 0 59.6G 0 raid1 ├─ubuntu-root (dm-0) 252:0 0 30.4G 0 lvm │ └─ubuntu-root_crypt (dm-5) 252:5 0 30.4G 0 dm / └─ubuntu-swap (dm-1) 252:1 0 8G 0 lvm └─ubuntu-swap_crypt (dm-9) 252:9 0 8G 0 dm [SWAP] sr0 11:0 1 1024M 0 rom zram0 251:0 0 100M 0 disk [SWAP] ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572 After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. Workaround: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #/etc/crypttab ubuntu-root_crypt UUID=0b1f585c-5dee-43a5-9106-b3bbd8a173b5 /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/ubuntu-root luks,keyscript=passdev,loud ubuntu-swap_crypt /dev/mapper/ubuntu-swap /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,swap data-var_crypt UUID=fb8c9458-bc86-4346-aca3-e845993f326f /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-var luks,keyscript=passdev data-homes_crypt UUID=172d9ce6-7aa6-4a2b-8e83-f7ea59b65fea /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-homes luks,keyscript=passdev data-media_crypt UUID=1739a5b3-8a38-4fac-9e73-df0181e62b29 /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-media luks,keyscript=passdev #/etc/fstab proc /proc proc nodev,noexec,nosuid 0 0 /dev/mapper/ubuntu-root_crypt / ext4 relatime,commit=30,errors=remount-ro 0 1 UUID=e6cb942e-1f09-4564-838c-280af283042e /mnt/keydev ext2 noauto,ro 0 0 UUID=dd4525cd-8bc4-4ba8-8a14-f743cf8e66f4 /boot ext4 defaults 0 2 /dev/mapper/data-homes_crypt /home ext4 relatime,commit=30 0 2 /dev/mapper/data-media_crypt /mnt/media xfs relatime 0 2 /dev/mapper/data-var_crypt /var ext4 relatime,commit=30 0 2 /dev/mapper/ubuntu-swap_crypt none swap sw 0 0 #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 #dmsetup table data-media_crypt: 0 586774520 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:4 2056 data-media: 0 586776576 linear 9:2 523452800 data-homes_crypt: 0 261732344 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:2 2056 data-var: 0 261718016 linear 9:2 261734784 data-var: 261718016 419430400 linear 9:2 1110229376 data-homes: 0 261734400 linear 9:2 384 ubuntu-swap_crypt: 0 16777216 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:1 0 ubuntu-swap: 0 16777216 linear 9:3 63678464 ubuntu-root: 0 63676416 linear 9:3 2048 ubuntu-root_crypt: 0 63674360 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:0 2056 data-var_crypt: 0 681146360 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:3 2056 #lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sda2 8:2 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sda3 8:3 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdb 8:16 0 465.8G 0 disk ├─sdb1 8:17 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sdb2 8:18 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sdb3 8:19 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdc 8:32 1 968.8M 0 disk └─sdc1 8:33 1 964.8M 0 part sde 8:64 0 465.8G 0 disk ├─sde1 8:65 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sde2 8:66 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sde3 8:67 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdf 8:80 1 30.6M 0 disk └─sdf1 8:81 1 30.6M 0 part /mnt/keydev sdg 8:96 0 465.8G 0 disk ├─sdg1 8:97 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sdg2 8:98 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sdg3 8:99 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdh 8:112 0 149.1G 0 disk └─sdh1 8:113 0 59.6G 0 part   └─md3 9:3 0 59.6G 0 raid1     ├─ubuntu-root (dm-0) 252:0 0 30.4G 0 lvm     │ └─ubuntu-root_crypt (dm-5) 252:5 0 30.4G 0 dm /     └─ubuntu-swap (dm-1) 252:1 0 8G 0 lvm       └─ubuntu-swap_crypt (dm-9) 252:9 0 8G 0 dm [SWAP] sdi 8:128 0 59.6G 0 disk └─sdi1 8:129 0 59.6G 0 part   └─md3 9:3 0 59.6G 0 raid1     ├─ubuntu-root (dm-0) 252:0 0 30.4G 0 lvm     │ └─ubuntu-root_crypt (dm-5) 252:5 0 30.4G 0 dm /     └─ubuntu-swap (dm-1) 252:1 0 8G 0 lvm       └─ubuntu-swap_crypt (dm-9) 252:9 0 8G 0 dm [SWAP] sr0 11:0 1 1024M 0 rom zram0 251:0 0 100M 0 disk [SWAP] ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron:  LANGUAGE=en_US  TERM=xterm  PATH=(custom, no user)  LANG=en_US.utf8  SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572
2012-10-27 20:56:47 GOo attachment added /etc/crypttab https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1072180/+attachment/3415884/+files/crypttab
2012-10-27 20:58:06 GOo attachment added /etc/fstab https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1072180/+attachment/3415885/+files/fstab
2012-10-27 20:58:57 GOo attachment added output of "dmsetup table" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1072180/+attachment/3415886/+files/dmsetup
2012-10-27 21:00:08 GOo attachment added output of "lsblk" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1072180/+attachment/3415888/+files/lsblk
2012-10-27 21:01:02 GOo description After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. Workaround: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #/etc/crypttab ubuntu-root_crypt UUID=0b1f585c-5dee-43a5-9106-b3bbd8a173b5 /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/ubuntu-root luks,keyscript=passdev,loud ubuntu-swap_crypt /dev/mapper/ubuntu-swap /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,swap data-var_crypt UUID=fb8c9458-bc86-4346-aca3-e845993f326f /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-var luks,keyscript=passdev data-homes_crypt UUID=172d9ce6-7aa6-4a2b-8e83-f7ea59b65fea /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-homes luks,keyscript=passdev data-media_crypt UUID=1739a5b3-8a38-4fac-9e73-df0181e62b29 /dev/disk/by-uuid/e6cb942e-1f09-4564-838c-280af283042e:/keys/darkgoo/data-media luks,keyscript=passdev #/etc/fstab proc /proc proc nodev,noexec,nosuid 0 0 /dev/mapper/ubuntu-root_crypt / ext4 relatime,commit=30,errors=remount-ro 0 1 UUID=e6cb942e-1f09-4564-838c-280af283042e /mnt/keydev ext2 noauto,ro 0 0 UUID=dd4525cd-8bc4-4ba8-8a14-f743cf8e66f4 /boot ext4 defaults 0 2 /dev/mapper/data-homes_crypt /home ext4 relatime,commit=30 0 2 /dev/mapper/data-media_crypt /mnt/media xfs relatime 0 2 /dev/mapper/data-var_crypt /var ext4 relatime,commit=30 0 2 /dev/mapper/ubuntu-swap_crypt none swap sw 0 0 #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 #dmsetup table data-media_crypt: 0 586774520 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:4 2056 data-media: 0 586776576 linear 9:2 523452800 data-homes_crypt: 0 261732344 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:2 2056 data-var: 0 261718016 linear 9:2 261734784 data-var: 261718016 419430400 linear 9:2 1110229376 data-homes: 0 261734400 linear 9:2 384 ubuntu-swap_crypt: 0 16777216 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:1 0 ubuntu-swap: 0 16777216 linear 9:3 63678464 ubuntu-root: 0 63676416 linear 9:3 2048 ubuntu-root_crypt: 0 63674360 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:0 2056 data-var_crypt: 0 681146360 crypt aes-cbc-essiv:sha256 0000000000000000000000000000000000000000000000000000000000000000 0 252:3 2056 #lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sda2 8:2 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sda3 8:3 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdb 8:16 0 465.8G 0 disk ├─sdb1 8:17 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sdb2 8:18 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sdb3 8:19 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdc 8:32 1 968.8M 0 disk └─sdc1 8:33 1 964.8M 0 part sde 8:64 0 465.8G 0 disk ├─sde1 8:65 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sde2 8:66 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sde3 8:67 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdf 8:80 1 30.6M 0 disk └─sdf1 8:81 1 30.6M 0 part /mnt/keydev sdg 8:96 0 465.8G 0 disk ├─sdg1 8:97 0 282.4M 0 part │ └─md0 9:0 0 564M 0 raid10 /boot ├─sdg2 8:98 0 30.6G 0 part │ └─md1 9:1 0 61.1G 0 raid10 └─sdg3 8:99 0 435G 0 part   └─md2 9:2 0 869.9G 0 raid10     ├─data-homes (dm-2) 252:2 0 124.8G 0 lvm     │ └─data-homes_crypt (dm-6) 252:6 0 124.8G 0 dm /home     ├─data-var (dm-3) 252:3 0 324.8G 0 lvm     │ └─data-var_crypt (dm-7) 252:7 0 324.8G 0 dm /var     └─data-media (dm-4) 252:4 0 279.8G 0 lvm       └─data-media_crypt (dm-8) 252:8 0 279.8G 0 dm /mnt/media sdh 8:112 0 149.1G 0 disk └─sdh1 8:113 0 59.6G 0 part   └─md3 9:3 0 59.6G 0 raid1     ├─ubuntu-root (dm-0) 252:0 0 30.4G 0 lvm     │ └─ubuntu-root_crypt (dm-5) 252:5 0 30.4G 0 dm /     └─ubuntu-swap (dm-1) 252:1 0 8G 0 lvm       └─ubuntu-swap_crypt (dm-9) 252:9 0 8G 0 dm [SWAP] sdi 8:128 0 59.6G 0 disk └─sdi1 8:129 0 59.6G 0 part   └─md3 9:3 0 59.6G 0 raid1     ├─ubuntu-root (dm-0) 252:0 0 30.4G 0 lvm     │ └─ubuntu-root_crypt (dm-5) 252:5 0 30.4G 0 dm /     └─ubuntu-swap (dm-1) 252:1 0 8G 0 lvm       └─ubuntu-swap_crypt (dm-9) 252:9 0 8G 0 dm [SWAP] sr0 11:0 1 1024M 0 rom zram0 251:0 0 100M 0 disk [SWAP] ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron:  LANGUAGE=en_US  TERM=xterm  PATH=(custom, no user)  LANG=en_US.utf8  SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572 After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. Workaround: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron:  LANGUAGE=en_US  TERM=xterm  PATH=(custom, no user)  LANG=en_US.utf8  SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572
2012-10-27 21:02:48 GOo description After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. Workaround: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron:  LANGUAGE=en_US  TERM=xterm  PATH=(custom, no user)  LANG=en_US.utf8  SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572 After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. Workaround: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron:  LANGUAGE=en_US  TERM=xterm  PATH=(custom, no user)  LANG=en_US.utf8  SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572
2012-10-27 21:03:12 GOo description After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. Workaround: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron:  LANGUAGE=en_US  TERM=xterm  PATH=(custom, no user)  LANG=en_US.utf8  SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572 After upgrading to 12.10 via "do-release-upgrade", I am no more able to boot. Previously I was able to boot with the same setup since Ubuntu 10.10. My /, /home, /var and /mnt/media partitions are LUKS encrypted LVs on top of RAID10,RAID1 md arrays and accessed via a key-file on a usb-stick. /boot is on an unencrypted md (md0). What I would have expected is cryptsetup mapping the encrypted volumes, mounting them and normal boot of the system. Actually cryptroot unlocks the key slot of the root filesystem (cryptsetup: cryptroot setup successfully) but it gets stuck on waiting for the root filesystem. WORKAROUND: Boot in recovery mode. Wait for the timeout for the root fs to finish. In the recovery menu select "root" to access the root shell. Eventually the root filesystem is mounted after the failure hooks and I am able to boot by typing: # mount / -o remount,rw # mount /boot # mount /mnt/keydev # cryptsetup -d /mnt/keydev/keys/darkgoo/data-media luksOpen /dev/mapper/data-media data-media_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-homes luksOpen /dev/mapper/data-homes data-homes_crypt # cryptsetup -d /mnt/keydev/keys/darkgoo/data-var luksOpen /dev/mapper/data-var data-var_crypt # mount /home # mount /var # mount /media # exit Select menu item "resume". The system now boots succesfully. #lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: initramfs-tools 0.103ubuntu0.2 [modified: usr/share/initramfs-tools/scripts/local] ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sat Oct 27 20:30:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-08-23 (796 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MarkForUpload: True PackageArchitecture: all ProcEnviron:  LANGUAGE=en_US  TERM=xterm  PATH=(custom, no user)  LANG=en_US.utf8  SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: Upgraded to quantal on 2012-10-19 (8 days ago) mtime.conffile..etc.initramfs.tools.initramfs.conf: 2012-03-07T06:09:36.142811 mtime.conffile..etc.initramfs.tools.update.initramfs.conf: 2010-09-04T17:39:23.260572
2012-11-07 15:51:50 Launchpad Janitor initramfs-tools (Ubuntu): status New Confirmed
2012-11-20 06:32:10 JT Gould bug added subscriber JT Gould