Windows XP not detected by GRUB

Bug #10824 reported by Fred Westfall
84
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-installer
Fix Released
Undecided
Unassigned
os-prober (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I have a system with an ASUS Motherboard, 2 hard drives (both 160GB), and
Windows XP on the first drive. I attempted to install Ubuntu on the slave
drive. After doing so, GRUB did not recognize Windows XP and would only boot to
Ubuntu.

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 10825 has been marked as a duplicate of this bug. ***

Revision history for this message
Colin Watson (cjwatson) wrote :

Are you sure that the drives are really that way round? Check
/boot/grub/device.map to see which order GRUB thinks the drives are in. If
Windows is installed on anything other than (hd0), then this is bug #8283 and I
can supply a workaround.

Revision history for this message
Hidde Brugmans (hcbrugmans-deactivatedaccount) wrote :

I have ubuntu on the master, and winxp on the slave, XP was not recognised for
me when I installed this on colony3 / Breezy
i386, altho the hardware is amd64.

Revision history for this message
Martin Bergner (martin-bergner) wrote :

Is this still an issue today, with the dapper install cds?

Revision history for this message
Colin Watson (cjwatson) wrote :

The only fix I'm aware of applying for this bug was in May 2005, and Hidde reported a problem with Colony CD 3 which was released three months after that. I'm not sure that this bug should be closed just yet.

Revision history for this message
Fred Westfall (fbwestfalljr) wrote : Re: [Bug 10824] Windows XP not detected by GRUB

I have not tried a dual-install with Ubuntu since I encountered the problem long ago. I never received any infor regarding a potential fix for the problem and other versions of Ubuntu have occurred since then.

Martin Bergner <email address hidden> wrote: Public bug report changed:
https://launchpad.net/malone/bugs/10824

Comment:
Is this still an issue today, with the dapper install cds?

Fred Westfall

---------------------------------
New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

Revision history for this message
Fred Westfall (fbwestfalljr) wrote :

I have not tried a dual-install with Ubuntu since I encountered the problem long ago. I never received any infor regarding a potential fix for the problem and other versions of Ubuntu have occurred since then.

Colin Watson <email address hidden> wrote: Public bug report changed:
https://launchpad.net/malone/bugs/10824

Comment:
The only fix I'm aware of applying for this bug was in May 2005, and
Hidde reported a problem with Colony CD 3 which was released three
months after that. I'm not sure that this bug should be closed just yet.

Fred Westfall

---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1&cent;/min.

Revision history for this message
Carthik Sharma (carthik) wrote :

Thank you for reporting this bug.

Can anyone confirm this with the latest Dapper Flight 6 CD (or newer should you happen to read this later)?

While replying using an email client, please take care to not top-post, that is, please put your answer below the question, and not right at the top of the email you send. Makes it easier to comprehend the comment. Thanks a lot!

Revision history for this message
Colin Watson (cjwatson) wrote :

I suspect this is just the well-known os-prober bug that it doesn't find mounted partitions. A confirmation on Dapper wouldn't hurt, but I'm moving this bug to Confirmed so that it gets off bug triagers' radar of bugs to close if they don't hear back within some random time interval ...

Changed in os-prober:
status: Needs Info → Confirmed
Revision history for this message
Marco Rodrigues (gothicx) wrote :

After one year this isn't fixed yet?

Colin Watson (cjwatson)
Changed in os-prober:
assignee: kamion → nobody
Revision history for this message
Michael Doube (michael-doube) wrote :

This is still a problem in Hardy alpha 5 - there seem to be quite a few bugs posted about bad grub configs coming out of the install process but I didn't realise there was one in the bug number 10 k's (a new one just got posted in the 190 k's!). Attaching some info from the config I get:

Partitioning scheme is:

WinXP: /dev/sda1 * 1 1185 9518481 7 HPFS/NTFS
Gutsy: /dev/sda2 1186 2460 10241437+ 83 Linux
/home: /dev/sda3 2461 18182 126286965 83 Linux
            /dev/sda4 18183 19457 10241437+ 5 Extended
Hardy: /dev/sda5 18183 18947 6144831 83 Linux
Swap: /dev/sda6 18948 19457 4096543+ 82 Linux swap / Solaris

Revision history for this message
Erik Rosenlund (er-lug) wrote : Other problem after system updates

Please also consider the wrong (detection and) change of the Linux disk in the existing and working menu.lst during some system updates.

Reported in https://bugs.launchpad.net/bugs/197687 and noted as duplicate to this report.

Erik

Revision history for this message
Chronos (chronos00) wrote :

This happened to me several times. The common factor when grub was not detecting windows was that windows was HIBERNATED instead of shutdown. It seems that when windows is in hibernated state, grub fails to detect it's presence.
I hope one of the ubuntu developers could pass this "bug" to grub developers.

In any case, to fix the problem just head this way: (Spanish)
http://mundogeek.net/archivos/2008/04/26/anadir-windows-al-menu-de-grub/#more-1473

In short, you should add to /boot/grub/menu.1st the following lines:

title Windows XP
root (hd0,0)
chainloader +1

change hd0,0 to the drive and partition where you have windows installed.

Revision history for this message
Michael Doube (michael-doube) wrote :

This bug is still present in Intrepid alpha 4

Revision history for this message
Michael Doube (michael-doube) wrote :

This is much improved in Intrepid alpha 5, Grub now lists Intrepid, XP and Hardy on my notebook and assigns them to the correct drive. There is a bit of cruft left in my menu.lst though:

# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda5.
title Ubuntu 7.10, memtest86+ (on /dev/sda5)
root (hd0,4)
kernel /boot/memtest86+.bin
savedefault
boot

Which shouldn't be there because Hardy is on that partition.

Revision history for this message
Michael Doube (michael-doube) wrote :

I got a correct GRUB configuration after installing Intrepid alpha 6, perhaps because I tidied up Hardy's menu.lst. In any case, my triple boot configuration was automatically set up.

Revision history for this message
Michael Doube (michael-doube) wrote :

Ack. After installing Intrepid Beta I got another mysterious section in my menu.lst; same as above - looking for Hardy on /dev/sda1, where Intrepid is...

Revision history for this message
Michael Doube (michael-doube) wrote :

sorry, wrong menu.lst, that one is Hardy's. This one is Intrepid Beta's.

Revision history for this message
Michael Doube (michael-doube) wrote :

This is still going... just installed Jaunty alpha 4 and this is the menu.lst that was generated (note the absence of win XP and presence of wrong entries to boot Hardy on /dev/sda1, where XP is installed).

Revision history for this message
Michael Doube (michael-doube) wrote :

Installed Jaunty Final and got a sensible menu.lst, containing Jaunty, Hardy and Win XP, though I'm not sure whether it was copying a fixed menu.lst from a previous installation. This looks fixed to me.

Changed in os-prober (Ubuntu):
status: Confirmed → Fix Released
Changed in grub-installer:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.