After 9.10 grub update can not boot into Wubi install

I've got the same problem today. Seems like grub2 don't like something in its configuration file. I did something like that to boot the system:

sh:grub> linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda2 loop=/ubuntu/disks/root.disk ro
sh:grub> initrd /boot/initrd.img-2.6.31-14-generic
sh:grub> boot

sda2=(hdd0,2) in my is a windows partition with /ubuntu folder on it. Sure thing, you will have to change your kernel version in files (or just hit TAB to suggestions).

To find what drive is what you can use 'ls -l ' command or 'ls (hdd0,2)/' for the content. I've had (loop0) as an image of my linux root folder, supplementary partition (hdd0,1) and windows partition (hdd0,2). This will not solve the bug, but at least you will be able to use OS until it will be solved.

It is really disappointing, that this things still happening. After this bug will be gone, I'll definitely disable updates.

Hope it will help

Same here... I guess that when the upgrader asked whether we wanted to overwrite the current grub2 configuration file or not we should have said "YES" instead of "KEEP CURRENT VERSION" (or something like that).

I'm running grub in a second stage after rEFIt (this is an Intel MAC), and my situation is even worse because I cannot even enter the grub shell.

What I can do is boot from a liveCD and access the original filesystem. I guess there is something I must do to "/boot/grub/grub.conf" so that it works again.

Any idea ?

Same problem here. After a clean shutdown, I treid to reboot this morning, getting the same problem..

(Also, when booting to Windows, windows was running a chkdsk.. so maybe something else went wrong too.. :S)

This is how I fixed it:

1) Boot from a Live CD
2) Reinstall grub as explained here: https://wiki.ubuntu.com/Grub2#Recover%20Grub%202%20via%20LiveCD

Just in case the link above stops working, this is what I did:

# sudo mount /dev/sda4 /mnt
("/dev/sda4" is where my linux data partition -containing also "/boot"- can be found. The other three previous ones are OSX stuff).
# sudo mount --bind /dev/ /mnt/dev
# sudo chroot /mnt
# upgrade-grub
# grub-install /dev/sda
(yes... this is "/dev/sda", without the "4")

Once it boots again, the "update manager" does not find any new grub package... so I guess this won't happen again (after all the new grub was installed, we just re-created its config file)

Try to replace C:\wubildr and C:\wubildr.mbr with the respective files in C:\ubuntu\winboot\wubildr*
Please let me know if that works

Also please post the grub configuration file that does not work

This does not help :(

Also the fix suggested by Fernando does not work, as I use a root.disk file and no direct partition.

Replaced the files.
No change.
Still get the sh:grub> prompt.

Dieter

On Sat, Nov 7, 2009 at 7:31 AM, Agostino Russo <email address hidden>wrote:

> Try to replace C:\wubildr and C:\wubildr.mbr with the respective files in
> C:\ubuntu\winboot\wubildr*
> Please let me know if that works
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub” package in Ubuntu: New
>
> Bug description:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the problem after update.
>
> Help.
>

What is the grub.cfg inside of root.disk? root.disk > /boot/grub/grub.cfg
What is the output in the grub console of?

ls
ls (loop0)

Do you get any file printout with?
cat (loop0)/boot/grub/grub.cfg

From the sh:grub> ls (loop0) I get

Device loop0: Filesystem type ext2,
Last modification time 2009-11-06 00:53:47 Friday,
UUID bd548a62-c679-41f3-8c33-1854ff6ae498

Dieter

On Sat, Nov 7, 2009 at 9:04 AM, Agostino Russo <email address hidden>wrote:

> What is the grub.cfg inside of root.disk? root.disk > /boot/grub/grub.cfg
> What is the output in the grub console of?
>
> ls
> ls (loop0)
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub” package in Ubuntu: New
>
> Bug description:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the problem after update.
>
> Help.
>

I get a screen full of <0><0> ...

On Sat, Nov 7, 2009 at 9:06 AM, Agostino Russo <email address hidden>wrote:

> Do you get any file printout with?
> cat (loop0)/boot/grub/grub.cfg
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub” package in Ubuntu: New
>
> Bug description:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the problem after update.
>
> Help.
>

Same here

On Sat, Nov 7, 2009 at 8:31 AM, robau <email address hidden> wrote:

> This does not help :(
>
> Also the fix suggested by Fernando does not work, as I use a root.disk
> file and no direct partition.
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub” package in Ubuntu: New
>
> Bug description:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the problem after update.
>
> Help.
>

i try to istall ubuntu 9.10 on my acer aspire with windows xp sp3
with wuby i selected an empty parition on my hd and i continued the installation..
but when i restart the pc to complete the istallation and i selected ubuntu it has appeared

Try (hd0,0) : NTFS5:

and then

                        GNU GRUB version 1.97~1.97beta4
[ Minimal Bash-like line editing is supported ...

sh:grub>

Someone had find a solution??
thk

Agostino, is this needed before the cat (loop0)?

>insmod ntfs
>set root=(hd0,1)
>loopback loop0 /ubuntu/disks/root.disk

Ok, I did just try to cat the (Ioop0)/boot/grub/grub.cfg.. It is to long to fit on the screen, so I tried pausing it. It does not contain any interesting entries, (maybe because I tried the other solution above and broke something?).

Anyway, the problem I now have is that the command 'load_env' breaks with the error 'error file not found'

Is there a way to easily restore the grub.cfg in the root.disk from windows (or ubuntu live cd)?

ok so I found out how to restart by hand:

>insmod ntfs
>set root=(hd0,1)
>loopback loop0 /ubuntu/disks/root.disk
>set root=(loop0)
>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
> initrd /boot/initrd.img-2.6.31-14-generic

Now I probably have to add this somewhere to my /boot/grub/grub.cfg ... will do that tomorrow :S

I successfully booted to ubuntu using Zhmurov steps:

sh:grub> linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
sh:grub> initrd /boot/initrd.img-2.6.31-14-generic
sh:grub> boot

only changed "root=/dev/sda2" to to "root=/dev/sda1"
Because Ubuntu Wubi installed on C:\ Partition

I attached grub.cfg for you Agostino Russo

I installed 9.10 using wubi on xp I also updated grub with update manager. I have to manual boot with:

sh:grub>insmod ntfs
sh:grub>set root=(hd0,1)
sh:grub>loopback loop0 /ubuntu/disks/root.disk
sh:grub>set root=(loop0)
sh:grub>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
sh:grub>initrd /boot/initrd.img-2.6.31-14-generic
sh:grub>boot

Hmm, comment #11 shows that loop0 is already mounted,
which means that the steps in #19 up to `set root-(loop0)` are not needed.

What happens if you type `root` in the grub terminal (without entering any other command)?

I am particularly interested in why you are using `insmod ntfs`, since ntfs should be already built into grub.
If there is an ntfs module built-in, you should be able to list the content of an ntfs partition without using insmod.

This works if you add the boot command.
After the system booted, I ran "update-grub2" in terminal.
This fixed the boot problem.

thanks

On Sat, Nov 7, 2009 at 2:14 PM, robau <email address hidden> wrote:

> ok so I found out how to restart by hand:
>
> >insmod ntfs
> >set root=(hd0,1)
> >loopback loop0 /ubuntu/disks/root.disk
> >set root=(loop0)
> >linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1
> loop=/ubuntu/disks/root.disk ro
> > initrd /boot/initrd.img-2.6.31-14-generic
>
> Now I probably have to add this somewhere to my /boot/grub/grub.cfg ...
> will do that tomorrow :S
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “grub” package in Ubuntu: New
>
> Bug description:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the problem after update.
>
> Help.
>

I ran "update-grub2" after system boot in terminal as root and this did not fix my problem.

Agostino Russo when I keyed "root" at the prompt I got:

(loop0): File system is ext2

As far as why I used `insmod ntfs` I have no reason for using. (is my face red?)
what I used is:

sh:grub>set root=(loop0)
sh:grub>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
sh:grub>initrd /boot/initrd.img-2.6.31-14-generic
sh:grub>boot

and it worked.

Agostino, I took the grub.cnf entry from a clean wubi 9.10 install, so that's why the insmod is there :)

Thanks for everybody's posts to this issue -- they solved the problem for me. Here's a brief account:

I installed 9.10 AMD64 under Windows XP MCE using wubi, and got stranded at the grub2 prompt during the first reboot.
As described by others, I entered only:
> linux /boot/vml... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
> initrd /boot/init...
> boot

Where the dots are I pressed TAB for auto-completion. The boot was successful. I then installed all proposed updates, rebooted and again landed at the grub2 prompt. So I entered the above commands again and after successful boot entered in a terminal:
> sudo update-grub2

After that, the system booted normally.

The sudo update-grub2 broke my system :o

I earlier replaced the grub.cfg in /boot/grub, but the update-grub2 replaced that one by a new one?

McKraught what is the output of

cat (loop0)/boot/grub/grub.cfg

Augostino,

 here it is:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
  have_grubenv=true
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  saved_entry=${prev_saved_entry}
  save_env saved_entry
  prev_saved_entry=
  save_env prev_saved_entry
fi
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
 insmod ntfs
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set ee48086248082bc1
 loopback loop0 /ubuntu/disks/root.disk
 set root=(loop0)
 linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro quiet splash
 initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
 insmod ntfs
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set ee48086248082bc1
 loopback loop0 /ubuntu/disks/root.disk
 set root=(loop0)
 linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro single
 initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Home Edition (on /dev/sda1)" {
 insmod ntfs
 set root=(hd0,1)
 search --no-floppy --fs-uuid --set ee48086248082bc1
 drivemap -s (hd0) ${root}
 chainloader +1
}
menuentry "Microsoft Windows XP (on /dev/sdb1)" {
 insmod ntfs
 set root=(hd1,1)
 search --no-floppy --fs-uuid --set 8eb4b645b4b62f97
 drivemap -s (hd0) ${root}
 chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

hope this helps....
John

McKraught, that looks fine, can't you boot with that config.cfg?

I.e. can you do

configfile (loop0)/boot/grub/grub.cfg

then select the first option?

Please note, I only need reports for people who have the problem, if somehow you fixed the issue, please do not reply or you will be make debugging more complex. If it does NOT work for you, please post the output of the following grub commands:

ls
root
cat (loop0)/boot/grub/grub.cfg
configfile (loop0)/boot/grub/grub.cfg

A fresh install of Wubi 9.10, also failed to reboot after the initial configuration boot.
results of above commands are:

ls
(loop0) (hd0) (hd0,2) (hd0,1) (hd1) (hd1,1) (fd0)
root
(loop0): Filesystem is ext2.
cat (loop0)/boot/grub/grub.cfg
     (pages of garbage, eg. <cb><ce>8<aa>F[T<a4><bb>R<c3>)
configfile (loop0)/boot/grub/grub.cfg
error: unknown command '?'
Syntax error
Incorrect command
Syntax error
error: unknown command 'np???w<?????iq?' (some characters were untypeable)
Syntax error
Incorrect command

So it seems that (loop0)/boot/grub/grub.cfg is corrupted, can the others confirm?
You can also check the file if you boot manually as explained above and then open /boot/grub/grub.cfg

ls:
----

(loop0) (hd0) (hd0,5) (hd0,1)

root:
--------

Filesystem is ext2. <--- why its not ext4?

cat (loop0)/boot/grub/grub.cfg:
----------------------------------------

Fullscreen of <0><0><0><0><0>........ <--- Inverted colors, background white, text black

configfile (loop0)/boot/grub/grub.cfg:
-----------------------------------------------
error: unknown command '<value'
error: unknown command '</prop>'
error: unknown command '<prop'
error: unknown command '</node>'
error: unknown command '</node>'
error: unknown command '</oor:component data'

And about the grub.cfg after booting manually, i attached it in post #18

Tried to boot manually using:
> linux /boot/vml... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
> initrd /boot/init...
> boot

got:
ALERT! /hosts/ubuntu/disks/root.disk does not exist. Dropping into a shell!

the path exists in windows, but there is no ubuntu in hosts in BusyBox, although hosts exits.

Augostino,

I also got the errors:

sh:grub>configfile (loop0) /boot/grub/grub.cfg

error: unknown command A@??!?$'Ao?T%'
error: unknown command D?1%
error: unknown command E?H??L9???@??

@ looked like a smiley face :)
% looked like clubs ie deck of cards

Andy,

I've had:

ALERT! /hosts/ubuntu/disks/root.disk does not exist. Dropping into a shell!

but I had syntax wrong.

After typing:
> linux /boot/vml... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
> initrd /boot/init...
> boot
and getting:
ALERT! /hosts/ubuntu/disks/root.disk does not exist. Dropping into a shell!

I can't find root.disk or even 'Ubuntu' folder. 'Hosts' folder exists, but there's no 'Ubuntu' folder within it.

The Ubuntu folder exists in windows on the C: drive, so does the ubuntu/disks/root.disk.

I just can't seem to boot.

Has anyone got any ideas?

I have exactly the same problem. After the grub update, i restarted the next day (today) and am suck in the same place starting at sh:grub>

Did what you said Augostino. Here's what I got:

ls delivered:
(loop0) (hd 0) (hd 0,5) (hd 0,3) (hd 0,2) (hd 0,1)

root delivered:
Filesystem is ext2

then typed:
cat (loop0)/boot/grub/grub.cfg and got a whole bunch of <0>'s. Like a bunch of eyes looking at me in deep pleasure of my irritation.
configfile (loop0)/boot/grub/grub.cfg

and it returned me to sh:grub>

So after typing config (loop0)/boot/grub/grub.cfg I had no 1st option to select.

Additionally, I tried:

linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda loop=/ubuntu/disks/root.disk.ro
initrd /boot/initrd.img-2.6.31-14-generic
boot

I get a bunch of stuff including "Kernel Panic - not syncing: VFS:unable to mount root fs on unknown block (8,1)
I believe this is because it's trying to do it's thing from the wrong partition. It gives me a list of partitions:

0801 80293 sda1
0802 10485760 sda2
0803 231009280 sda3
0804 1 sda4
0805 2620416 sda5

I have no idea what I should be using for the /dev/sda bit. I tried sda1, sda2 and i think i also tried sda3. Nothing. Thoughts?

Whoops, sorry for the sp on your name Agostino. I typed it from someone else's sp error. Thanks in advance for any help.

If you have "ALERT! /hosts/ubuntu/disks/root.disk does not exist." it is because when you run the command

linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro quiet splash

you need to replace /dev/sda1 with the appropriate partition, /dev/sda1 means that wubi is to be found on the first partition of the first disk, which might not be the case.

If you have a corrupted /boot/grub/grub.cfg, please try to boot manually following the instructions above, do a system upgrade, the regenerate the grub configuration with the command: sudo update-grub

Then check whether the file /boot/grub.cfg is meaningful or just a bunch of random chars
If it seems ok try to reboot, otherwise please report it here.

Hi Agostino,

I also get a load of <0>'s when catting the loop0/boot/grub/grub.cnf before setting the loopback...

I also tried to figure out what is going wrong, it seems not to be related to grub, but rahter to what happens before/how grub is loaded... Here is why I think this:

I moved my broken wubi to /ubuntu.old. Did a clean 9.10 wubi install. Works like a charm. Then booted the old /ubuntu.old back to /ubuntu and then it works fine. So I figure the upgrade-grub2 messes up something that wubi uses?

Comment #90 worked for me.

Replacing C:\wubildr with Agostino's downloaded version fixed the boot problem encountered after Ubuntu update on 3/4/10 ... did not replace the other wubildr file in windows root ... THANK YOU ... this was going to be my 5th WUBI/Ubuntu reinstall as this happens every time ... seems like Wubi distribution should include this fix ... ??? thanks again ... StopChaos in Memphis, TN

Replacing C:\wubildr also worked for me, THANKS SO MUCH. This all happened after an update two nights ago (3/5/10), which I noticed when booting into ubuntu last night... Now I just have to fix a bunch of other things that have gone wonky (my keyboard is on num-lock regardless of whether it's actually on or not - which makes it impossible for me to type in stuff like passwords to perform stuff like sudo commands, connect to a network, etc...) The WUBI distro should most definitely include this fix though.

#90 worked also for me. Thanks!!
(i have dual boot with wubi Win7 and Ubuntu 9.10. The problem apeared after an update)

McKraught,

These codes worked for me (#22), I was able to get back in to ubuntu, then I updated grub2 but when I rebooted, I end up in the
sh:grub> again and I have to retype all the codes again to get into ubuntu. Is there anything else I need to do? I'm a newbee please help.

Thanks!

sh:grub>set root=(loop0)
sh:grub>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
sh:grub>initrd /boot/initrd.img-2.6.31-14-generic
sh:grub>boot

Agostino,

These codes worked for me but I have to manually entered the command every time I boot.

sh:grub>set root=(loop0)
sh:grub>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
sh:grub>initrd /boot/initrd.img-2.6.31-14-generic
sh:grub>boot

Then I replaced the wubildr from #90 and it booted automatically this time.

Thanks!

Agostino,

Like RonG, I can manually boot into a low graphics mode using the following steps:

sh:grub>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda3 loop=/ubuntu/disks/root.disk ro
sh:grub>initrd /boot/initrd.img-2.6.31-14-generic
sh:grub>boot

When I replaced the wubildr from #90, nothing happened and I must still boot manually.

for me the fix in comment #90 worked exactly as described, big thanks for the fix!

Tall Guy,

I've had a similar problem (running Vista) which was due to the fact that
Windows Vista silently failed to overwrite C:\wubildr.

Possible solution:
Download wubildr again to your Desktop/Downloads folder first, and only then
copy it over C:\wubildr using Explorer. You should get an User Account
Control prompt this time asking you for permission to do that.

On Wed, Mar 17, 2010 at 9:48 PM, Tall Guy <email address hidden> wrote:

> Agostino,
>
> Like RonG, I can manually boot into a low graphics mode using the
> following steps:
>
> sh:grub>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda3
> loop=/ubuntu/disks/root.disk ro
> sh:grub>initrd /boot/initrd.img-2.6.31-14-generic
> sh:grub>boot
>
> When I replaced the wubildr from #90, nothing happened and I must still
> boot manually.
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GRand Unified Bootloader: New
> Status in “grub2” package in Ubuntu: Fix Committed
> Status in “grub2” source package in Lucid: Fix Committed
> Status in “grub2” source package in Karmic: Fix Committed
>
> Bug description:
> GRUB2 could not read past 4G on NTFS.
>
> The patch was <http://launchpadlibrarian.net/37322976/debdiff>, uploaded
> to karmic-proposed as 1.97~beta4-1ubuntu5.
>
> Test case:
> Install Ubuntu 9.10 using Wubi
> Install all available updates.
> Reboot into Ubuntu.
>
> Original report follows:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the problem after update.
>
> Help.
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/grub/+bug/477104/+subscribe
>

--
Best regards
Ciprian Enache

Tall Guy,

For some reason I had two locations where I have the wubildr. C:\ and also C:\wubi\boot. When I replace the C:\wubi\boot location it did NOT wok. So I replaced both locations on C:\ and also C:\wubi\boot, then it load up automatically. Now it has been loading ok for me so far.

Thanks!

RobG and Ciprian Enache,

Thanks for the pointers. I am booting automatically into ubuntu again!!!

-Tall Guy

I think I have the same problem, however I am NOT using WUBI. I have Ubuntu installed directly onto the hard disk, but with all filesystems except /boot installed on an LVM.

The kernel panic only occurs with the latest kernel - 2.6.31-20-generic - but the system boots fine with the previous kernel 2.6.31-19-generic.

The message being given is
Kernel Panic - not syncing: VFS:unable to mount root fs on unknown block (0,0)

I've opened tasks on lupin for Mark Abene's patches from bug 477169. This is slightly independent of the grub2 patches that are the main substance of this bug, but since Agostino marked that bug as a duplicate of this one, we might as well hoover them up here.

This bug was fixed in the package lupin - 0.28

---------------
lupin (0.28) lucid; urgency=low

  * Don't corrupt wubildr if grub-mkimage is interrupted.
  * Fix /etc/grub.d/10_lupin to handle separate /boot (thanks, Mark Abene;
    LP: #477104).
  * Handle separate /boot in grub-mkimage, based on a patch from Mark Abene
    (LP: #477104).
  * Source /scripts/casper-functions only after processing 'prereqs'
    argument, to avoid warnings with new initramfs-tools.
 -- Colin Watson <email address hidden> Fri, 19 Mar 2010 19:11:03 +0000

I've uploaded lupin to karmic-proposed, which is now waiting for another archive admin to approve it. Pursuant to https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/477169/comments/70, I think that this should allow a straightforward update to repair wubildr without having to download and install Agostino's image by hand.

Accepted lupin into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I experienced this problem too on Ubuntu karmic installed via WUBI. Behaviour on my system is consistent with comment #47 by
Mark Abene. I was able to boot my system using these commands on the grub shell:

sh:grub>linux /boot/vmlinuz-2.6.31-19-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
sh:grub>initrd /boot/initrd.img-2.6.31-19-generic
sh:grub>boot

(2.6.31-20 gave the invalid magic number error)

I installed the proposed lupin packaged on my semi-broken system, and now my system won't boot. It takes me to the grub shell like before, but the boot sequence ends with a weird Call Trace and a soft lockup (modprobe:683) after AppArmor profiles are loaded.

Kernel 2.6.31-14 also fails to boot. Any tips on how can I get my ubuntu booting again?

Could you attach a photo of the error? I wonder if this is some different problem getting in the way.

The 4GiB NTFS barrier problem should be fixed in Lucid, at least, so I'm closing the grub2/lucid bug task for the time being. The Karmic tasks remain open.

2009-12-10 Vladimir Serbinenko <email address hidden>

        Eliminate NTFS 4Gib barrier.

        * fs/ntfs.c (read_attr): Use grub_disk_addr_t and grub_size_t.
        (read_run_data): Likewise.
        (grub_ntfs_read_run_list): Likewise.
        (grub_ntfs_read_block): Likewise.
        (grub_ntfs_iterate_dir): Likewise.
        (read_mft): Likewise.
        (read_data): Likewise.
        Use COM_LOG_LEN.
        * fs/ntfscomp.c (read_block): Cast ctx->target_vcn & 0xF to unsigned
        to avoid 64-bit division
        * include/grub/ntfs.h (COM_LOG_LEN): New definition.
        (grub_ntfs_rlst): Use grub_disk_addr_t.

Okay, the proposed lupin package did not completely break my system, it was a USB mouse I have that makes ubuntu not to boot when connected, sorry about that.

However, I can confirm, that the proposed package per-se won't fix a system in this state, I have to continue booting by usingthe aforementioned commands from the Grub shell.

Ricardo, could you clarify two things for me:

  * Do you have /boot mounted separately? (This should not really be necessary, but it was recommended as a workaround at one point in this bug, and the purpose of the lupin-support upgrade was to handle this better.)
  * Have you also upgraded grub-common and grub-pc from karmic-proposed? (If not, please do.)

Colin,

as for the first question, I do not have /boot mounted separately. How can I do this? I guess I have to create a new disk image to sit under the Win XP NTFS partition, move the boot contents to the new disk, add it to mtab, and rerun grub. I'm not sure about the steps to do it, specially the image creating part.

as for the second question, I just upgraded grub-common and grub-pc from karmic-propsed, after the upgrade the problem remains unfixed by default.

I just made an update for the first time yesterday to my karmic and the problem is occuring again.

After reading all 169 comments, nobody has the same problem that I have:

I dont have any "vmlinuz-..." like file placed in /boot/ . Moreover, I dont have any file called root.disk, could it mean that somehow the whole WUBI instalation has been deleted?
I've the /ubuntu folder at C:/

*I've already replaced wubildr at c:/ but as I dont have any vmlinuz-... like file I cannot follow instructions done in some comments as #1.

Thnx!

I have downloaded today the revision 160 and get a "grub>" prompt when trying to boot on Ubuntu

Can somebody point out to instructions on how to create and configure a separate disk image and get the /boot contents our of /ubuntu/disks/root.disk, so everybody experiencing this can put in place a workaround?

The recent lack of updates this unresolved issue is getting is discouraging.

Dosen't work :(

Anybody can provide manual boot.?

Ubuntu is in folder

D:\

Also i bymistakely replaced the file in comment #90 into D:/ubuntu/winboot/wubildr

Any help please?

This bug is a big monster! Imagine the amount of users with a broken boot. If I just had more information that could help, but I posted all I could find!

dosen't work yet

The wubi guide might help someone in here
https://wiki.ubuntu.com/WubiGuide#Cannot%20boot%20into%20Ubuntu
but probably not everyone

Good luck and regards from
Tom :)

Thanks tom...I'll try ;)

Fix wubi or ill switch 20 pcs to windows!

2010/4/18 friendishan <email address hidden>

> Thanks tom...I'll try ;)
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in GRand Unified Bootloader: New
> Status in “grub2” package in Ubuntu: Fix Released
> Status in “lupin” package in Ubuntu: Fix Released
> Status in “grub2” source package in Lucid: Fix Released
> Status in “lupin” source package in Lucid: Fix Released
> Status in “grub2” source package in Karmic: Incomplete
> Status in “lupin” source package in Karmic: Fix Committed
>
> Bug description:
> GRUB2 could not read past 4G on NTFS.
>
> The patch was <http://launchpadlibrarian.net/37322976/debdiff>, uploaded
> to karmic-proposed as 1.97~beta4-1ubuntu5.
>
> Test case:
> Install Ubuntu 9.10 using Wubi
> Install all available updates.
> Reboot into Ubuntu.
>
> Original report follows:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the problem after update.
>
> Help.
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/grub/+bug/477104/+subscribe
>

@juanit0

go ahead switch to windows, no problem !!

http://luckydev07.blogspot.com/

On Mon, Apr 19, 2010 at 1:54 AM, juanit0 <email address hidden> wrote:

> Fix wubi or ill switch 20 pcs to windows!
>
> 2010/4/18 friendishan <email address hidden>
>
> > Thanks tom...I'll try ;)
> >
> > --
> > After 9.10 grub update can not boot into Wubi install
> > https://bugs.launchpad.net/bugs/477104
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
> > Status in GRand Unified Bootloader: New
> > Status in “grub2” package in Ubuntu: Fix Released
> > Status in “lupin” package in Ubuntu: Fix Released
> > Status in “grub2” source package in Lucid: Fix Released
> > Status in “lupin” source package in Lucid: Fix Released
> > Status in “grub2” source package in Karmic: Incomplete
> > Status in “lupin” source package in Karmic: Fix Committed
> >
> > Bug description:
> > GRUB2 could not read past 4G on NTFS.
> >
> > The patch was <http://launchpadlibrarian.net/37322976/debdiff>, uploaded
> > to karmic-proposed as 1.97~beta4-1ubuntu5.
> >
> > Test case:
> > Install Ubuntu 9.10 using Wubi
> > Install all available updates.
> > Reboot into Ubuntu.
> >
> > Original report follows:
> > Binary package hint: grub
> >
> > Installed ubuntu 9.10 using Wubi.
> > Performed upgrades.
> > After a grub update could not boot.
> > Get screen:
> >
> > Try (hd0,0) : NTFS5:
> >
> > and then
> >
> > GNU GRUB version 1.97~1.97beta4
> > [ Minimal Bash-like line editing is supported ...
> >
> > sh:grub>
> >
> > Online help does not work for this grub version.
> >
> > Need instructions to recover.
> >
> > I could try a new install, but may recreate the problem after update.
> >
> > Help.
> >
> >
> >
> > To unsubscribe from this bug, go to:
> > https://bugs.launchpad.net/grub/+bug/477104/+subscribe
> >
>
> --
> After 9.10 grub update can not boot into Wubi install
> https://bugs.launchpad.net/bugs/477104
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GRand Unified Bootloader: New
> Status in “grub2” package in Ubuntu: Fix Released
> Status in “lupin” package in Ubuntu: Fix Released
> Status in “grub2” source package in Lucid: Fix Released
> Status in “lupin” source package in Lucid: Fix Released
> Status in “grub2” source package in Karmic: Incomplete
> Status in “lupin” source package in Karmic: Fix Committed
>
> Bug description:
> GRUB2 could not read past 4G on NTFS.
>
> The patch was <http://launchpadlibrarian.net/37322976/debdiff>, uploaded
> to karmic-proposed as 1.97~beta4-1ubuntu5.
>
> Test case:
> Install Ubuntu 9.10 using Wubi
> Install all available updates.
> Reboot into Ubuntu.
>
> Original report follows:
> Binary package hint: grub
>
> Installed ubuntu 9.10 using Wubi.
> Performed upgrades.
> After a grub update could not boot.
> Get screen:
>
> Try (hd0,0) : NTFS5:
>
> and then
>
> GNU GRUB version 1.97~1.97beta4
> [ Minimal Bash-like line editing is supported ...
>
> sh:grub>
>
> Online help does not work for this grub version.
>
> Need instructions to recover.
>
> I could try a new install, but may recreate the p...

Tom, the solution mentioned in the link you posted is not related with the issues regarding this bug.

In comment 166 Ricardo confirmed that the packages in -proposed do not help to automatically fix a broken system. There are tons of workarounds described here, but they are for the karmic-final package.

Agostino, can you please give a summary of the current state here? Should the current -proposed packages be removed due to failure, or will there be more changes to make them work, etc.? Thank you!

Hi,

I am facing the same error- after updating Ubuntu 9.10- but when I try to set the root as '/dev/sda1' in this step:

linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1

 it is not there( there is no sda in /dev)

Hence, I am not able to boot into ubuntu now :(
Anyone has had a similar issue? Got Around it? Please do let me know about the same!

This update has been in karmic-proposed for half a year or longer, without any testing feedback. I removed the proposed package again.

@Martin i just got this issue on a system that can't run lucid or maverick stably, how do i provide some feedback?

Resolved this issue with the solution proposed by #5 above.

I have encountered this issue in karmic, lynx, maverick, <?>

Repeating the solution:
Copy wubildr and wubildr.mbr from your installation found in X:\ubuntu\winboot\wubildr onto X:\. That is, copy from the full path to the root of that partition. X:\ is of course the partition where you installed wubi. It may or may not be C:\

Verified in maverick. Had a bunch of updates after that, which asked me to reboot. And it did fine without issues.

I am new to launchpad bug-tracking, so as of now posting this in karmic thread (although the main reason I am now in maverick is out of hope that probably this was fixed in later releases (including the "LTS" lynx). But it wasn't...

Don't know whether this is appropriate place, but I wonder if it is possible to keep the critical boot files from getting disturbed at every kernel update? I've been using the heavyweight SUSE for 8+ years before I switched to ubuntu recently for its "wubi" feature, because I didn't have the patience to sit through a long installation after I upgraded my pc. (I keep windows to play games). But never ever did SUSE manhandle the boot files. It is good to have updates, more so because the lightweight ubuntu has a larger user base so is more tested on field. But shouldn't boot files be undisturbed as long as the OS is in the pc?