From: Michael Frotscher <infomails@tronserver.dyndns.org>
To: linux-raid@vger.kernel.org
Subject: RAID5 not being reassembled correctly after device swap
Date: Sun, 1 Jul 2007 23:21:48 +0200 [thread overview]
Message-ID: <200707012321.48346.infomails@tronserver.dyndns.org> (raw)
Hello RAID-Experts,
I have three RAID5 consisting of different partitions on 3 disks (Debian
stable) running the root-filesystem on a md (/boot is a separate non-raid
partition) which is running rather nicely. For convenience I plugged all
drives into the first ide controller making them hda, hdb and hdc. So far, so
good. The partitions are flagged "fd", i.e. Linux raid autodetect.
As I have another builtin-ide-controller onboard, I'd like to distribute the
disks for performance reasons, moving hdb to hde and hdc to hdg. The arrays
would then consist of drives hda, hde and hdg.
This should not be a problem, as the arrays should assemble themselves using
the superblocks on the partitions, shouldn't it?
However, when I switch one drive (hdc), the array starts degraded with two
drives present because it is still looking for hdc, which of course now is
hdg. This shouldn't be happening.
Well, then I re-added hdg to the degraded array, which went well and the array
rebuilded itself. I now had healthy arrays consisting of hda, hdb and hdg.
But after a reboot the array was degraded again and the system wanted its hdc
drive.
And yes, I edited /boot/grub/device.map and changed hdc to hdg, so that can't
be the reason.
I seem to be missing something here, but what is it?
--
YT,
Michael
next reply other threads:[~2007-07-01 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 21:21 Michael Frotscher [this message]
2007-07-01 22:12 ` RAID5 not being reassembled correctly after device swap Neil Brown
2007-07-02 6:35 ` Michael Frotscher
2007-07-02 6:50 ` Michael Frotscher
2007-07-03 17:16 ` Michael Frotscher
2007-07-03 17:22 ` Patrik Jonsson
2007-07-03 18:43 ` David Greaves
2007-07-03 19:20 ` Michael Frotscher
2007-07-03 19:29 ` Michael Frotscher
2007-07-04 8:45 ` David Greaves
2007-07-04 16:31 ` Michael Frotscher
2007-07-04 13:35 ` 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=200707012321.48346.infomails@tronserver.dyndns.org \
--to=infomails@tronserver.dyndns.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).