View Full Version : [ubuntu] 9.10 - Kernel Update 2.6.32-22-generic = sh.grub>

September 6th, 2010, 03:36 PM
hi all,

I did the kernel update via Update Manager today. Unfortunately , after this , disaster happened whereby sh.grub> prompt appeared on screen.

I got no idea how to rescue or repair the grub. I installed Ubuntu 9.10 in my E:\ under Windows 7 partition and labeled as "ubuntu". It has dual boot capability.

Please advise. Appreciate

September 6th, 2010, 03:47 PM
Really need more info, read on:

This sounds like a Wubi install, does that sound right?

If so this may be helpful:


Although I'm thinking 2.6.32* is a Lucid kernel :confused:

I'd want to be sure we're working with Karmic and not Lucid before proceeding. There's a different problem with Wubi in Lucid:


But it should render the whole puter unbootable, is that where you're at with this?

If so this may be the place to look:

Important Note to Wubi (Windows Ubuntu) Users: Grub Update results in "No Such Disk":
A late July 2010 Grub 2 update is causing a "no such disk" error for some users of WUBI, resulting in an unbootable system. If the system doesn't display the original Windows menu, the most likely cause of the failure is that Grub 2 was installed in the MBR and/or on the Windows partition. To correct this, restore the Windows bootloader using this link:


That's taken from here:


September 6th, 2010, 04:01 PM
hi kansasnoob, thanks for your reply. Yes, I installed it with wubi last time

However I did try out the method given in
http://sourceforge.net/apps/mediawiki/bootinfoscript/index.php?title=Boot_Problems:Wubi_9.10 before my posting to replace the wubildr given in the link, turns out that my ubuntu repetitively rebooting while ubuntu is chosen in dual boot option.

I believe my existing kernel which running fine prior to update was Karmic. Unfortunately there is no way I could cross-check again, since my grub corrupted. Maybe. Do you know how to retrieve the list from sh.grub>

Hope to hear again. Thanks

September 6th, 2010, 04:26 PM
Can you boot anything?

Can you still boot Windows only?

I think the most helpful info you could provide would be the output of the Boot Info Script as described here:


Alternative instructions:


That can be done from a live CD/USB.

September 6th, 2010, 04:42 PM
I should also add that I'm not very knowledgeable regarding Wubi because of this:

Any gotcha?

Hibernation is not supported under Wubi, moreover Wubi filesystem is more vulnerable to hard-reboots (turning off the power) and power outages than a normal filesystem, so try to avoid unplugging the power. An Ubuntu installation to a dedicated partition provides a filesystem that is more robust and can better tolerate such events.

I'm rural and power outages are very common!

Every time I got Wubi working it would only last a few days to a few weeks :(

September 6th, 2010, 04:49 PM
It is booting with windows 7 while i am replying the post.
Boot into any Linux based operating system, LiveCD or LiveUSB with an Internet connection. --> Since, i can't boot into ubuntu at all, is that mean the only way is to boot with ubuntu 9.10 DVD and run the script to provide the info ?

Note: If yes, should I have to follow the solution "If you can't boot into the Ubuntu install: From a live Ubuntu CD: " given in


September 6th, 2010, 06:35 PM
Any live Linux media should work. I often use Puppy or a very old version of either Damn Small linux or Knoppix just because they seem to work on nearly anything.

So, yes, a Live DVD will work. I'm lazy, so instead of typing "sudo bash ~/Desktop" or "sudo bash ~/Downloads", I just "cd" the directory where the "boot_info_script" is downloaded to and then "run as root' "bash boot_info_script055.sh".

So, in Ubuntu I'd download the boot info script, by default Firefox will drop it in Downloads, so I'd do this:

lance@lance-desktop:~$ cd Downloads
lance@lance-desktop:~/Downloads$ sudo bash boot_info_script055.sh
[sudo] password for lance:
Identifying MBRs...
Computing Partition Table of /dev/sda...
Computing Partition Table of /dev/sdb...
Searching sda1 for information...
Searching sda2 for information...
Searching sda3 for information...
Searching sda4 for information...
Searching sda5 for information...
Searching sda6 for information...
Searching sda7 for information...
Searching sda8 for information...
Searching sda9 for information...
Searching sda10 for information...
Searching sda11 for information...
Searching sda12 for information...
Searching sda13 for information...
Searching sda14 for information...
Searching sdb1 for information...
Searching sdb2 for information...
Searching sdb5 for information...
Finished. The results are in the file RESULTS6.txt located in /mnt/sda7

The only catch is that some older Linux media still designates drives as "hd" instead of "sd".