SuSE 9.3 Pro RAID /boot
I went to install 9.3 SuSE Pro last night. During the installation phase I selected to RAID the two disks (SATA). ( I chose striping, not mirroring, but the message was generic to RAID). A warning message appeared stating that the system may not be directly bootable since I had elected to RAID /boot. Should I make a stand alone partition for /boot, or will I be fine including it in the RAID configuration? This is Linux based RAID, and not through any type of a controller card. -Alain.
I went to install 9.3 SuSE Pro last night. During the installation phase I selected to RAID the two disks (SATA). ( I chose striping, not mirroring, but the message was generic to RAID).
A warning message appeared stating that the system may not be directly bootable since I had elected to RAID /boot. Should I make a stand alone partition for /boot, or will I be fine including it in the RAID configuration?
The problem is that the bootloader needs to know how to load the kernel image. With raid0 (and raid5), it would need to know how the actual file is striped across the two disks to locate the correct disk blocks to read. With raid1 it's simple: ignore the raid and pick either disk to load the file from. Unless the boot loader has somehow learned to undo the striping (dito for raid5), your system won't boot from a raided /boot. My question would be: how does one install a boot loader(s) on a raid0/raid5 system such that the system still boots + runs when removing any one disk? Does yast do this automagically... ? Btw nothing specific to amd64. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
participants (2)
-
Black, Alain
-
Volker Kuhlmann