From: "John Stoffel" <stoffel@lucent.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: degraded raid5 at bootup
Date: Fri, 13 Aug 2004 16:19:29 -0400 [thread overview]
Message-ID: <16669.8785.592904.686201@gargle.gargle.HOWL> (raw)
In-Reply-To: <411D1B3E.9050306@tupshin.com>
Tupshin> I have a 5 disk raid5 using autodetect partitions. If I have
Tupshin> a clean array when I shut down, I always have a degraded
Tupshin> array with one disk removed when I boot back up. Below I
Tupshin> include the relevant dmesg output. hdi1 is always the
Tupshin> problem. If I do a "mdadm -a /dev/md0 /dev/hdi1", then the
Tupshin> array rebuilds without a problem, and runs clean until I
Tupshin> reboot again. Any suggestions?
Are all your disks setup with partition 1 setup as 'Linux Raid'
properly? Check /dev/hdi using 'cfdisk' and see what partition 1 has
for a type.
Tupshin> Kernel is 2.6.8-rc2-mm2, but I've tried it with a few other
Tupshin> recent kernels (mm and not) and all have the same
Tupshin> problem. Distro is Debian Sid.
Tupshin> -Tupshin
Tupshin> md: considering hdl1 ...
Tupshin> md: adding hdl1 ...
Tupshin> md: adding hdj1 ...
Tupshin> md: hdi1 has different UUID to hdl1
This is a key line here! You need to update the superblocks on the
raid elements to have the proper stuff. My personal system is down,
so I can't tell you the exactl command, but make sure you've got the
same setup on all five disks.
I assume they're all the same size, right? If so, just make sure
they're all the same partition stuff, etc.
If need be, reboot your system and zero out the first few blocks on
/dev/hdi (say 32 or 64 blocks) and then re-partition the disk, and
then make sure partition 1 is set to Linux Raid.
Then use the mdadm command to update the superblocks.
John
prev parent reply other threads:[~2004-08-13 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 19:49 degraded raid5 at bootup Tupshin Harper
2004-08-13 20:19 ` John Stoffel [this message]
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=16669.8785.592904.686201@gargle.gargle.HOWL \
--to=stoffel@lucent.com \
--cc=linux-raid@vger.kernel.org \
--cc=tupshin@tupshin.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