Failure to boot Windows 7 after installing Karma
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub-installer (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I have spent a day remedying this situation and I still do not fully understand what has gone on.
I have three hard discs:
sda - single partition - Windows Vista was installed on this and more recently windows 7 release candidate. I use this infrequently to run Xara Xtreme - the windows version is better than the linux version.
sdb -two partitions - Ubuntu Jaunty in an ext4 partition and a swap partition
sdc - single fat 32 parttion for Data backup. This is a new disk and 1TB is a fat32 partition and the rest (approx 500GB) was unused.
After installing Karmic alpha 4 on the unused part of Disk 3 (c) the system refused to boot windows. After a lot of trial and error I reinstalled Windows and Jaunty and removed Karmic and repaired the MBR but for some reason Windows would not boot. Booting went to the Grub Legacy menu and windows would not boot. Ubuntu booted without a problem.
I have discovered from Gparted that Windows 7 installs a second partition (100MB) and boots from this. This partition was on the sdc disc - disk three - Not the windows installation partition sda (drive c)
menu.lst had windows booting from hd(0,0) and this needed changing to hd(1,1) to work although I had calculated it should be hd(2,1)
It is all working fine now. I wonder if Grub 2 can cope with windows 7 booting from a second partition?
tags: | added: grub2 |
affects: | ubuntu → grub2 (Ubuntu) |
affects: | grub2 (Ubuntu) → grub-installer (Ubuntu) |
Am Mittwoch, den 19.08.2009, 02:22 +0000 schrieb Launchpad Bug Tracker:
>
> menu.lst had windows booting from hd(0,0) and this needed changing to
> hd(1,1) to work although I had calculated it should be hd(2,1)
>
> It is all working fine now. I wonder if Grub 2 can cope with windows 7
> booting from a second partition?
>
It can. It would be good to know how the generated grub.cfg from karmic
looked like.
os-prober should detect it and add so update-grub should add it to
grub.cfg