From: David Greaves <david@dgreaves.com>
To: Thomas Kenyon <zhadnost@googlemail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help with Failed array
Date: Sun, 12 Jul 2009 12:47:38 +0100 [thread overview]
Message-ID: <4A59CD5A.2070406@dgreaves.com> (raw)
In-Reply-To: <dd404eb00907110046k2bda785fy204c0d23075bda24@mail.gmail.com>
Thomas Kenyon wrote:
> My server at home operates a 4 disk software RAID 5 array which is
> normally mounted at /.
>
> At the moment I am using mdadm v2.6.7.2 (I don't know which version
> built the array).
Also kernel version.
> One of the disks appeared to have developed a fault, an I/O error
> would be produced and the array would rebuild to try and mao round it,
> and once it had finished there'd be another I/O error and it would
> start again.
>
> I marked the drive as faulty, removed it from the array, replaced it
> with a nother drive, replicated the partition map and added it to the
> array.
>
> As expected the drive started being built.
Good
> I'm not sure if it had finished by this point, but another disk
> produced an I/O error which broke the array.
During the rebuild? That doesn't make sense since below it's showing 'clean'.
Are you sure the rebuild didn't finish?
If not then you may need expert support (probably from Neil on monday).
I suggest digging out the logs to see.
> Now I'm trying to recover any data I can from it.
Normally with the data you describe below the /dev/sd[abd]1 partitions would
happily create a degraded array.
However if you are sure sdb is broken then I'd wait.
> When I first try to assemble the array, this message appears in kernel messages.
command?
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
prev parent reply other threads:[~2009-07-12 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd404eb00907110001n177f9fabpb394aac706d3e90@mail.gmail.com>
2009-07-11 7:46 ` Help with Failed array Thomas Kenyon
2009-07-11 14:29 ` Sujit Karataparambil
2009-07-11 14:35 ` Twigathy
2009-07-12 11:47 ` David Greaves [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=4A59CD5A.2070406@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=zhadnost@googlemail.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;
as well as URLs for NNTP newsgroup(s).