Kernel > 2.6.32-20 does not boot (origin documents system does not exist)

Among my note pads is a Compaq nc4200 (Mobile Intel 915GM Express). All Ubuntu bits > 2.6.32-20 do not boot on that particular equipment. Rather I get a mistake message:

error: unexpectedly disconnected from boot status daemon
Begin: Waiting for root file system ...

After some googling I located Bug #574755 in Debians BTS. In this instance plymouth had some bug. So I attempted to add i915 modeset=1 to /etc/initramfs-tools/modules. This made the boot screen full absence. I saw no result any longer. 2nd I attempted to remove the plymouth-package. After removing it I obtained the very same message once more.

I dug a little bit more. From my perspective this have to be some sort of documents system point. Result 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 time there is a timeout and also a BusyBox covering shows up:

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.

Currently I'm out of suggestions. What can be the source of it? Just how I settle this concern?

2019-05-04 08:04:57
Source Share
Answers: 3

Have you attempted to make use of the old symbols/ dev/sdxn as opposed to making use of UUID?.

2019-05-12 09:13:38

If you are still having this trouble : 1. Most likely to launch pad and also submit a bug. A new bug. Do not add a "me also" to an existing bug. 2. Most likely to #ubuntu - kernel on freenode (this is an irc network on an irc web server). The Ubuntu kernel group hangs around there virtually 24 hrs daily, Monday via Friday. Please, do not appear, ask an inquiry and also if you do not get a solution today, disconnect. If you hold your horses, you can get people focus and also they will certainly attempt to aid. Actually, they are not terrifying individuals : -)

2019-05-10 07:41:23

It's feasible that your drive is not coming on-line quickly sufficient and also the kernel is surrendering on it prior to it prepares. There's a means to examine this to function around it.

The guidelines listed below think you are running Ubuntu 9.10 or later on. If you are running an earlier release, you can see for guidelines on executing the edits listed below.

When restarting your system, select the kernel too (you might require to hold change while the system is starting to see the GRUB bootloader food selection, relying on your arrangement). After that press 'E' to modify the boot alternatives.

Scroll to the line that begins with "kernel" and also relocate the arrow throughout of the line. At the end of that line, add a room and also "rootdelay = 60". This will certainly inform the kernel to wait approximately one minute for your drive to come to be all set. After that press Control - X too.

If all works out, your system will certainly boot. If this holds true, you can make the adjustments irreversible by including them to the default boot alternatives. To do this, open an incurable (Applications - Accessories - Terminal) and also type :

sudo gedit /etc/default/grub

Find the line that resembles :


and also transform it to


Finally, run

sudo upgrade - grub

to see to it your adjustments are effectively grabbed.

For additional information concerning the alternatives readily available in the bootloader, you can see (There is a bug record concerning this hold-up for details equipment at

2019-05-08 17:23:03