Fortunately, all my partitions in /dev/disks/by-uuid reappeared again. So I cannot reproduce the initial problem. But you can reproduce the hanging boot easily by creating a /home mount with a wrong uuid in /etc/fstab.
I have tested this approach (intentionally giving the wrong uuid of my /home partition) with mountall versions 0.2.2 as it is in karmic at the time of writing this and 0.2.2~boot2 as published in ppa. In both cases the boot hangs and cannot be interrupted, neither with ctrl-c nor with sysreq-e. Sysreq-e kills udev but not mountall anymore. Uninstalling cryptsetup so that ctrl-c might work does not help either. You need either a live-cd or another boot-partition to get the system running again. Attached is the output of mountall --debug of 0.2.2 with my correct and incorrect /etc/fstab before the reboot as requested. ** Attachment added: "m-0.22.log" http://launchpadlibrarian.net/33726055/m-0.22.log ** Attachment added: "m-0.22-bad.log" http://launchpadlibrarian.net/33726056/m-0.22-bad.log -- mountall hangs in case of inconsistent /etc/fstab https://bugs.launchpad.net/bugs/442495 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