From: NeilBrown <neilb@suse.de>
To: Michael Samer <michael.samer@epos-cat.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm error
Date: Wed, 18 Dec 2013 09:51:57 +1100 [thread overview]
Message-ID: <20131218095157.7244c651@notabene.brown> (raw)
In-Reply-To: <52AF6915.7010806@epos-cat.de>
[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]
On Mon, 16 Dec 2013 21:56:53 +0100 Michael Samer <michael.samer@epos-cat.de>
wrote:
> Hello Mr Brown
> you might remember helping me end of 2012 with an mdadm error
> (lost/inactive volume).
> This year I've been proactive in advertising your name to our yearly
> donation list. My collegue Lisa Braunert should already have contacted
> you and booked 250EUR at your account. Hope this was/is an adequate
> donation for the two very helpful mails :-)
??? Sorry, don't know what you are talking about.
I'm not really interested in receiving donations. If you have spare money,
please give it to a local children's charity.
>
> Currently I've the a mdadm system here again with unmountable volume due
> to disk (timeout and badblocks) failures. I transfered the disk already
> to new HDs.
>
> Question: for this is a RAID5 the only redundant disk was lost to a
> timeout sometime in the past and the second (/dev/sdf) had tons of
> BadBlocks in the first and last 5MBs. I reconstructed the partition
> table (as all 8 disks are build the same way), but how could I glue the
> mdadm system together again. After that I'd start an integrity check of
> the mdadm volume and afterwards an fsck.
>
> I attach the "mdadm --examine /dev/sd*" so you might consider looking
> upon my problem
This is a very vague problem description. I'm not really sure what you are
asking beyond "It doesn't work, please help"...
You mentioned RAID5 and there only seems be be one RAID5 in the mdadm
--examine output, on /dev/sd[aceh]3
It is an 8-disk RAID5, so 4 devices seem to be missing?
The "Update Time" is 21st April. So this array has not been used for over 5
months???
I think you need to spell out in more detail what the problem is, what the
current state is, how it got that way, and what you hope to achieve.
Because at the moment I am lost.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-12-17 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 20:56 mdadm error Michael Samer
2013-12-17 22:51 ` NeilBrown [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=20131218095157.7244c651@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=michael.samer@epos-cat.de \
/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).