*** This bug is a duplicate of bug 527666 ***
https://bugs.launchpad.net/bugs/527666
There were a bunch of confirmed bugs that should all be fixed with
Plymouth 0.8.1-3
(and hi, CaE!)
** This bug has been marked a duplicate of bug 527666
Waiting for /some/partition [SM]
--
Boot hangs
*** This bug is a duplicate of bug 527666 ***
https://bugs.launchpad.net/bugs/527666
err, I actually mean fixed with mountall 2.10 - it's been a long week
--
Boot hangs with Waiting for /some/mount [SM] forever.
https://bugs.launchpad.net/bugs/544223
You received this bug notification
I have remarked this as new to give Mr. Remnant or others an opportunity
to reexamine this considering the new evidence.
** Changed in: sysvinit (Ubuntu)
Status: Invalid = New
--
Boot hangs with Waiting for /some/mount [SM] forever.
https://bugs.launchpad.net/bugs/544223
You received
I confirm this bug, I am aso affected.
I have two partitions, including /home, which are ext4 on lvm and I randomly
get the Waiting for /home [SM] at boot.
--
Boot hangs with Waiting for /some/mount [SM] forever.
https://bugs.launchpad.net/bugs/544223
You received this bug notification because
I also confirm this bug.
Perhaps of interest; when shown this message for my troublesome
filesystem, I pressed S to get on with the boot. I then mounted it from
an ssh root shell which worked absolutely fine [using just mount /dump
so fstab was used to look up the details], however this was
You missed the second part of the original report, which also affects
me. That is, perfectly valid entires in fstab are hanging up with this
problem and mount without issue in recovery mode. In my case, I have a
second disk (EXT4 on LVM on LUKS) which mounts to /backup. The LUKS
crypt is
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41617959/Dependencies.txt
--
Boot hangs with Waiting for /some/mount [SM] forever.
https://bugs.launchpad.net/bugs/544223
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is the expected behaviour.
If you have an invalid or old entry in your /etc/fstab file, the system
will not boot because it's waiting for that file - or for you to tell it
what to do.
At this prompt, you could have pressed S to skip that entry and
continue booting or M to drop to a shell to
