Re: non-fakeraid controllers

[Phillip Susi <psusi@cfl.rr.com>]

Helge Hafting wrote:
> Ability to boot requires bios/bootloader support. Depending on the 
> bios in
> question, this may work for real RAID, fakeraid or even linux sw raid.
>
> You can boot directly from the software raid-1 in linux.  And you can set
> it up so it will boot with one drive failed too - although you may have
> to disconnect the bad drive so the biosdoesn't mistakenly try to load the
> kernel bootloader from the damaged disk.
>
> Having the root filesytem on a damaged array is not a problem - as soon
> as the kernel is running it can activate the raid in degraded mode and
> use the filesystem just fine.  This is no more secure than a 
> single-disk setup
> though, so don't wait too long before you replace the failed drive.
>
> Fakeraid controllers may have bios support for booting, but often
> you'll find that linux have no support for the fake raid.  So you have
> to turn that off and use software raid instead.  An expensive "real raid"
> controller that have linux support, will usually have a bios that support
> booting from the raid too.  Writing to manufacturers should get you the
> details on booting in degraded conditions.
>


Heinz wrote a utility called 'dmraid' which detects and activates 
various hardware fakeraid volumes using the kernel device mapper.  I'm 
using it at home to dual boot ubuntu and winxp ( just in case ) from a 
stripe of two WD 10,000 rpm raptors and it works great.  I'm still 
pushing to get it integrated into dapper.  At this time however, neither 
my hardware, nor dmraid support raid-5.  Hopefully this will change in 
the future.