Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I'm running Ubuntu 13.04. Yesterday I tried to install updates but there was an error, and it suggested running apt-get -f install which I did.

Now when I try to boot, I get an error "Gave up waiting for root device". The text is almost identical to the text shown in this and this question. However, the "built-in shell" simply doesn't work! Nothing I type shows up on the screen or does anything.

Loading the previous kernel works (although there are a few graphics glitches) but as far as I can tell, it should be booting the exact same stuff. The new kernel is 3.8.0-31-generic and the previous working one is 3.8.0-25-generic.

I tried adding a rootdelay to grub as suggested but it just waits longer and shows the same screen. Here is my entire /boot/grub/menu.lst file, comments removed:

default     0
timeout     3

title       Ubuntu 13.04, kernel 3.8.0-31-generic
uuid        c690c1e6-beb9-46e7-85c2-145cd07d44ac
kernel      /boot/vmlinuz-3.8.0-31-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac ro quiet splash 
initrd      /boot/initrd.img-3.8.0-31-generic
quiet

title       Ubuntu 13.04, kernel 3.8.0-31-generic (recovery mode)
uuid        c690c1e6-beb9-46e7-85c2-145cd07d44ac
kernel      /boot/vmlinuz-3.8.0-31-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac ro  single
initrd      /boot/initrd.img-3.8.0-31-generic

title       Ubuntu 13.04, kernel 3.8.0-25-generic
uuid        c690c1e6-beb9-46e7-85c2-145cd07d44ac
kernel      /boot/vmlinuz-3.8.0-25-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac ro quiet splash 
initrd      /boot/initrd.img-3.8.0-25-generic
quiet

title       Ubuntu 13.04, kernel 3.8.0-25-generic (recovery mode)
uuid        c690c1e6-beb9-46e7-85c2-145cd07d44ac
kernel      /boot/vmlinuz-3.8.0-25-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac ro  single
initrd      /boot/initrd.img-3.8.0-25-generic

title       Ubuntu 13.04, kernel 3.8.0-23-generic
uuid        c690c1e6-beb9-46e7-85c2-145cd07d44ac
kernel      /boot/vmlinuz-3.8.0-23-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac ro quiet splash 
initrd      /boot/initrd.img-3.8.0-23-generic
quiet

title       Ubuntu 13.04, kernel 3.8.0-23-generic (recovery mode)
uuid        c690c1e6-beb9-46e7-85c2-145cd07d44ac
kernel      /boot/vmlinuz-3.8.0-23-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac ro  single
initrd      /boot/initrd.img-3.8.0-23-generic

title       Ubuntu 13.04, memtest86+
uuid        c690c1e6-beb9-46e7-85c2-145cd07d44ac
kernel      /boot/memtest86+.bin
quiet

title       --------------------------------
root

title       Windows Vista
rootnoverify    (hd0,2)
savedefault
makeactive
chainloader +1

With the rootdelay the line in the top section was:

kernel      /boot/vmlinuz-3.8.0-31-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac rootdelay=120 ro quiet splash 

As you can see the UUID is the same for all kernels. Why am I getting this problem, and what can I do to fix it?

The output of dpkg -l linux-image-* was pretty long so I put it here: http://pastebin.com/mLjQECBv

share|improve this question
    
@Braiam I've run that but no change. I've edited the output of the command into the question. –  DisgruntledGoat Oct 22 '13 at 1:16
add comment

1 Answer 1

up vote 4 down vote accepted
+50

Ok, first of all, there is tons of scruff in your kernel list, purge them:

sudo apt-get purge linux-image-2.6.* linux-image-3.0.* linux-image-3.2.*

The problems seems to have different causes, from software to hardware, but some of them doesn't apply to you since you are able to boot other kernels. So, what to do?

While you use other kernels, remove and reinstall the both new kernel:

 sudo apt-get clean
 sudo apt-get purge linux-image-3.8.0-31-generic linux-image-3.8.0-32-generic
 sudo apt-get install linux-image-generic

The first line will remove the kernel you have a problem with and a kernel that is "installed" but doesn't appear in the GRUB list. That should take care of possible errors while installing the kernel.

Now, if you see this block:

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/a0c70102-b5d8-4b82-a14c-225330e1c4d4 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) _ 

Then here the common "solutions" with their causes:

  1. You attempted to fix the issue using rootdelay=, sadly that doesn't work in your case, since the problem could be elsewhere.

    /boot/vmlinuz-3.8.0-31-generic root=UUID=c690c1e6-beb9-46e7-85c2-145cd07d44ac rootdelay=120 ro quiet splash
  2. If you are using a RAID (doubtful since other kernels boot) this could cause problems. Mooving the partition to a non-raid filesystem should do the trick. Or checking if /etc/initramfs-tools/modules has the correct modules then running sudo update-initramfs -u.
  3. While you use (initramfs) built-in shell, you could type exit and should boot too. Again, problems is elsewhere.
  4. Bad filesystems could cause this. Running fsck from a live system should help.
  5. If you remove quiet splash you could get even more details about what exactly fails. If you experience this issue, remove the quiet splash from your grub script, that would really helps.

This are some tips I collected here and there, if you experience the same problem, please use the 5 tip and give full output of the kernel messages.

share|improve this answer
1  
If you mean to just delete the rootdelay part, I added that after the problem started, as stated in my question. So with that removed, that's how it was originally. –  DisgruntledGoat Oct 21 '13 at 23:13
    
@DisgruntledGoat updated answer with even more information. –  Braiam Oct 22 '13 at 6:10
    
Thanks for the update. Reinstalling the kernel worked great! I did have a bunch of glitchy graphical issues on the desktop but I managed to fix those by reinstalling nautilus. –  DisgruntledGoat Oct 22 '13 at 16:52
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.