I'm having difficulty using GRUB to boot a WinXP partition on my laptop. I've been using Grub to boot a similar configuration that I've been running on this laptop since SuSE 7.x the only difference being that the WinOS was Windows 2000, and not XP. The CDROM that I am installing XP from came with the Thinkpad and is an IBM packaging of the OS. Basically the configuration is (1) swap partition, (1) partition for linux, (1) for the Windows configuration and (1) shared partition that I store files on. Fstab file is listed below. The error message that I'm getting from GRUB is: root (hd0,0) Filesystem type is fat, partition type 0xc chainloader +1 The GRUB config file is also listed below. Any ideas? The Windows partition is the first on the disk, so that shouldn't be a problem. Is it possible that the IBM WinXP installation disk is installing a recovery partition on the HD that is not showing up on the FSTAB and is skewing my mapping? Thanks in advance for wisdom, advice and relevant insights. Glenn Fstab is: (with /dev/hda1 the WindowsXP boot target) /dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C vfat users,gid=users,umask=0002,iocharset=utf8 0 0 /dev/hda4 /windows/D vfat defaults 0 0 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 The GRUB file is: color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,2)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.2 kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 vga=0x317 selinux=0 splash=verbose resume=/dev/hda2 showopts desktop elevator=as initrd (hd0,2)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows root (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX 9.2 kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3 initrd (hd0,2)/boot/initrd
On 18.04.05,18:48, Glenn-KPU wrote:
I'm having difficulty using GRUB to boot a WinXP partition on my laptop.
...
Fstab is: (with /dev/hda1 the WindowsXP boot target)
/dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C vfat users,gid=users,umask=0002,iocharset=utf8 0 0
/dev/hda4 /windows/D vfat defaults 0 0 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
The GRUB file is:
color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,2)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.2 kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 vga=0x317 selinux=0 splash=verbose resume=/dev/hda2 showopts desktop elevator=as initrd (hd0,2)/boot/initrd
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows root (hd0,0) chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX 9.2 kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3 initrd (hd0,2)/boot/initrd
You might try this in your grub file:
title windows
rootnoverify(hd0,0)
chainloader+1
- Jostein
--
Jostein Berntsen
Using, title windows rootnoverify(hd0,0) chainloader+1 will not boot XP. After selecting WinXP from the Grub splash screen I get, rootnoverify (hd0,0) chainloader +1 Thanks for the suggestion. -----Original Message----- From: Jostein Berntsen [mailto:jbernts@broadpark.no] Sent: Tuesday, April 19, 2005 3:47 AM To: suse-linux-e@suse.com; suse-linux-e@lists.suse.com Subject: Re: [SLE] GRUB loader on Thinkpad On 18.04.05,18:48, Glenn-KPU wrote:
I'm having difficulty using GRUB to boot a WinXP partition on my laptop.
...
Fstab is: (with /dev/hda1 the WindowsXP boot target)
/dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C vfat users,gid=users,umask=0002,iocharset=utf8 0 0
/dev/hda4 /windows/D vfat defaults 0 0 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
The GRUB file is:
color white/blue black/light-gray default 0 timeout 8 gfxmenu (hd0,2)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE LINUX 9.2 kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 vga=0x317 selinux=0 splash=verbose resume=/dev/hda2 showopts desktop elevator=as initrd (hd0,2)/boot/initrd
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows root (hd0,0) chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE LINUX 9.2 kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3 initrd (hd0,2)/boot/initrd
You might try this in your grub file:
title windows
rootnoverify(hd0,0)
chainloader+1
- Jostein
--
Jostein Berntsen
Glenn-KPU wrote:
Using,
title windows rootnoverify(hd0,0) chainloader+1
will not boot XP. After selecting WinXP from the Grub splash screen I get,
rootnoverify (hd0,0) chainloader +1
Thanks for the suggestion.
It may be worth your while to find out for sure if your XP CD from IBM is installing an additional partition. If I were you I would at least check with fdisk. It shouldn't bother the boot process, as IBM usually sticks the recovery partition after the Windows install. I have a tri-boot IBM Thinkpad and have not had any of these problems. I am assuming XP installed without complaining? If you can start from scratch wipe the drive, install XP first, then Linux. At the time I did this is was strongly recommended that Windows gets installed first (Not just on the first partition, but before Linux). I have had not problems with grub or lilo. You may try to switch boot loaders, but I prefer grub. I am sorry I can't be more help, hopefully this provides a little insight. - James W.
Thanks James, I'm suspicious that there may have been a recovery partition installed by the IBM XP cd, but it seems that it would show up in fstab as well as in YAST. I did install XP first on a wiped HD: it booted fine with no problems. I then ran YAST in the Suse 9.2 dist, this compressed the WinXP Fat32 partition from 37gb down to 15gb. I've tried Lilo as well with no luck. It really is a bit of a puzzle as I've been running Win2k-Linux-Shared disk configutrations on this machine (an Thinkpad T30) and others for several years with no boot problems. Thanks for your suggestions. Glenn -----Original Message----- From: James Wright [mailto:jwright@blackriverproduce.com] Sent: Tuesday, April 19, 2005 8:05 AM To: Suse List Subject: Re: [SLE] GRUB loader on Thinkpad Glenn-KPU wrote:
Using,
title windows rootnoverify(hd0,0) chainloader+1
will not boot XP. After selecting WinXP from the Grub splash screen I get,
rootnoverify (hd0,0) chainloader +1
Thanks for the suggestion.
It may be worth your while to find out for sure if your XP CD from IBM is installing an additional partition. If I were you I would at least check with fdisk. It shouldn't bother the boot process, as IBM usually sticks the recovery partition after the Windows install. I have a tri-boot IBM Thinkpad and have not had any of these problems. I am assuming XP installed without complaining? If you can start from scratch wipe the drive, install XP first, then Linux. At the time I did this is was strongly recommended that Windows gets installed first (Not just on the first partition, but before Linux). I have had not problems with grub or lilo. You may try to switch boot loaders, but I prefer grub. I am sorry I can't be more help, hopefully this provides a little insight. - James W. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Glenn-KPU wrote:
Thanks James, I'm suspicious that there may have been a recovery partition installed by the IBM XP cd, but it seems that it would show up in fstab as well as in YAST. I did install XP first on a wiped HD: it booted fine with no problems. I then ran YAST in the Suse 9.2 dist, this compressed the WinXP Fat32 partition from 37gb down to 15gb. I've tried Lilo as well with no luck.
It really is a bit of a puzzle as I've been running Win2k-Linux-Shared disk configutrations on this machine (an Thinkpad T30) and others for several years with no boot problems.
Thanks for your suggestions.
Glenn
Have you tried using the XP CD to boot to the recovery console? You can then type FIXMBR to fix the master boot record for XP. Then you will need to reinstall Grub or Lilo. For that you should be able to boot with your Suse CD/DVD. That's all I can think of at the moment. Good luck in any case. - James W
Glenn-KPU wrote:
Using,
title windows rootnoverify(hd0,0) chainloader+1
will not boot XP. After selecting WinXP from the Grub splash screen I get,
rootnoverify (hd0,0) chainloader +1
Work here with Winblows XP Pro. title Windows root (hd0,0) <- Primary/Master/Partition 1 chainloader +1 -- 73 de Donn Washburn Hpage: " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email: " n5xwb@hal-pc.org " 307 Savoy St. HAMs: " n5xwb@arrl.net " Sugar Land, TX 77478 LL# 1.281.242.3256 " http://counter.li.org " #279316
participants (4)
-
Donn Washburn -
Glenn-KPU -
James Wright -
Jostein Berntsen