Hello. I just bought a new hard drive to replace my old one that suse was on. I also have windows on a seperate hard drive. In suse 9.3 the windows drive is viewable, I can access the files, but I can't boot to it from the menu in grub, when I try I get

"root (hd1,0)
Filesystem type unknown, Partition
Type 0x7
chainloader +1

How can I fix this problem? I tried running the repair utility on the suse installation dvd, but it had no effect. I should mention on my new drive i installed suse with a /boot partition, on that same drive, nothing is on the windows drive exept windows. thanks

Googling, I found that you want to use "rootnoverify" instead of root.

ok, how do I use norootverify in grub? Do I have to add it in a configuration file or something? when I get that error screen I don't think I can type anything I have to ctrl alt del out of there

This is what I have in my boot text file for grub, the suse repair utility did not change this configuration.


# Modified by YaST2. Last modification on Sat Jul 16 20:44:12 UTC 2005

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,0)/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 9.3
kernel (hd0,0)/vmlinuz root=/dev/hda2 vga=0x317 selinux=0 splash=silent acpi=off resume=/dev/hda3 showopts
initrd (hd0,0)/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 -- SUSE LINUX 9.3
kernel (hd0,0)/vmlinuz root=/dev/hda2 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0 3
initrd (hd0,0)/initrd

I'm still unable to solve my dual boot problem. I googled a bit about grub but I can't get my windows drive to load. My windows drive is on secondary master, I think before it was on cable select but not sure. I tried running the suse repair utility on the dvd several times but it has no effect. I tried editing the grub menu but without luck. I'm pasting my grub file in here, hopefully the problem has an obvious solution. the windows drive is listed as hdc1, the linux boot partition is hda1, and the root is hda2

(hd1) /dev/hdc
(hd0) /dev/hda

# Modified by YaST2. Last modification on Sat Jul 16 20:44:12 UTC 2005

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,0)/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 9.3
kernel (hd0,0)/vmlinuz root=/dev/hda2 vga=0x317 selinux=0 splash=silent acpi=off resume=/dev/hda3 showopts
initrd (hd0,0)/initrd

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

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

Because some OS like windows boots only from the first drive,you should map your windows drive to the first drive,using map
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
root (hd1,0)
rootnoverify (hd1,0)
makeactive
chainloader +1
many guys may be confused by "root" and "rootnoverify",root set the device which contains OS image,and attempting to mount it,while rootnoverify is similar to root,but not mounting the device . I hope this will work for u.

Hey sakur, your suggestion was bang on, it worked right away. Many thanks, I know what to do now if this happens again.

,if u know some about eDirectory,or want 2 install, we can share the knowledge,im interested in that .