From: Christoph Nelles <evilazrael@evilazrael.de>
To: linux-raid@vger.kernel.org
Subject: Re: Raid5 crashed, need comments on possible repair solution
Date: Mon, 23 Apr 2012 23:47:12 +0200 [thread overview]
Message-ID: <4F95CDE0.4070200@evilazrael.de> (raw)
In-Reply-To: <20120424070044.707745b8@notabene.brown>
Hello Neil,
first thanks for the answer. I will happily provide any data or logs if
it helps you to investigate this problem.
Am 23.04.2012 23:00, schrieb NeilBrown:
> This is really worrying. It's about the 3rd or 4th report recently which
> contains:
>
>> Raid Level : -unknown-
>> Raid Devices : 0
>
> and that should not be possible. There must be some recent bug that causes
> the array to be "cleared" *before* writing out the metadata - and that should
> be impossible.
> What kernel are you running?
I switched kernel versions during that server rebuild. Last running
system was with 3.2.5, then rebuild and switch to 3.3.1 ant with that it
crashed. Kernel is vanilla selfcompiled, x86_64.
mdadm is 3.1.5, selfcompiled, too.
> You are correct that order is important. Your algorithm looks good.
> However I suggest that you first look through your system looks to see if
>
> RAID conf printout:
>
> appears at all. That could contain the device order.
Yes, i found that, but as i reordered and rewired the drives due to
thermal reasons so I have no idea which drive was mapped to which device
name. In the normal system logs are only the model names and i had
multiple drives of the same type.
Regards
Christoph Nelles
--
Christoph Nelles
E-Mail : evilazrael@evilazrael.de
Jabber : eazrael@evilazrael.net ICQ : 78819723
PGP-Key : ID 0x424FB55B on subkeys.pgp.net
or http://evilazrael.net/pgp.txt
next prev parent reply other threads:[~2012-04-23 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 13:56 Raid5 crashed, need comments on possible repair solution Christoph Nelles
2012-04-23 21:00 ` NeilBrown
2012-04-23 21:47 ` Christoph Nelles [this message]
2012-04-23 23:01 ` NeilBrown
2012-05-12 17:19 ` Pierre Beck
2012-05-14 21:00 ` C.J. Adams-Collier KF7BMP
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=4F95CDE0.4070200@evilazrael.de \
--to=evilazrael@evilazrael.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.