I'd like to comment on this fix (e.g. cryptsetup - 2:1.0.6+20090405.svn49-1ubuntu7.2 w/watershed 4 and mountall 1.0):
I've been running with encrypted root/swap for a month, but then had hardware problems forcing me to replace the system disk. All was well for nearly a week 5+ days and 6+ reboots, but now I'm seeing on boot usually (but I can't say every time) the recovery shell message: One or more of the mounts listed in /etc/fstab cannot be mounted: /: waiting for /dev/mapper/xtremepapa-root /tmp: waiting for (null) /boot: waiting for /dev/disk/by-uid/blahblahblah Press ESC to enter into a recovery shell The first curious thing above is /tmp is not a separate file system and thus not explicitly called out. Secondly, when ESC to recovery, / is mounted (read-only), and a mount -av mounts /boot with no issues. If I ctrl-D I go back to the shell and see: One or more of the mounts listed in /etc/fstab cannot be mounted: /: waiting for /dev/mapper/xtremepapa-root /tmp: waiting for (null) Press ESC to enter into a recovery shell Thirdly, when ESC to recovery, mount -o remount,rw / and ctrl-d again, I proceed to boot with no further errors. This feels like a race-condition, and seems new to recent updates, though I guess it could be new simply because my new disk has gotten progressively slower in the last 6 days and am thus more susceptable to a race-condition, but from the bug responses to cryptsetup the last few days, it appears I'm not alone. Not knowing the true cause, I'm not sure if I should submit this as a new bug, or if adding this information to this one which appears quite similar should suffice. Thanks & Regards, == k == -- race condition between encrypted device creation and mountall probing with random-encrypted devices (swap, tmp) https://bugs.launchpad.net/bugs/475936 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
