[crazyclown13]

Hello all,

I've recently got a new computer. It has 4 hard disks, 2 of which were setup as RAID 1 (mirrored) using the onboard RAID (these are dev/sda and dev/sdb), and 2 other normal SATA 400 GB disks (sdc and sdd). I went to install Suse Linux 10.1 and the the installer gave me an error mesg, here it is (approx.):
_____________________________________________________
Warning: This system has at least one hard disk with a RAID configuration presented by the BIOS as RAID that is software RAID:
dev/sda dev/sdb

Linux kernel 2.4 supported such systems, but kernel 2.6 does not support all of them.

If you install on these disks, your RAID config and all data on these disks will be lost. Refer to http://portal.suse.com to learn how to migrate to Linux S/W RAID.
_____________________________________________________

I then installed to dev/sdc, and the install completed, and the system rebooted (I took the DVD out first). It went to an "Nvidia boot loader" which failed and exited, and then it just says GRUB on the screen. nothing happens, boot loader doesnt start, it just sits there.

If I start with the install disc in and select "Boot from Hard Drive", it goes to a screen that just says "Booting from local drives" and just hangs there.

I can access the install IF i start the installation cd, and tell it to boot previously installed OS. So I can access the bootloader settings (using Yast Control center). When I did, there were three options of where to place the bootloader: MBR on dev/sda, or dev/sdc or "other" where u could select where to place it. also in detailed bootloader settings I set the drive priority as dev/sdc, dev/sda, dev/sdb, dev/sdd.

I wasnt sure if the boot priority (in the BIOS) is an issue, but the boot priority is:
1) IDE CD LITEON DVDROM DRIVE
2) PCI BEV NVIDIA Boot Agent
3) PCI SCSI NVIDIA MIRROR <---- (I assume its referring to the RAID)
4) IDE 0:
5) IDE 1:
6) IDE 2:
7) IDE 3:

any idea what I'm doing wrong here? I suspect something is wrong with my bootloader or its settings because it just sits there and says GRUB. The install is okay I think since I can access it fine.

Thanks for the help!

[rob.rice]

Try grub or lilo all I could find on the web was problems with NVIDIA Boot Agent (pretty much the same one your having )
You may be able to save your install with a slack install boot disk (don't worry about kernel mismatches ) it may allow you to get the system running so you can run ether grub or lilo
I don't know where you installed suse to but the slack boot disk boot command to use would be something like mount root=/dev/something ro