linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon McNair <simonmcnair@gmail.com>
To: Paul van der Vlis <paul@vandervlis.nl>
Cc: linux-raid@vger.kernel.org
Subject: Re: Software raid, booting and bios
Date: Fri, 20 May 2011 11:00:35 +0100	[thread overview]
Message-ID: <4DD63BC3.3010009@gmail.com> (raw)
In-Reply-To: <ir5ci1$uc6$1@dough.gmane.org>

Paul,
Please can you get some digital camera shots (resize them, low res and 
compress them) of the bios screen (or screen grabs if it's via a LOM).  
I'm especially interested in knowing if in the device listing there are 
two or more hard disks in the first place (as if there is only one disk 
I'd not be surprised at getting only one set of options).

Can you ask you rack space vendor the specific question 'how do I set up 
a secondary boot device ?".

Simon

On 20/05/2011 10:33, Paul van der Vlis wrote:
> Op 20-05-11 10:56, Roman Mamedov schreef:
>> On Fri, 20 May 2011 10:33:00 +0200
>> Paul van der Vlis<paul@vandervlis.nl>  wrote:
>>
>>> 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".
>> How about just not buying crappy hardware from this lying vendor anymore.
>> http://ompldr.org/vOHB6Zw/bios4.jpg<- this is present in majority of
>> motherboard BIOSes since forever.
> Interesting. From what brand server is this?
>
>>> 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.
>> Yes, I think it is conceivable that if a disk fails in a 'bad' way, i.e. by
>> locking up on reads, or reading the first sector but not the next ones it can
>> prevent the system from booting even with this priority system. I don't know
>> if chances of that are high, considering that quite often disks fail by also
>> ceasing to be detectable in BIOS, in which case your boot-up would proceed
>> normally.
> The problem is about detected disks with a defect in the MBR.
>
> With regards,
> Paul van der Vlis.
>
>
> --
> 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 10:00 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 [this message]
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=4DD63BC3.3010009@gmail.com \
    --to=simonmcnair@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=paul@vandervlis.nl \
    /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).