Wanted to post update.
I got time to come back to this test / system and found out some odd things.
Did a full install of SLES 10 on the system and it addressed the drives as /dev/hda
/dev/hdb
It did note that their was a basic RAID controller but that it was not able to be used.
Tried to complete an 'upgrade' to the system via FC7 (and later a FC8) CD and both only saw
/dev/md0 type Software RAID
/dev/md1 type Software RAID
/dev/md2 type Software RAID
I figured I would see what would happen if I let Fedora address the drives as RAID (/dev/mapper) target and then hope that it was enabled as RAID1
Did the install and formated the partitions. Completed install and set BIOS to accept boot order as: HD0, HD1, Disabled.
Booted system and created a text file.
Shut system off and unplugged power from HD0 drive.
The system booted, Grub loaded and started to boot then hangs with kernel error:
Quote:
<snip>
ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
device-mapper: table: 253:0: mirror: Device lookup failure
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl failed: No such device or address
Unable to access resume device (LABEL=SWAP-pdc_dijfee)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev/ failed: No such file or directory
setuprooot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
|
I assume this means that the drive configuration is some form of RAID0 then by default. But no GUI or interface / menu in BIOS to change definition (nor even a Windows Gui to set it and reload with Linux)
So. I tried Fedoa 5 and it also sees the drives as /dev/mapper (and from shell as raw /dev/sda /dev/sdb) is their ANY way to allow them to see the drives as /dev/hda /dev/hdb like SLES 10 does?
I guess my only option is to use SLES.