Comment 10 for bug 559761

Hello Scott,

The updated mountall package (2.13~ppa1) appears to create more problems than it solves.

Although the mountall process no longer spams the console with "mountall: Plymouth command failed", there is now a more serious problem. The system no longer boots, even if fsck isn't doing disk checks. The last boot status messages show the disk status. After this, the system still responds to the Alt-Ctrl-F? commands to switch consoles, but no further advancement is seen in the boot process (KDM doesn't start, no logon prompts appear on the consoles). SysRq-R, SysRq-E, SysRq-I causes the system to launch the mountall-shell recovery shell, with the root partition mounted read only. The following output is observed on the console:

This output is transcribed. I've contracted some parts between the '<>' tags.
--- Output Begins ---

fsck from util-linux-ng 2.17.2
Root: clean, <xxx>/<yyy> files, <ppp>/<qqq> blocks
<Similar messages for all other partitions fsck usually checks>

SysRq : Keyboard mode set to system default
SysRq : Kill All Tasks

init: plymouth main process (348) killed by KILL signal
init: plymouth-stop pre-start process (854) terminated with status 1
init: udev main process (387) killed by KILL signal
init: udev main process ended, respawing
[ <uptime> ] udev: starting version 151
General error mounting filesystem

<Recovery shell boilerplate>
root@<host>:~#

--- Output Ends ---

I'm also attaching the list of running processes 'ps -eF', obtained once the root filesystem was remounted read/write.

Package versions:
mountall: 2.13~ppa1
plymouth: 0.8.2-2
kernel: 2.6.32-21 i386