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 17:53:04 +0200 [thread overview]
Message-ID: <ir62p0$b5o$1@dough.gmane.org> (raw)
In-Reply-To: <4DD65A66.5030904@turmel.org>
Op 20-05-11 14:11, Phil Turmel schreef:
> On 05/20/2011 05:33 AM, Paul van der Vlis wrote:
>>
>> The problem is about detected disks with a defect in the MBR.
>
> This is a crucial point. A BIOS that supports multiple drives in the
> boot order should skip to the next if the MBR cannot be read. But
> the BIOS loses control once the MBR code is executed. If an error is
> encountered in later sectors of the bootloader, there's no way to
> switch to the next drive. This is also true when the BIOS only
> supports dissimilar devices in the boot order.
I think you are right.
> If I had to minimize the chance of this ever biting me, I'd use a CF
> <==> IDE adapter with a DMA capable CF card, and set it up as my boot
> device. And I wouldn't use it for anything but boot. A quick google
> turned up this:
>
> http://www.addonics.com/products/flash_memory_reader/adidecf.asp
In the servers I use, there is normally no place for such a cardreader.
But a low profile PCI card with a CF card on it could do it.
> (Just to show what's out there.) The embedded boards I use
> occasionally have the equivalent of this soldered to their
> motherboards.
>
> The best DMA capable CF cards are usually found in markets that cater
> to industrial designers or to professional photographers.
Do you think the risk of a problem with a CF card (or something like
that) is much lower then the risk of a problem with a harddisk?
And what about booting from an USB stick?
With regards,
Paul van der Vlis.
--
http://www.vandervlis.nl
next prev parent reply other threads:[~2011-05-20 15:53 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
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 [this message]
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='ir62p0$b5o$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).