linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul van der Vlis <paul@vandervlis.nl>
To: linux-raid@vger.kernel.org
Subject: Re: Software raid, booting and bios
Date: Fri, 20 May 2011 10:33:00 +0200	[thread overview]
Message-ID: <ir58vs$9qp$1@dough.gmane.org> (raw)
In-Reply-To: <9067914580344941270@unknownmsgid>

Op 20-05-11 09:19, Simon Mcnair schreef:
> I have not come across a pc which does not allow you to boot a
> secondary drive before... Please can you read  the manual and triple
> check this ?  The only possible reason I can think this would happen
> Is that you're using an add on board and you would configure this from
> a secondary bios. My Dell, Asus, and all other motherboards I've had
> over the past 10 years all allow a second device.

You can select the "boot device priority" where you can choose about
devices types (DVD, harddisk, USB, network) but you can choose only one
SATA disk. Study it, and you will see I am right. I've asked it to my
rackserver-vendor, they say: "that's always the case".

But I think I have had systems in the past, what could do it. An
interesting question is then: how well is it tested?  What when e.g. a
disk boots, and then gives an I/O error? I am looking for a well-tested
way to solve this, and I am willing to pay for it or choose another
hardware vendor for it.

With regards,
Paul van der Vlis.



> Cheers
> Simon
> 
> On 20 May 2011, at 08:15, Paul van der Vlis <paul@vandervlis.nl> wrote:
> 
>> Op 20-05-11 09:03, Simon Mcnair schreef:
>>> Please can you further define what you mean by 'it can become a
>>> problem to boot' ?
>>> Generally this is resolved by having a mbr and boot partition on each
>>> of your mirrored drives so that whichever you use to boot has the
>>> pertinent information to boot the kernel and construct the raid array.
>>> If you have raid 5 with 3 disks you'd have a 3 drive mirror partition
>>> on each disk and a raid 5 set across all three too.
>>
>> In the bios from my machines (Supermicro, Dell) I can select only one
>> drive to boot. Wenn the drive fails, no other disk is tried.
>>
>> I can go into the bios and change the drive when it fails, or I can
>> exchange the disks. But I would like it, when the machine would simple
>> boot even when the first disk is corrupt.
>>
>> With regards,
>> Paul van der Vlis.
>>
>>
>>> I'm not a guru on this and can't provide much knowledge past the
>>> theory and high level ;-)
>>> Simon
>>>
>>> On 20 May 2011, at 07:55, Paul van der Vlis <paul@vandervlis.nl> wrote:
>>>
>>>> Hello,
>>>>
>>>> I use software raid (mdadm). The main problem for me is that when the
>>>> drive with the MBR fails, it can become a problem to boot.
>>>>
>>>> When the bios would use another drive to boot when the first drive
>>>> failes, this problem would be gone. But I don't know rackservers who do
>>>> that. Do you?
>>>>
>>>> Or is there maybe some kind of fake-raid card what uses mdadm to solve
>>>> this problem?
>>>>
>>>> Another way would be to use e.g. an USB device to boot to solve this
>>>> problem. Any experiences with that?
>>>>
>>>> (hmm, I realize that netboot is an option too).
>>>>
>>>> With regards,
>>>> Paul van der Vlis.
>>>>
>>>>
>>>> --
>>>> http://www.vandervlis.nl
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



  reply	other threads:[~2011-05-20  8:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20  7:19 Software raid, booting and bios Simon Mcnair
2011-05-20  8:33 ` Paul van der Vlis [this message]
2011-05-20  8:56   ` Roman Mamedov
2011-05-20  9:33     ` Paul van der Vlis
2011-05-20 10:00       ` Simon McNair
2011-05-21 16:43         ` Paul van der Vlis
2011-05-20 12:11       ` Phil Turmel
2011-05-20 13:22         ` Gordon Henderson
2011-05-20 15:53         ` Paul van der Vlis
2011-05-20 19:32           ` Phil Turmel
2011-05-20 21:27             ` Roberto Spadim
2011-05-20 21:52             ` Brad Campbell
2011-05-21  8:19               ` Leslie Rhorer
2011-05-22  6:31                 ` Simon McNair
2011-05-20 10:04   ` CoolCold
2011-05-20 19:13   ` Ed W
2011-05-21 16:58     ` Paul van der Vlis
2011-05-21 19:57       ` Ed W
  -- strict thread matches above, loose matches on Subject: below --
2011-05-20  6:54 Paul van der Vlis
2011-05-20  7:03 ` Simon Mcnair
2011-05-20  7:14   ` Paul van der Vlis

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='ir58vs$9qp$1@dough.gmane.org' \
    --to=paul@vandervlis.nl \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).