public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: alex-lists-linux-kernel@yuriev.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: non-fakeraid controllers
Date: Tue, 07 Feb 2006 08:58:47 +0100	[thread overview]
Message-ID: <43E85337.1090001@aitel.hist.no> (raw)
In-Reply-To: <20060207015126.GA12236@s2.yuriev.com>

alex-lists-linux-kernel@yuriev.com wrote:

>Hi,
>
>	This is not an attempt to start a religious flamewar about what is
>RAID vs. what is softraid vs. what is fakeraid. 
>
>	Does anyone has a list/refence/etc on reasonably modern SCSI
>controllers (at least u160) in a non-fakeraid way i.e. the way that would
>allow linux to boot from a RAID protected disk array when one of the drives
>in the array failed even if the root filesystem is located on the same
>array?
>  
>
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.

Helge Hafting

  reply	other threads:[~2006-02-07  7:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  1:51 non-fakeraid controllers alex-lists-linux-kernel
2006-02-07  7:58 ` Helge Hafting [this message]
2006-02-07 15:45   ` Phillip Susi
2006-02-07 17:39     ` Wakko Warner
2006-02-07 18:25       ` Phillip Susi
2006-02-07 22:45         ` Wakko Warner
2006-02-07  9:30 ` Christoph Hellwig
2006-02-07 12:08 ` Alan Cox
2006-02-07 22:57 ` Jesper Juhl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43E85337.1090001@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=alex-lists-linux-kernel@yuriev.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox