After 9.10 grub update can not boot into Wubi install
Bug #477104 reported by
dknollman
This bug affects 170 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub |
Invalid
|
Undecided
|
Unassigned | ||
grub2 (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Karmic |
Won't Fix
|
Critical
|
Agostino Russo | ||
Lucid |
Fix Released
|
Critical
|
Agostino Russo | ||
lupin (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
GRUB2 could not read past 4G on NTFS.
The patch was <http://
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
[ 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.
Changed in grub (Ubuntu): | |
status: | New → Confirmed |
status: | Confirmed → New |
Changed in grub (Ubuntu): | |
status: | New → Confirmed |
affects: | grub (Ubuntu) → grub2 (Ubuntu) |
Changed in grub2 (Ubuntu): | |
importance: | Undecided → Critical |
Changed in grub2 (Ubuntu): | |
assignee: | nobody → hyungt1024 (hyungt1024) |
Changed in grub2 (Ubuntu): | |
assignee: | hyungt1024 (hyungt1024) → Lakshmanan (lak89) |
assignee: | Lakshmanan (lak89) → nobody |
Changed in grub2 (Ubuntu): | |
status: | Confirmed → Triaged |
description: | updated |
tags: | added: verification-needed |
Changed in grub2 (Ubuntu): | |
status: | Triaged → Fix Committed |
Changed in grub2 (Ubuntu): | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
description: | updated |
Changed in grub2 (Ubuntu Lucid): | |
assignee: | nobody → Agostino Russo (ago) |
Changed in grub2 (Ubuntu Karmic): | |
assignee: | nobody → Agostino Russo (ago) |
status: | New → Fix Committed |
tags: | removed: verification-done |
tags: | added: verification-needed |
Changed in grub2 (Ubuntu Lucid): | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in grub: | |
assignee: | nobody → Agostino Russo (ago) |
Changed in grub: | |
assignee: | Agostino Russo (ago) → nobody |
Changed in grub2 (Ubuntu Karmic): | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in grub2 (Ubuntu Karmic): | |
status: | Fix Committed → Incomplete |
Changed in grub2 (Ubuntu): | |
assignee: | Agostino Russo (ago) → nobody |
affects: | grub → null |
affects: | null → grub |
Changed in grub: | |
status: | New → Invalid |
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 img-2.6. 31-14-generic
sh:grub> initrd /boot/initrd.
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