[Bug 1096307] Re: Boot process hang because 'mountall' fails
Steve Langasek
steve.langasek at canonical.com
Thu Jan 31 19:33:40 UTC 2013
Ok, if the messages are not showing up, that would seem to be a bug in
plymouth rather than in mountall. And it seems to be specific to use of
a serial console. Could you post the full contents of /proc/cmdline on
the affected system? (Even better would be to run 'apport-collect
1096307' and let apport auto-collect the system data relevant to the
plymouth package.)
> Is it possible that there is some package missing or and mis-configuraiton
> within our installation ?
The plymouth package is a required component and a dependency of
mountall; and the 'details' plugin used as the fallback for displaying
messages is part of the core plymouth package. So this is unlikely to
be a configuration problem.
** Package changed: mountall (Ubuntu) => plymouth (Ubuntu)
** Changed in: plymouth (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1096307
Title:
Boot process hang because 'mountall' fails
Status in “plymouth” package in Ubuntu:
New
Bug description:
We suspect a bug in Ubuntu 12.04 where boot process is hanged because ‘mountall’ fails due to an HDD failure.
The issue can be easily reproduced through either of the following scenario on Ubuntu 12.04
1. Mount a non-existing disk device node.
2. Disk/partition error. You can simulate such error by corrupting a working partition using DD command.
In either case, you will see system stuck at mount procedure and never reach the login prompt.
I have tried some option like “timeout=30”, “optional”, update mountall to v2.46. But none of them is working.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1096307/+subscriptions
More information about the foundations-bugs
mailing list