On Thu, 2009-12-24 at 04:24 +, Stephen Cradock wrote:
> The symptoms are dramatic: the error message is
>
> mountall: cannot connect to plymouth
>
That's not an error message, it's just a warning; I'll make a note to
expand the text a bit. It should probably read:
"mountall: cannot connect to plymouth, you will not see
fsck progress and will not be prompted to solve issues"
> bootchart shows that plymouthd does not start as expected, and the fsck
> tasks are done without any delay.
>
Why would you expect plymouth to start? It's not in the default
installation yet.
> There may or may not be other error messages: one I got was
>
> cannot open session: no such file/directory
>
This is one of many plymouth issues right now.
> ** Attachment added: "bootchart.png"
>http://launchpadlibrarian.net/37147789/bootchart.png
>
The bootchart suggests that for some reason ureadahead isn't running for
you; your boot is largely in I/O wait, ureadahead appears to exit
immediately.
Do you have a /var/lib/ureadahead/pack ? What is the output of
"ureadahead --dump" ?
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
After latest mountall update on Lucid, mountall exits because it cannot connect
to Plymouth
https://bugs.launchpad.net/bugs/499519
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
