One of my notebooks is a Compaq nc4200 (Mobile Intel 915GM Express). All Ubuntu kernels > 2.6.32-20 don't boot on that machine. Instead I get an error message:
error: unexpectedly disconnected from boot status daemon
Begin: Waiting for root file system ...
After some googling I found Bug #574755 in Debians BTS. In this case plymouth had some bug. So I tried to add i915 modeset=1
to /etc/initramfs-tools/modules
. This made the boot screen complete lack. I saw no output anymore. Second I tried to remove the plymouth-package. After purging it I got the same message again.
I dug a bit further. From my point of view this must be some kind of file system thing. Output from boot:
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ...`
After some time there is a timeout and a BusyBox shell appears:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! r/dev/disk/by-uuid/(UUID-of-my-sda1) does not exist. Dropping to a shell!
BusyBox v1.19.3 (Ubuntu 1:1.10.3-7ubuntu1.1) built-in shell (ash)
Enter 'help' for a lost of built-in commands.
(initramfs)
Now I'm out of ideas. What can be the cause of it? How I resolve this issue?
linux-image-2.6.32-XY-generic
(XY
is UBuntus minor version).nosplash
andnoplymouth
, and removingquiet
in yourGRUB_CMDLINE_LINUX_DEFAULT
line in/etc/default/grub
?noplymouth
as a temporary option at grubs commandline and also completely deinstalled plymouth. In both cases I saw the error message. I also removedquiet
andsplash
temporarily, no effect. In my opinionnosplash
should lead to the same effect as removingsplash
. So I never tried this.