Ubuntu server cannot find the root device

[Asif Iqbal]

On Tue, Dec 21, 2010 at 3:13 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
> On Tue, Dec 21, 2010 at 1:50 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
>> On Tue, Dec 21, 2010 at 1:46 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
>>> On Tue, Dec 21, 2010 at 1:43 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
>>>> On Tue, Dec 21, 2010 at 1:39 PM, Scott Kitterman <scott at kitterman.com> wrote:
>>>>> Try typing 'exit' from the shell you get dropped into.
>>>>>
>>>>
>>>> brings me back to initramfs
>>>>
>>>> (initramfs) exit
>>>> 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)
>>>>
>>>
>>> (initramfs) cd /dev
>>> (initramfs) ls md*
>>> md10
>>>
>>> It does not show md1 (root device) and md0 (swap)
>>>
>>> any idea why?
>>>
>>
>> any suggestion on how to catch the grub menu? timeout `0' is not
>> helping to catch it. I tried esc few times real fast.
>> Then I could switch back to the previous kernel and hope fully that
>> bring me back to my OS.
>
> With the help from genii-around and RoyK (#ubuntu-server in freenode)
> I were able to modify the fstab and used /dev/sda2 to boot to OS.


I am back to same problem

this is how my fstab looks like

proc            /proc           proc    nodev,noexec,nosuid 0       0
/dev/sda2 /               ext4    errors=remount-ro 0       1
UUID=ad5e933e-d6bf-0df0-dac9-edcf54bcf06d none            swap    sw
           0       0
UUID="9b3de848-b6e7-4c6b-9659-89875da35403"	/opt/splunk	ext4	defaults	0	0

but /proc/cmdline still using the UUID of /dev/md1
BOOT_IMAGE=/boot/vmlinuz-2.6.32-27-generic
root=UUID=08febc85-9ce2-40ac-a354-e006f709a586 ro console=ttyS0,9600n8

any idea why?


> Now I need to find a way to fix the initramfs and make sure I can boot
> back from md1 (root) UUID. Not sure how to do that yet.
>
> Let me know if anyone knows how to fix the initramfs. I noticed I lost
> my md10 raid10. I also need to find out how to fix that.
>
> Here is the latest dmesg http://pastebin.com/YHcDbHXn showing how
> badly md10 is broken.
>
>
>
>
>
>
>>
>>
>>>>
>>>>
>>>> --
>>>> 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?
>>>
>>
>>
>>
>> --
>> 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?
>



-- 
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?