Gave up waiting for root device

Bug #525600 reported by craig
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
System76
New
Undecided
Unassigned

Bug Description

When booting up my lemur ultrathin, it brings up the system76 BIOS screen and lands on the GRUB screen to choose which kernel to boot. If I let it go through the the normal boot with kernel 2.6.28-19. The ubuntu logo shows up for around 20-30 seconds. Then it goes away and the screen remains black. I have let it sit there for 5 minutes without any changes. I have also tried to switch to a virtual terminal by pressing Ctrl+Alt+F1, and get no response. The only response I received was using Ctrl+Alt+Delete to restart.

Next time I came to the GRUB boot I used recovery mode on kernel 2.6.28-19. After waiting for 10-15 seconds for the system to look for the root device, I get the following lines.

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! /dev/disk/by-uuid/2c20b79b-bb2c-4422-9d48-d1cc487b189f does not exist. Dropping to a shell!

BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help for a list of built-in commands.

(initramfs)

I've done some searching and everyone seems to mention this is usually right after an upgrade to your kernel. However, I have been running the 2.6.28-19 for a week or so without any problems booting the system. In addition, I have kernels 2.6.28-16 and 2.6.28-17, which will not boot either.

Since, I am on the Ultrathin without a CD drive, I cannot boot from a live CD. I am currently trying to set-up a live USB with GParted. While I am setting that up, I thought I would see if this what System76 knows about this error. Is this common on your systems? What would you suggest to get this system booting again? Anything at all would be helpful.

Thanks,
Craig

Revision history for this message
craig (tapocol) wrote :

Sorry. I inputted the incorrect kernel number. They should all be 2.6.31-xx not 2.6.28-xx

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.