-   Linux - Distributions (
-   -   problem using grub/lilo to boot windows with suse 9.1 (

jcasanue 06-27-2004 08:01 AM

problem using grub/lilo to boot windows with suse 9.1
Hi there,
I have just installed suse 9.1 and grub to have both linux and windows on my machine.

I have two hdds:
hda (IDE which has suse 9.1)
hde (SATA which has windows)

grub is installed in hda, and linux boots fine... The problem is that when I boot
windows grub gives me an error saying "unrecognised file system type"
However all the grub settigna are correct... and If I disconnect hda, windows boots up fine...

any ideas?

CartersAdvocate 06-27-2004 06:34 PM

We'll need more information in order to help you...the main thing would be posting your grub.conf file so we can make sure there aren't any mistakes in it

jcasanue 06-28-2004 03:50 PM

Hi there....
I actually have 3 hdds as follows
hda: IDE drive with suse 9.1
hde and hdg: SATA drives with windows

I installed suse 9.1 on the IDE drive (hda) and installed grub in it aswell.
linux boots perfectly, but when I try to boot windows, I get this error:

root (hd1,0)
filesystem type unknows, partition type 0x7

if I disconnect the hda drive, when windows boot perfectly (without grub)

here are the grub settings:
boot Loader Location IDE, /dev/hda (MBR)
Disk Order /dev/hda, /dev/hde, /dev/hdg
Default section Linux
Available sections Linux (default), Windows, Failsafe
Activare Boot Loader Partition No
Replace code in MBR Leave untouched
Back uo Affected Disk Areas No
Add Saved MBR to Boot Loader Menu No
Save Method Save only changed files

and here are the grub config files:

(hd0) /dev/hda
(hd1) /dev/hde
(hd2) /dev/hdg

# Modified by YaST2. Last modification on Sun Jun 27 15:25:20 2004

gfxmenu (hd0,1)/boot/message
timeout 8
default 0

###Don't change this comment - YaST2 identifier: Original name: Linux###
title Linux
kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=0x31a splash=silent desktop resume=/dev/hda1 showopts
initrd (hd0,1)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: Windows###
title Windows
root (hd1,0)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: Failsafe###
title Failsafe
kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 3
initrd (hd0,1)/boot/initrd

root (hd0,1)
install --stage2=/boot/grub/stage2 /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst

if anyone has any idea, please help

CartersAdvocate 06-28-2004 08:50 PM


Originally posted by jcasanue
root (hd0,1)
install --stage2=/boot/grub/stage2 /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst

Hmm, I'm not an expert on grub, I usually use lilo, so I may be wrong, but it seems like you should have more in your /etc/grub.conf than this...something along the lines of:

rootnoverify (hd1,0)
chainloader +1

I saw that you listed that in your /boot/grub/menu.1st which YaST put in there, so I'm not sure if that means you don't need it in the grub.conf, but on Gentoo where I use grub, I have to put that in my grub.conf in order to boot my windows

jcasanue 07-14-2004 01:17 PM

Hi there... I finally solved the problem!

I had to add two lines in the /boot/grub/menu.lst file, in the windows section, which
now becomes:

###Don't change this comment - YaST2 identifier: Original name: Windows###
title Windows
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
chainloader +1

J.W. 07-14-2004 06:58 PM

jcasanue -- congrats on solving the problem and Welcome to LQ! -- J.W.

All times are GMT -5. The time now is 09:37 PM.