** Changed in: mountall (Ubuntu)
Status: Triaged = Fix Committed
--
Boot hangs waiting for local filesystems if / isn't in fstab and / is only
mounted ro
https://bugs.launchpad.net/bugs/527216
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package mountall - 2.10
---
mountall (2.10) lucid; urgency=low
* Rework the Plymouth connection logic; one needs to attach the client to
the event loop *after* connection otherwise you don't get disconnection
notification, and one needs to actually
** Changed in: mountall (Ubuntu)
Status: New = Triaged
--
Boot hangs waiting for local filesystems if / isn't in fstab and / is only
mounted ro
https://bugs.launchpad.net/bugs/527216
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
creating a file /etc/udev/rules.d/root.rules with the content for the
root device as found in /proc/self/mountinfo similar to the following
fixes the bug:
SUBSYSTEM==block, ENV{MAJOR}==8, ENV{MINOR}==0, SYMLINK+=root
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) = Scott James
We've triaged this on #ubuntu-devel today, the problem is that the
kernel doesn't pass the device specified by root= to userspace, e.g. by
naming it in /proc/self/mountinfo, and instead passes /dev/root.
mountall will wait for that device to appear, which it never does,
because nothing creates it.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39736716/Dependencies.txt
** Changed in: mountall (Ubuntu)
Importance: Undecided = Low
--
Boot hangs waiting for local filesystems if / isn't in fstab and / is only
mounted ro
https://bugs.launchpad.net/bugs/527216
You
NB: I tried with the linux armel/versatile kernel and qemu with a lucid
rootfs; I actually had a fstab myself, but a lot of people using
rootstock do not in fact have / in their fstab; I've mentioned this
issue to Oliver for fixing in rootstock/documentation.
--
Boot hangs waiting for local
