Re: Ubuntu server cannot find the root device
Quoting Asif Iqbal (vad...@gmail.com): > how do I do that from busybox at (initramfs) ? mkdir /mnt2 mount /dev/sda2 /mnt2 cd /mnt2 mount -t proc proc proc # If you have a separate boot device, mount it now. I didn't chroot . # (you won't see a prompt here, just keep going) stty rows 24 cols 80 vi /boot/grub/grub.cfg # make the edits here exit cd / umount /mnt2/proc /mnt2 reboot -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On Tue, Dec 21, 2010 at 5:07 PM, Serge Hallyn wrote: > Quoting Asif Iqbal (vad...@gmail.com): >> 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 > > If you like, you might use blkid to find the UUID of /dev/sda2, and use > that. yeah, but the problem is it will still try to boot from md1 > >> 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? > > You've not run update-grub? > how do I do that from busybox at (initramfs) ? -- 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? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
Quoting Asif Iqbal (vad...@gmail.com): > I am back to same problem > > this is how my fstab looks like > > proc/proc procnodev,noexec,nosuid 0 0 > /dev/sda2 / ext4errors=remount-ro 0 1 If you like, you might use blkid to find the UUID of /dev/sda2, and use that. > UUID=ad5e933e-d6bf-0df0-dac9-edcf54bcf06d noneswapsw >0 0 > UUID="9b3de848-b6e7-4c6b-9659-89875da35403" /opt/splunk ext4 > defaults0 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? You've not run update-grub? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On Tue, Dec 21, 2010 at 3:13 PM, Asif Iqbal wrote: > On Tue, Dec 21, 2010 at 1:50 PM, Asif Iqbal wrote: >> On Tue, Dec 21, 2010 at 1:46 PM, Asif Iqbal wrote: >>> On Tue, Dec 21, 2010 at 1:43 PM, Asif Iqbal wrote: On Tue, Dec 21, 2010 at 1:39 PM, Scott Kitterman 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 procnodev,noexec,nosuid 0 0 /dev/sda2 / ext4errors=remount-ro 0 1 UUID=ad5e933e-d6bf-0df0-dac9-edcf54bcf06d noneswapsw 0 0 UUID="9b3de848-b6e7-4c6b-9659-89875da35403" /opt/splunk ext4 defaults0 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? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On Tue, Dec 21, 2010 at 1:50 PM, Asif Iqbal wrote: > On Tue, Dec 21, 2010 at 1:46 PM, Asif Iqbal wrote: >> On Tue, Dec 21, 2010 at 1:43 PM, Asif Iqbal wrote: >>> On Tue, Dec 21, 2010 at 1:39 PM, Scott Kitterman >>> 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. 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? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On Tue, Dec 21, 2010 at 2:41 PM, Serge Hallyn wrote: > Quoting Asif Iqbal (vad...@gmail.com): >> Here is the detail message http://pastebin.com/ihffpT7z. >> >> Here are the few relevant lines >> >> [ 0.00] Command line: >> BOOT_IMAGE=/boot/vmlinuz-2.6.32-27-generic >> root=UUID=08febc85-9ce2-40ac-a354-e006f709a586 ro console=ttyS0,9600n8 >> [ 0.00] KERNEL supported cpus: >> [ 0.00] Intel GenuineIntel >> [ 0.00] 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! > > Hi, > > you're upgrading from what, to what? And are you using multipath? from linux kernel 2.6.32-26-generic to 2.6.32-27-generic I am using linux software raid for root/swap/data root and swap are raid1 and data is raid10 > If so, you may need to use ppa:serge-hallyn/initramfs-multipath. > I'm still working (right now, in fact) on a fix that is proper > enough to be allowed into a package. > > -serge > -- 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? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
Quoting Asif Iqbal (vad...@gmail.com): > Here is the detail message http://pastebin.com/ihffpT7z. > > Here are the few relevant lines > > [0.00] Command line: > BOOT_IMAGE=/boot/vmlinuz-2.6.32-27-generic > root=UUID=08febc85-9ce2-40ac-a354-e006f709a586 ro console=ttyS0,9600n8 > [0.00] KERNEL supported cpus: > [0.00] Intel GenuineIntel > [0.00] 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! Hi, you're upgrading from what, to what? And are you using multipath? If so, you may need to use ppa:serge-hallyn/initramfs-multipath. I'm still working (right now, in fact) on a fix that is proper enough to be allowed into a package. -serge -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On 10-12-21 01:50 PM, Asif Iqbal wrote: > any suggestion on how to catch the grub menu? timeout `0' is not > helping to catch it. I tried esc few times real fast. Press and hold Shift before the BIOS POST finish, but before the OS load. The window of opportunity is very short. Yes, it's terribly annoying, but he, it boot faster! :) -- Etienne Goyer Technical Account Manager - Canonical Ltd Ubuntu Certified Instructor -LPIC-3 ~= Ubuntu: Linux for Human Beings =~ -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On Tue, Dec 21, 2010 at 1:46 PM, Asif Iqbal wrote: > On Tue, Dec 21, 2010 at 1:43 PM, Asif Iqbal wrote: >> On Tue, Dec 21, 2010 at 1:39 PM, Scott Kitterman 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. >> >> >> -- >> 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? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On Tue, Dec 21, 2010 at 1:43 PM, Asif Iqbal wrote: > On Tue, Dec 21, 2010 at 1:39 PM, Scott Kitterman 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? > > > -- > 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? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu server cannot find the root device
On Tue, Dec 21, 2010 at 1:36 PM, Asif Iqbal wrote: > Here is the detail message http://pastebin.com/ihffpT7z. > > Here are the few relevant lines > > [ 0.00] Command line: > BOOT_IMAGE=/boot/vmlinuz-2.6.32-27-generic > root=UUID=08febc85-9ce2-40ac-a354-e006f709a586 ro console=ttyS0,9600n8 > [ 0.00] KERNEL supported cpus: > [ 0.00] Intel GenuineIntel > [ 0.00] 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? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
