From: Louis-David Mitterrand <vindex@apartia.org>
To: linux-raid@vger.kernel.org
Subject: recovering after a /dev/sda failure on raid1
Date: Thu, 1 Aug 2002 16:49:22 +0200 [thread overview]
Message-ID: <20020801144922.GA5284@apartia.org> (raw)
Hi,
I have a root raid1 partition on /dev/sda1 & /dev/sdb1 (swap on
/dev/sda2 & /dev/sdb2). The server boots directly from the raid
partition.
Now /dev/sda1 and /dev/sda2 have both failed and been removed from the
array and I am getting ready to replace the disk tonight.
What is the best way to proceed to minimize downtime?
My concern is that if I power down and replace /dev/sda the machine
won't be able to reboot without a rescue CD (lilo.conf has root=/dev/md0
and boot=/dev/md0) or will it?
When the bios (Dell Poweredge 1500) will try /dev/sda's mbr and fail,
will it then automatically try /dev/sdb?
Or should I swap /dev/sdb on the scsi ribbon to have it take the first
place and thus become /dev/sda or will this just confuse the kernel
raid driver? (the letter on scsi drives is dependent on their place on
the ribbon cable, isn't it?)
Alternatively I was thinking of booting with a rescue CD (after
replacing /dev/sda) with the "root=/dev/md0", creating my partitions,
running lilo and rebooting into production for final reconstruction.
Would that be the safest bet?
Thanks in advance for your insight, cheers,
--
vindex@apartia.org
next reply other threads:[~2002-08-01 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <message from Louis-David Mitterrand on Monday August 5>
2002-08-01 14:49 ` Louis-David Mitterrand [this message]
2002-08-02 21:26 ` recovering after a /dev/sda failure on raid1 Neil Brown
2002-08-02 23:03 ` Danilo Godec
2002-08-05 9:34 ` Louis-David Mitterrand
2002-08-05 9:26 ` Louis-David Mitterrand
2002-08-05 12:15 ` Neil Brown
2002-08-05 12:36 ` Louis-David Mitterrand
2002-08-05 18:38 ` Maurice Hilarius
2002-08-05 18:35 ` Maurice Hilarius
2002-08-06 8:36 ` Louis-David Mitterrand
2002-08-06 19:51 Cress, Andrew R
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=20020801144922.GA5284@apartia.org \
--to=vindex@apartia.org \
--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).