Can't login to windows xp after suse 11.1 install

Hello everyone,

I can’t seem to boot to windows xp after installation and then update from the openSUSE 11.1 live cd.

This is my /boot/grub/menu.lst

# Modified by YaST2. Last modification on Sun Apr 19 19:35:24 WEST 2009
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,4)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1
    root (hd0,4)
    kernel /boot/vmlinuz root=/dev/disk/by-id/ata-Hitachi_HTS541212H9AT00_HP0400BEGD827A-part5 resume=/dev/disk/by-id/ata-Hitachi_HTS541212H9AT00_HP0400BEGD827A-part7 splash=silent showopts
    initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
    rootnoverify (hd0,1)
    makeactive
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: Vendor diagnostic###
title Vendor diagnostic
    rootnoverify (hd0,0)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1
    root (hd0,4)
    kernel /boot/vmlinuz root=/dev/disk/by-id/ata-Hitachi_HTS541212H9AT00_HP0400BEGD827A-part5 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1  x11failsafe
    initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: memtest86###
title Memory Test
    kernel (hd0,4)/boot/memtest.bin

###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-2.6.27.21-0.1-default
    root (hd0,4)
    kernel /boot/vmlinuz-2.6.27.21-0.1-default root=/dev/disk/by-id/ata-Hitachi_HTS541212H9AT00_HP0400BEGD827A-part5 resume=/dev/disk/by-id/ata-Hitachi_HTS541212H9AT00_HP0400BEGD827A-part7 splash=silent showopts
    initrd /boot/initrd-2.6.27.21-0.1-default

This is the output from fdisk -l:

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb8f0ffa4

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         637     5116671   12  Compaq diagnostics
/dev/sda2   *         638        7013    51215220    c  W95 FAT32 (LBA)
/dev/sda3            7584        8412     6658942+   c  W95 FAT32 (LBA)
/dev/sda4            8413       14593    49648882+   5  Extended
/dev/sda5            8413        9507     8795556   83  Linux
/dev/sda6            9699       14593    39319056   83  Linux
/dev/sda7            9508        9698     1534176   82  Linux swap / Solaris

Partition table entries are not in disk order

I know that FAT32 is bad but I can’t do anything about it :wink:

/dev/sda1 boots fine to the system restore from Acer. when selecting Windows option on boot menu it simply flickers and returns to the menu. /dev/sda3 is non bootable, symply filesystem.

When using boot loader settings from YasT I go to other and press “Propose new configuration” it changes the menu but when pressing OK it asks for a floppy disk and doesn’t save the configuration (so on new boot I return to the same).

Hope anybody can help

Thanks in advance

Same happened to me and i am still waiting for a solution.
in order to dual-boot correctly xp with opensuse, i had to downgrade to opensuse 10.3 and use lilo as my preferred boot manager.

any new version for grub or lilo didn’t work on my system (versions from sled11, opensuse11 & opensuse 11.1).

for some strange reason, the lilo versions from SLED10 & opensuse 10.3 worked flawlessly, which is very weird and makes me wonder why older versions work while the new ones don’t.

can you try to install lilo instead of grub?

later on i am going to start a thread on how to install sled11, OS11 or OS11.1 using the good ol’ lilo from previous versions, if someone has ever achieved this feat, because i wish to accomplish this and don’t know how to do it.

<OF>

Windows menu to:

rootnoverify (hd0,1)
chainloader (hd0,1)+1

caf4926:

I changed the windows menu on the configuration file and although the change sticked it didn’t changed anything

Can you mount sda2 ? If so post XP’s boot.ini file.

Well if the utility partition is working then the next should follow lets try just taking out the make active of the original so it looks like:

###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,1)
chainloader +1

###Don’t change this comment - YaST2 identifier: Original name: Vendor diagnostic###
title Vendor diagnostic
rootnoverify (hd0,0)
chainloader +1

LostFarmer: I can mount sda2 without any problem. Here is my boot.ini from Windows XP

[boot loader]

timeout=15

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Media Center Edition" /noexecute=optin /fastdetect

caf4926: That was the original, without the make active, and it didn’t work. I tried to use that to see if it would do anything.

Have a look at swerdna’s info
GRUB Boot Multiboot openSUSE Windows (2000, XP, Vista) using the Grub bootloader.

Did you move or resize the XP partition to install Suse ?

Due to you being able to mount XP do not think there is a problem with the Volume Boot Record but can not see any other problem.
From a root terminal:

dd if=sda2 of=sda2vbr count=1 bs=512

xxd sda2vbr

post xxd’s display.

Do you have a floppy drive in comp ?

Hello,

LostFarmer,

