linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Colin McDonald <ce.mcdonald@gmail.com>
To: Paul Clements <paul.clements@steeleye.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 1 on a server with possible mad mobo
Date: Tue, 8 Mar 2005 19:48:03 -0500	[thread overview]
Message-ID: <bbfa528905030816484108fa7@mail.gmail.com> (raw)
In-Reply-To: <422DF363.6090105@steeleye.com>

Thanks for the suggestions.

Let me ask an additional question.

Is it a bad idea to write the grub to a software mirror. Is it written
to a specific disk when this is done?

If I had a corrupt boot loader or boot sector and i needed to rescue.
Would I point to the md device or one of the disks (or both).

TIA


On Tue, 08 Mar 2005 13:48:03 -0500, Paul Clements
<paul.clements@steeleye.com> wrote:
> Colin McDonald wrote:
> 
> > Without taking up to much of y'alls time, what would be the best
> > solution for moving the RAID array over to a new box?
> 
> > 2. Try to boot off of the disks after they have been transferred into
> > the new machine? I know this will cause all kinds of problems with
> > kernel/devices, etc and probably won't work.
> 
> Actually, I've done this a couple of times with both Red Hat and SUSE
> and it's worked surprisingly well. With the kernel being mostly modular
> and the hardware detection/configuration utilities being pretty advanced
> these days, it's not much of a problem. (I had a minor issue with SUSE
> doing this sort of thing because the MAC address of the NIC was
> different, so the network stuff was not getting configured. On Red Hat
> [and hopefully Fedora is still the same] you should get prompted at
> bootup if there is any hardware to add or remove.)
> 
> Especially if you're wanting to keep the system configuration exactly
> the same, this may be the way to go, rather than trying to reconfigure
> everything exactly the way you had it before.
> 
> And of course if, after booting the new system with the old disks, you
> find that things are not quite right, you can always re-install at that
> point...
> 
> --
> Paul
>

  reply	other threads:[~2005-03-09  0:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 18:19 RAID 1 on a server with possible mad mobo Colin McDonald
2005-03-08 18:48 ` Paul Clements
2005-03-09  0:48   ` Colin McDonald [this message]
2005-03-09  1:08     ` berk walker
2005-03-09  2:14     ` Mike Hardy

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=bbfa528905030816484108fa7@mail.gmail.com \
    --to=ce.mcdonald@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=paul.clements@steeleye.com \
    /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).