The original bug description was about a message that did NOT prevent booting
However if for some reason you cannot boot but can view boot messages on a text console then there is a good chance this message will already be visible and nothing much else. So if you have not looked before you might think this is the cause of your boot problem. Consequently many people who cannot boot (and I cannot boot) have ended up commenting on this ticket. As boot problems and the message are not directly related there is not much reason to assume that different boot problems reported here have a common cause. All in all it does not make sense to extend the scope of this ticket to fixing issues that prevent booting. One good reason for getting rid of the message is to avoid providing a false lead for people who have boot problems but that is the only useful connection to make between the two types of issue. Nevertheless, as someone with boot problems some of the comments above are useful (I can boot using recovery mode) but I am now going to look elsewhere for resources specifically about boot problems. Good luck :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273261 Title: Cryptsetup error during boot: /scripts/local-top/cryptroot: line 1: can't open /dev/mapper/ubuntu--vg-root: no such file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
