From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid failing, which command to remove the bad drive?
Date: Sat, 03 Sep 2011 11:45:10 -0700 [thread overview]
Message-ID: <4E6275B6.2000702@vorgon.com> (raw)
In-Reply-To: <20110903121723.GA6123@cthulhu.home.robinhill.me.uk>
On 9/3/2011 5:17 AM, Robin Hill wrote:
> On Sat Sep 03, 2011 at 04:35:39 -0700, Simon Matthews wrote:
>
>> On Fri, Sep 2, 2011 at 8:42 AM, Timothy D. Lenz<tlenz@vorgon.com> wrote:
>>>
>>>>
>>>> How did you install Grub on the second drive? I have seen some
>>>> instructions on the web that would not allow the system to boot if the
>>>> first drive failed or was removed.
>>>>
>>>
>>>
>>> I think this is how I did it, at least it is what I had in my notes:
>>>
>>> grub-install /dev/sda&& grub-install /dev/sdb
>>>
>>> And this is from my notes also. It was from an IRC chat. Don't know if it
>>> was the raid channel or the grub channel:
>>>
>>> [14:02]<Jordan_U> Vorg: No. First, what is the output of grub-install
>>> --version?
>>> [14:02]<Vorg> (GNU GRUB 1.98~20100115-1)
>>> [14:04]<Jordan_U> Vorg: Ok, then run "grub-install /dev/sda&& grub-install
>>> /dev/sdb" (where sda and sdb are the members of the array)
>>>
>>
>> Which is exactly my point. You installed grub on /dev/sdb such that it
>> would boot off /dev/sdb. But if /dev/sda has failed, on reboot, the
>> hard drive that was /dev/sdb is now /dev/sda, but Grub is still
>> looking for its files on the non-existent /dev/sdb.
>>
> The way I do it is to run grub, then for each drive do:
> device (hd0) /dev/sdX
> root (hd0,0)
> setup (hd0)
>
> That should set up each drive to boot up as the first drive.
>
> Cheers,
> Robin
That is how I was trying to do it when I first set it up and was having
problems with it not working. The grub people said not to do it that way
because of a greater potential for problems.
The way I read the line I think I used, "&&" is used to put two commands
on the same line, so it should have done both. But, If I did that from
user vorg instead of user root, I would have needed sudo before both
grub-install commands. I can't remember now what I did.
The second drive is teh one that died and was removed, but I guess if
sda wasn't bootable, it could have been booting off of sdb the whole time.
next prev parent reply other threads:[~2011-09-03 18:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 20:13 Raid failing, which command to remove the bad drive? Timothy D. Lenz
2011-08-26 21:25 ` Mathias Burén
2011-08-26 22:26 ` Timothy D. Lenz
2011-08-26 22:45 ` Mathias Burén
2011-08-26 23:14 ` Timothy D. Lenz
2011-08-26 22:45 ` NeilBrown
2011-09-01 17:51 ` Timothy D. Lenz
2011-09-02 5:24 ` Simon Matthews
2011-09-02 15:42 ` Timothy D. Lenz
2011-09-03 11:35 ` Simon Matthews
2011-09-03 12:17 ` Robin Hill
2011-09-03 17:03 ` Simon Matthews
2011-09-03 17:04 ` Simon Matthews
2011-09-09 22:01 ` Bill Davidsen
2011-09-12 20:56 ` Timothy D. Lenz
2011-09-03 18:45 ` Timothy D. Lenz [this message]
2011-09-05 8:57 ` CoolCold
2011-09-09 21:54 ` Bill Davidsen
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=4E6275B6.2000702@vorgon.com \
--to=tlenz@vorgon.com \
--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).