All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.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 20:13:41 +0100	[thread overview]
Message-ID: <4DD6BD65.7020702@wildgooses.com> (raw)
In-Reply-To: <ir58vs$9qp$1@dough.gmane.org>

On 20/05/2011 09:33, Paul van der Vlis 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".

Hi, what I have done with all my supermicro servers is to buy a tiny USB
flash drive (physically small, not capacity small) - I think what I
bought might be one of the tiny PNY devices, not sure though

The Supermicro boards have internal USB headers mounted on the
motherboard, even with a 1U server I have plenty of room to install my
USB on the MB (could stick them out the back of the server and cable tie
them (or superglue them))

Then I put SysrescueCD on my stick and setup GRUB with a bunch of boot
options.

In my case I'm under the possibly misguided apprehension that my boot
will fail over to the spare disks if one fails. However, I can set the
subsequent failover to be my USB stick also.  I think I have them set at
the moment that the USB stick boots the main drives as normal, but has a
boot menu where I can also boot the sysrescueimage if I need to (I use
this (over IPMI) for initial system installation and serious
maintenance, eg failed grub upgrade or similar).

The only other option that I think the big hosting guys use is to have a
netboot setup which boots everything and can also offer rescue images,
etc.  Beyond my skills to setup for my meagre number of servers, but if
you have more than a couple of machines this could be a very good solution?

For my needs the USB stick option is perfect

Sysrescuecd suits me because all my servers are gentoo based - clearly
it will work for other distros also, but you might want to evaluate
other rescue distros before choosing one?

Good luck

Ed W

  parent reply	other threads:[~2011-05-20 19:13 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
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 [this message]
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=4DD6BD65.7020702@wildgooses.com \
    --to=lists@wildgooses.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.