Having problems dual booting Suse 11.3 and Windows XP
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Having problems dual booting Suse 11.3 and Windows XP
I'm trying to dual boot Suse11.3 and Windows XP. I can boot up into linux, but when I select Windows from Grub, it says the following.
rootnoverify(hd0,1)
chainloader +1
remove disks or other media
Press any key to restart
I then press a key and then it says
(hd0,5)/boot/message not found
Here is some configuration information.
device.map
(fd0) /dev/fd0
(hd0) /dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445
(hd1) /dev/disk/by-id/ata-Maxtor_6Y120P0_Y31S6XEE
(hd2) /dev/disk/by-id/ata-ST3320620AS_3QF0XSH2
linux-v6en:/boot/grub # cat menu.lst
# Modified by YaST2. Last modification on Sun Jun 5 17:09:49 MST 2011
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
gfxmenu (hd0,5)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.3 - 2.6.34.8-0.2
root (hd0,5)
kernel /boot/vmlinuz-2.6.34.8-0.2-default root=/dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445-part6 resume=/dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445-part5 splash=silent quiet showopts vga=0x345
initrd /boot/initrd-2.6.34.8-0.2-default
My windows boot was working prior to installing 11.3, I had 11.0 installed before. My guess is that somehow the ms bootloader got corrupted, but I'm not sure. Any help would be appreciated. Thanks.
I really can't tell which windows partition contains your main OS. If it is
/dev/disk/by-id/ata-ST3320620AS_3QF0XSH2-part5 then the following should work for the windows entry in grub
Code:
title Windows XP
rootnoverify (hd2,4)
map (hd0) (hd2)
map (hd2) (hd0)
chainloader +1
Please state which partition your windows XP OS resides on.
============================= Boot Info Summary: ===============================
=> Grub Legacy (v0.97) is installed in the MBR of /dev/sda and looks on boot
drive #2 in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> Grub Legacy (v0.97) is installed in the MBR of /dev/sdb and looks on the
same drive in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> Windows is installed in the MBR of /dev/sdc.
File system: vfat
Boot sector type: -
Boot sector info: According to the info in the boot sector, sda5 starts
at sector 63. But according to the info from fdisk,
sda5 starts at sector 16225713. "63" and "2048" are
quite common values for the starting sector of a
logical partition and they only need to be fixed when
you want to boot Windows from a logical partition.
Operating System:
Boot files:
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: -
Boot sector info: According to the info in the boot sector, sda6 starts
at sector 63. But according to the info from fdisk,
sda6 starts at sector 75987513. "63" and "2048" are
quite common values for the starting sector of a
logical partition and they only need to be fixed when
you want to boot Windows from a logical partition.
Operating System:
Boot files:
sda7: __________________________________________________________________________
File system: vfat
Boot sector type: -
Boot sector info: According to the info in the boot sector, sda7 starts
at sector 63. But according to the info from fdisk,
sda7 starts at sector 170449713. "63" and "2048" are
quite common values for the starting sector of a
logical partition and they only need to be fixed when
you want to boot Windows from a logical partition.
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: vfat
Boot sector type: Windows XP: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files:
sdc1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows XP
Boot sector info: According to the info in the boot sector, sdc5 starts
at sector 63.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
--------------------------------------------------------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /NoExecute=OptIn
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
# Modified by YaST2. Last modification on Sun Jun 5 17:09:49 MST 2011
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
gfxmenu (hd0,5)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.3 - 2.6.34.8-0.2
root (hd0,5)
kernel /boot/vmlinuz-2.6.34.8-0.2-default root=/dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445-part6 resume=/dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445-part5 splash=silent quiet showopts vga=0x345
initrd /boot/initrd-2.6.34.8-0.2-default
I tried:
rootnoverify (hd0,0) and that does not work. It just prints out the command and then hangs.
I believe the partition I'm trying to be booting based on the results of the boot_info_script is:
/dev/sdb2 * 30,346,848 70,300,439 39,953,592 c W95 FAT32 (LBA).
That is also this hard drive:
/dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445-part2 /windows/C vfat users,gid=users,umask=0002,utf8=true 0 0
Currently my device.map file doesn't seem to match the output of the script. It has this:
(hd0) /dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445
(hd1) /dev/disk/by-id/ata-Maxtor_6Y120P0_Y31S6XEE
(hd2) /dev/disk/by-id/ata-ST3320620AS_3QF0XSH2
Yes there inconsistencies there, but that can happen. Did you run it from your OpenSuse system or a liveCD ?.
The partition with ntldr is the one you have to boot for Windoze.
You should learn to use the vbcode tags # or quote to enclose log lists or data. This will make your posts cleaner therefore easier to read. # & quote are at the top of the reply window.
The previous results were run from the booted OpenSuse.
Here are the results run from a live cd.
Quote:
Boot Info Script 0.60 from 17 May 2011
============================= Boot Info Summary: ===============================
=> Grub Legacy (v0.97) is installed in the MBR of /dev/sda and looks on boot
drive #2 in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> Grub Legacy (v0.97) is installed in the MBR of /dev/sdb and looks on the
same drive in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> Windows is installed in the MBR of /dev/sdc.
File system: vfat
Boot sector type: -
Boot sector info: According to the info in the boot sector, sda5 starts
at sector 63. But according to the info from fdisk,
sda5 starts at sector 16225713. "63" and "2048" are
quite common values for the starting sector of a
logical partition and they only need to be fixed when
you want to boot Windows from a logical partition.
Operating System:
Boot files:
sda6: __________________________________________________________________________
File system: vfat
Boot sector type: -
Boot sector info: According to the info in the boot sector, sda6 starts
at sector 63. But according to the info from fdisk,
sda6 starts at sector 75987513. "63" and "2048" are
quite common values for the starting sector of a
logical partition and they only need to be fixed when
you want to boot Windows from a logical partition.
Operating System:
Boot files:
sda7: __________________________________________________________________________
File system: vfat
Boot sector type: -
Boot sector info: According to the info in the boot sector, sda7 starts
at sector 63. But according to the info from fdisk,
sda7 starts at sector 170449713. "63" and "2048" are
quite common values for the starting sector of a
logical partition and they only need to be fixed when
you want to boot Windows from a logical partition.
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: vfat
Boot sector type: Windows XP: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files:
sdc1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows XP
Boot sector info: According to the info in the boot sector, sdc5 starts
at sector 63.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
--------------------------------------------------------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /NoExecute=OptIn
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
# Modified by YaST2. Last modification on Sun Jun 5 17:09:49 MST 2011
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
gfxmenu (hd0,5)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.3 - 2.6.34.8-0.2
root (hd0,5)
kernel /boot/vmlinuz-2.6.34.8-0.2-default root=/dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445-part6 resume=/dev/disk/by-id/ata-WDC_WD360GD-75GHA0_WD-WMAH91258445-part5 splash=silent quiet showopts vga=0x345
initrd /boot/initrd-2.6.34.8-0.2-default
No volume groups found
mdadm: No arrays found in config file or automatically
Looking at this I would thing the following should allow Windows to boot but it doesn't.
title Windows
rootnoverify (hd0,1)
map(hd1) (hd0)
map(hd0) (hd1)
chainloader +1
The previous results were run from the booted OpenSuse.
Here are the results run from a live cd.
Looking at this I would thing the following should allow Windows to boot but it doesn't.
title Windows
rootnoverify (hd0,1)
map(hd1) (hd0)
map(hd0) (hd1)
chainloader +1
You only need to use the map commands if windows is on a drive other than hd0 which is not the case in your above example.
As syg00 stated if you are trying to boot windows on sda1 it would be (hd0,0) since grub-0.97 starts the partition numbering at 0.
The question is: have you changed the boot order around in BIOS since you installed?
File system: vfat
Boot sector type: Windows XP: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP Boot files:
The only windows partition that has boot files is sda1
I used to have windows installed on sda1 as stated above, but last year I ended up having to re-install it, and I installed it to Sdb2, hence that's why /dev/sdb2 contains the windows/c. Windows booted but it was always funky, I had to hit a key after grub kicked it off for it to continue. Although I'm not really sure why the partition at /dev/sdb2 does not contain the windows boot files?
I had heck on one system where I reloaded. In the process I used fixboot andor fixmbr for some reason. It then put the windows install and a few of the core nt files on different disks. It then fooled me for a few days on a linux install. Could this be what is going on? Your boot files are on sda1 and your OS is on sda2?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.