Ubuntu server cannot find the root device

Asif Iqbal vadud3 at gmail.com
Tue Dec 21 18:42:55 UTC 2010


On Tue, Dec 21, 2010 at 1:36 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
> Here is the detail message http://pastebin.com/ihffpT7z.
>
> Here are the few relevant lines
>
> [    0.000000] Command line:
> BOOT_IMAGE=/boot/vmlinuz-2.6.32-27-generic
> root=UUID=08febc85-9ce2-40ac-a354-e006f709a586 ro console=ttyS0,9600n8
> [    0.000000] KERNEL supported cpus:
> [    0.000000]   Intel GenuineIntel
> [    0.000000]   AMD AuthenticAMD
> [..stripped for brevity..]
> 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/08febc85-9ce2-40ac-a354-e006f709a586 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)
>
> Any idea how to bring get it fixed?
>
> I cannot get to rescue mode from grub. timeout is `0' and I tried
> hitting escape fast, but could not catch it.
>
> I can however get to rescue mode by PXE booting from net image
>

I forgot to mention this happend after the last linux image upgrade in
the last hour. Until then I could reboot fine

> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?




More information about the ubuntu-server mailing list