Comment 20 for bug 1197789

So the processes are almost certainly tied to the mountall-shell job. Does the problem happen after every reboot? When it does occur, you can confirm that it's the mountall-shell job by running 'sudo service mountall-shell status', which probably shows that the service is start/running.

There's nothing in mountall that would trigger this behavior because of a plymouth failure; anything that caused mountall to fail should also have printed a line out in the upstart log. So this looks like mountall is instead dying with a signal from outside. Any idea what could be causing such a thing on your system?