From: Troy Telford <ttelford.groups@gmail.com>
To: linux-raid@vger.kernel.org
Subject: RAID-6 disk superblock issue
Date: Tue, 13 Dec 2011 15:42:20 -0700 [thread overview]
Message-ID: <jc8kca$mf$1@dough.gmane.org> (raw)
I have a RAID-6 array I'm having trouble with:
md2 : active raid6 sdl1[6] sdh1[0] sdm1[5] sdk1[3] sdj1[2] sdi1[1]
1953535488 blocks level 6, 128k chunk, algorithm 2 [6/5] [UUUU_U]
[>....................] recovery = 0.0% (27164/488383872)
finish=599.1min speed=13582K/sec
- When the system boots (or when I attempt to build the array), I get a
message that /dev/sdl and /dev/sdl1 have the same superblock, and that
I should zero one.
- So, I zero the superblock using 'mdadm --zero-superblock /dev/sdl (or
/dev/sdl1; doesn't matter which I use).
- I then re-add the device to the array (and the RAID-6 array recovers,
as above.)
- The next time I boot, I get the exact same error message.
- It doesn't seem to matter which (between the device or the partition)
that I zero the superblock on. I get the same error message at boot
(when the drive is being assembled).
- Since it's redundant data anyway, I've tried dd'ing from /dev/zero
over the drive, repartitioning the drive, and then adding the drive to
the array. Same behavior.
- My mdadm.conf just has the array itself, and the array's UUID. It
doesn't explicitly list devices.
So what am I missing? There's got to be a way I can get the array to
assemble at boot, instead of having to manually --zero-superblock every
time.
--
Troy Telford
next reply other threads:[~2011-12-13 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 22:42 Troy Telford [this message]
2011-12-14 19:01 ` RAID-6 disk superblock issue Phil Turmel
2011-12-14 21:41 ` Troy Telford
2011-12-14 22:04 ` Mark Knecht
2011-12-14 22:08 ` Troy Telford
2011-12-14 22:07 ` NeilBrown
2011-12-14 22:14 ` Troy Telford
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='jc8kca$mf$1@dough.gmane.org' \
--to=ttelford.groups@gmail.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).