on my production ubuntu server (HP380G6) 10.04 LTS i noticed this same issue.
console was hanging on an fsck .. and when logged i (ssh) a saw the
" /sbin/plymouthd --mode=boot --attach-to-session
"
running.
ubuntu is completely uptodate (today) and having mountall 2.15 installed.
So with the fix of mountall is probably only a partial fix/workaround
as a possibel (not tested yet) i adjusted the /etc/default/grub with GRUB_CMDLINE_LINUX_DEFAULT="" (removed the quiet and only option)
I didn't tested the workaround yet, and i'm not 100% now that everything that has to be started is actually started (apart from getty's).
ps: actually i have no indication plymouthd was eating CPU at all, haven's specially looked at that, but i see at the time i looked at it the time consumes was stil 0, so below 1 second.
Hello,
on my production ubuntu server (HP380G6) 10.04 LTS i noticed this same issue.
console was hanging on an fsck .. and when logged i (ssh) a saw the
" /sbin/plymouthd --mode=boot --attach-to-session
"
running.
ubuntu is completely uptodate (today) and having mountall 2.15 installed.
So with the fix of mountall is probably only a partial fix/workaround LINUX_DEFAULT= "" (removed the quiet and only option)
as a possibel (not tested yet) i adjusted the /etc/default/grub with GRUB_CMDLINE_
I didn't tested the workaround yet, and i'm not 100% now that everything that has to be started is actually started (apart from getty's).
ps: actually i have no indication plymouthd was eating CPU at all, haven's specially looked at that, but i see at the time i looked at it the time consumes was stil 0, so below 1 second.
Regards,
Arjan Filius