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: Good hardware for mdadm
Date: Fri, 29 Aug 2014 23:47:02 +0200	[thread overview]
Message-ID: <ltqscm$qp5$1@ger.gmane.org> (raw)
In-Reply-To: <CAH3kUhH=ZdfRtMw+FiRz4c7qkt8UgbHuoTKiUKyq5Uu9AxHBsQ@mail.gmail.com>

Hi Roberto,

op 29-08-14 22:44, Roberto Spadim schreef:
> i use two or more boot disks, if the first raid1 disk don't boot bios
> go to second boot disk, third, etc etc, 

In my opinion this only works when the boot-disk is completely defect or
removed. Not when the data in the MBR on that boot-disk is corrupt.

Or did you test this, or do you have other reasons to believe that your
bios will handle this correct?

With the boot-disk I mean the disk what's in the bios the first disk. So
this could also be the second raid1 disk. Or an USB stick.

> you must write grub to mbr of each disk

Of course.

With regards,
Paul van der Vlis.

> i'm using dell server r410 if i'm not wrong
> 
> 2014-08-29 17:31 GMT-03:00 Paul van der Vlis <paul@vandervlis.nl>:
>> Hello,
>>
>> I like mdadm and I am using it many years. But in my opinion it has one
>> disadvantage: when the MBR of the boot-disk is corrupt, the machine will
>> not boot.
>>
>> A bios could check this. Wait for some kind of signal from Grub or
>> Linux, and after a timeout boot from another disk. But I don't know
>> about a bios with that feature.
>>
>> A PCIe card could do something like that, but I don't know about such a
>> PCIe card.
>>
>> Is there such hardware?
>> What do you do to avoid this problem?
>>
>> With regards,
>> Paul van der Vlis.
>>
>>
>>
>>
>> --
>> Paul van der Vlis Linux systeembeheer, Groningen
>> 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
> 
> 
> 





-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl/


  reply	other threads:[~2014-08-29 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 20:31 Good hardware for mdadm Paul van der Vlis
2014-08-29 20:44 ` Roberto Spadim
2014-08-29 21:47   ` Paul van der Vlis [this message]
2014-08-29 21:52     ` Adam Talbot
2014-08-30  8:25       ` Paul van der Vlis
2014-08-29 22:38     ` Roger Heflin
2014-08-30  8:35       ` Paul van der Vlis
2014-08-30  9:53         ` Roger Heflin
2014-08-30 10:37           ` Paul van der Vlis
2014-08-30 15:56             ` Brad Campbell
2014-08-30  0:44     ` Roberto Spadim
2014-08-30  8:45       ` 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='ltqscm$qp5$1@ger.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).