Suse Grub map?
 

I have finally managed to installSuse 9.2 Pro

But... I have to boot using the installation CD... pretending to do a new install without apci, then when it finds the previous install I boot that instead of repairing or installing etc

If I don't do this this boot doesn't get past Grub, I previously install Ubuntu which gave me the grub 21 error, i.e. it can't find the hard drives... I am using Sata Raid...

However with Suse all I see is :

Boot from CD:
GRUB

So here is the foundation of my question, do I need to configure some kind of grub file in the boot directory (after I have booted using method I mentioned at the beginning)? I have come across a web page that mentioned some code to edit the grub map, but I didn't have exactly the same problem so I didn't want to blindly copy someone else's info

or

Is this a BIOS problem?

I have seen an alleged fix, whereby one enters the bios and sets the master to user and slave to LBA... but this did nothing for me.

My CD drive is attached to IDE Master 1... I tried using it in master 2 and then applying LBA details is the bios... again this had no effect.

I downloaded the latest bios for my motherboard and installed that, still no difference.

Anyway help greatly appreciated

Really could do with some pointers...

I've tried every combo possible in the bios, so I don't think it's that...

A couple of things... The easy way MAY be to again pretend you are installing from scratch and when it sees the linux system it offers a repair option. Try that. I think it has a section on grub.

If that does not work, go ahead and boot in using your disk. Check and see what is in the file. Go to your KDE menu, choose system, file manager, superuser mode. (you'll need your root password!) If you don't have this (superuser mode) go to YAST find it and install it. It will open in Konquerer. Put a / in the address line. Click on boot and look at your device map and menu.lst and see what is in there if anything. You might see the error in there. Since I don't know your HDD setups I can't give you specifics. However in GRUB disks are labeled differently. What would be hda1 in your standard setup is in Grub root (hd0,0)

Login as root in a shell try the following
#cd /mnt/hda1 (This is ASSUMING this is the first partition on your HDD!)
#mkdir boot/grub
#cp /sbin/update-grub ./
#chroot /mnt/hda1 /update-grub

This will prompt you to creat a menu.lst file. Answer yes. It may NOT find the correct root device to use. For example your root linux partition might be /dev/hda3, you have to edit the boot/grub/menu.lst file that was created. For example you will see the line that says
#groot=(hd0,0) you must change it to #groot=(hd0,2).

Rerun update-grub with the correct values
#cd /mnt/hda?(your root linux file)
#chroot /mnt/hda? /update-grub

Then grub-install --root-directory=/mnt/hda? /dev/hda

I have only done this once with a few trieds and got confused on the numbers of devices, but once I figured THAT out it worked.

A couple more things. Remember I've only done this once and it worked. I don't claim to be perfect! Here is a copy of my devicemap
hd0) /dev/hda

and my menu.lst

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 Linux
kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 vga=0x317 splash=silent desktop resume=/dev/hda2 showopts
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
kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3
initrd (hd0,2)/boot/initrd

I have windoughs on the first part of my HDD (I also have a bad spot on my disk there and I don't use it!)
My swap is dev/hda2
My root is dev/hda3
My home is dev/hda4

For more info go to a command line $ and type in info grub.

I also apologize for any spelling errors.

Hope I've helped.