dd if=sda2 of=sda2vbr count=1 bs=512
dd: opening `sda2': No such file or directory

I resized the XP partition for the instalation of openSUSE and I don’t have a floppy drive (nor floppys for that matter:) )

caf4926,
i followed the link but i don’t have the openSUSE DVD, and i don’t have the net power to download it.

Thanks for all the help you guys are trying to provide

If the fdisk you quote in the opening thread is correct then the:

rootnoverify (hd0,1)
chainloader (hd0,1)+1

Should work.

I see the * bootable flag on sda2 though. None of my windows partitions have this when using grub.

eg:

/dev/sda1 1 8487 68163795 7 HPFS/NTFS
/dev/sda2 * 8487 10575 16771829 83 Linux
/dev/sda3 10575 19457 71352697 f W95 Ext’d (LBA)
/dev/sda5 10575 10965 3140676 82 Linux swap / Solaris
/dev/sda6 10966 16191 41977813+ 83 Linux
/dev/sda7 16192 19457 26234113+ c W95 FAT32 (LBA)

This is my laptop with Vista grub to mbr
Box with xp is the same.
Might it be worth removing the flag on that to the suse /

Sorry the code in my post #9 is incorrect, it should be:

dd if=/dev/sda2 of=sda2vbr count=1 bs=512

xxd sda2vbr

I resized the XP partition

1)When you resized , did you move the start of XP partition ?
2)Did you try to boot into XP after resizing and before installing Suse ?
3)The boot.ini file you posted, is that the original or did you edit it after resizing ? 4)Do you have any way to boot into XP’s recovery console ?

I do not see any problem with the partition table or menu.lst file , so trying to think of possible reason for XP not to boot so asking questions and might find something wrong.

It says that xxd command not found.

1)When you resized , did you move the start of XP partition ?

  • No, just the end of the partition

2)Did you try to boot into XP after resizing and before installing Suse ?

  • Yeah, i did without any problem.

3)The boot.ini file you posted, is that the original or did you edit it after resizing ?

  • I didn’t edit anything, don’t really know how.

4)Do you have any way to boot into XP’s recovery console ?
I can enter the Acer recovery but it wants to erase all my data, not go to the recovery console

Hi,
I installed opensuse 11.2 version successfully on my computer x86_64 with an existing windows xp OS. But now when I start my computer I do not see the option to choose windows XP. Could anybody please tell me how to solve this problem? I was able to use both windows xp and suse 11.2 initially, but after i used the repair option once using the dvd-rom, I have this problem. Any help would be greatly appreciated.

Thank you,
Srikara

You need to open a terminal in openSUSE, become su and do:

fdisk -l

and

cat /boot/grub/menu.lst

Post result

Hi,
Thank you for the reply. These are the results of the command

fdisk -l

Disk /dev/sda: 146.8 GB, 146815737856 bytes
255 heads, 63 sectors/track, 17849 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xbf9bbf9b

Device Boot Start End Blocks Id System
/dev/sda1 1 1912 15358108+ 7 HPFS/NTFS
/dev/sda2 16543 17848 10490445 7 HPFS/NTFS
/dev/sda3 * 1913 15619 110101477+ f W95 Ext’d (LBA)
/dev/sda4 15620 15881 2104515 82 Linux swap / Solaris
/dev/sda5 1913 4523 20972826 83 Linux
/dev/sda6 4524 15619 89128588+ 83 Linux

Partition table entries are not in disk order

Disk /dev/sdb: 4007 MB, 4007624704 bytes
32 heads, 63 sectors/track, 3882 cylinders
Units = cylinders of 2016 * 512 = 1032192 bytes
Disk identifier: 0x19864c83

Device Boot Start End Blocks Id System
/dev/sdb1 1 3882 3913024+ b W95 FAT32

cat /boot/grub/menu.lst

system001:~ # cat /boot/grub/menu.lst

Modified by YaST2. Last modification on Tue Feb 2 02:34:29 IST 2010

THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader

Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,4)/boot/message
##YaST - activate

###Don’t change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX
root (hd0,4)
kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-35000cca005c45f18-part5 repair=1 resume=/dev/disk/by-id/scsi-35000cca005c45f18-part4 splash=silent quiet showopts vga=0x346
initrd /boot/initrd

###Don’t change this comment - YaST2 identifier: Original name: Linux other 1 (/dev/sda6)###
title Linux other 1 (/dev/sda6)
rootnoverify (hd0,5)
chainloader +1

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – SUSE LINUX
root (hd0,4)
kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-35000cca005c45f18-part5 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x346
initrd /boot/initrd

Thank you for any help with this problem.

-Srikara

You need to edit the meun.lst file and add in what I post - but forst you need to knpw how to edit it.

Open a terminal and copy in one of the following, depending if you use kde or gnome

kdesu kwrite /boot/grub/menu.lst
gnomesu gedit /boot/grub/menu.lst

###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
map (hd0) (hd0)
map (hd0) (hd0)
rootnoverify (hd0,0)
makeactive
chainloader +1

it’s possible the above will not work because I’m not certain which partition is you XP install, so if the first fails, try this

###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd0,1)
makeactive
chainloader +1

caf4926-correct me if I’m wrong with my thinking.

##YaST - generic_mbr

/dev/sda3 * 1913 15619 110101477+ f W95 Ext’d (LBA)

The way I read, is a generic code is installed into the MBR , with grub stage 1 in sda3.

If that is correct and one uses ‘makeactive’ in the XP option, then grub will be lost.

or will '##Yast -generic_mbr ', be written by Yast even if grub stage 1 is in the MBR ?

@Lostfarmer
You could be correct, i am not sure
My menu has
##YaST - generic_mbr

But Flag is on sda1 and grub to MBR.

I have no issues.

So you are saying that with makeactive will switch the flag to sda1 and because grub is to sda3, grub boot will be lost?

In which case @msrikara

use this:

**###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,0)
chainloader +1

or

###Don’t change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,1)
chainloader +1 **

You shouldn’t really need the map function anyway

What do you think @LostFarmer?

##YaST - generic_mbr , would think a generic_mbr was written in the MBR not grub but seems that entire is bogus, basically a bug.

Removing the boot flag from sda3 would only matter if grub stage 1 was installed there “sda3” vice MBR and a generic mbr code was installed. So if YaST output above is wrong , there is no way to be sure without more in depth investigating.

So you are saying that with makeactive will switch the flag to sda1 and because grub is to sda3, grub boot will be lost?
if and only if grub stage 1 is installed on sda3.

Can totally agree with your new XP Title suggestions.

I’ve never had problems not making XP partition active, but others will disagree, so some cases it might be needed.