All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Guy Watkins <linux-raid@watkins-home.com>
Cc: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: Re: Upgraded grub, now confused about mirrored /boot
Date: Tue, 02 Nov 2010 15:23:46 +0000	[thread overview]
Message-ID: <4CD02D02.3060701@anonymous.org.uk> (raw)
In-Reply-To: <9770F687FAE544F295B1A22155F2BBA6@m5>

On 02/11/2010 06:11, Guy Watkins wrote:
> Hello,
>
> 	I upgraded my system from Red Hat FC10 to FC11.  The instructions
> say to run this command:
> /sbin/grub-install BOOTDEVICE
>
> And if it fails, run this:
> /sbin/grub-install --recheck /dev/sda
>
> However, my boot disk (/boot) is mirrored on 4 disks and I think (or hope)
> all 4 are bootable.  The mirrors were created at install time many years ago
> when I installed FC5.  No idea if it really made more than 1 bootable.  I
> have assumed that if sda failed, I could still boot from sdb, sdc or sdd.
> And I do understand that I might need to remove sda first, depending on the
> type of failure.  Lucky for me, no drive has failed yet and I don't recall
> if I tested booting off of any other disks.
>
> I do have this on the kernel line:
> md-mod.start_dirty_degraded=1
>
> So, what do I do now?  Run that command on all 4 disks?  Or run it on
> /dev/md0?

I don't know which grub version you get in FC10/11, but in CentOS 5 
(with grub 0.97), grub-install is a clever little script which does all 
the work for you, so you just
   /sbin/grub-install /dev/md0
and it will install grub on all of /dev/md0's constituent drives and 
generally get everything right.

You should be fine with metadata 0.90 or 1.0 as both store the 
superblock at the end of the device. 1.1 and 1.2 probably won't work 
because their constituent partitions don't look like bare filesystems.

What actually happens is that the BIOS boots off the first live disc, 
and so does grub 0.97, neither has any inherent support for RAID but 
they don't have to if it's a RAID-1 mirror because both (or all) parts 
of the mirror can be used on their own, at least for reading enough to 
boot with.

You should probably test booting up with your first drive disconnected, 
just to be sure!

Cheers,

John.


  parent reply	other threads:[~2010-11-02 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 13:41 reshape success story Florian Dazinger
2010-10-31 14:19 ` John Robinson
2010-10-31 15:46   ` Neil Brown
2010-11-02  1:14     ` John Robinson
2010-11-02  6:11       ` Upgraded grub, now confused about mirrored /boot Guy Watkins
2010-11-02 14:20         ` Leslie Rhorer
2010-11-02 15:23         ` John Robinson [this message]
2010-11-05  1:42           ` Guy Watkins
2010-11-03  3:11       ` reshape success story Neil Brown

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=4CD02D02.3060701@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-raid@watkins-home.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 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.