Public bug reported:

My Lucid installation sometimes fails to boot, dropping me instead into
a BusyBox shell.  The error message looks like this:

Gave up wiating 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! /dev/disk/by-uuid/01234567-89ab-cdef-0123-456789abcdef does not exist. 
Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) _

My root= line contains the correct uuid.  (I masked it in the error
message above.)

Adding a rootdelay= of a couple minutes seems to make it fail less
often.  This is not a viable solution, because a couple minutes is way
to long to have to wait, because it doesn't always help, and because
booting used to work just fine with no wait.

If I wait a few minutes and type 'exit' at the (initramfs) prompt, the
system boots.  Sometimes I have to try this a few times before it works.

This bug is distinct from bug 360378, because in my case, the system is
able to boot if I wait long enough.  (Note the comments in bug 360378
stating that rootdelay doesn't help there.)

The problem is clearly not because my disk is taking too long to become
ready.  My root, /boot, and boot sector are all on the same disk.  If
the disk wasn't ready, the system would not have been able to load GRUB
or reach the BusyBox shell.

This seems to be a regression.  My system booted consistently in early
Intrepid kernels and in releases earlier than Intrepid.  The problem
first showed up late in the Intrepid release cycle, presumably after a
kernel upgrade.

I was using GRUB 1 when the problem first appeared.  It still exists
after upgrading to GRUB 2.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
gave up waiting for root device (temporary, intermittent)
https://bugs.launchpad.net/bugs/600728
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

Reply via email to