From: Frank Baumgart <frank.baumgart@gmx.net>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 superblocks partly messed up after degradation
Date: Sat, 14 Apr 2007 00:09:08 +0200 [thread overview]
Message-ID: <461FFF84.9020400@gmx.net> (raw)
In-Reply-To: <17948.7830.809009.253759@notabene.brown>
Neil Brown wrote:
> I'll see what I can do :-)
>
The problem could be resolved by removing one of the two external SATA
controllers (PCI card with ALI M5283) and using Kernel 2.6.20.6
Only removing the ALI PCI card brought the numbering scheme in line
again so the old (degraded) array became accessible again. Even with no
disks attached to it, the kernel did not get its disk naming in shape to
assemble more than one ("sdd") of the four old devices although all 4
devices could be accessed with "mdadm --examine" or fdisk.
Additionally, using 2.6.20.6 resolved the ghost device issue where one
SATA drive appeared additionally as a PATA drive, too. Now I could
create the new array and copy over all data from the degraded one.
<wipes sweat>
> Are there any kernel logs that this time which might make it clear
> what is happening?
>
Not really, the logs contain quite a mess of trying different kernels
and system configurations to get the data back
with the disc naming following the state of the moon.
I produced too much sweat to get the data back so I am reluctant to try
anything now that it works until my backup
scheme is somewhat improved :)
Thank you for your help.
Frank
prev parent reply other threads:[~2007-04-13 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 18:04 RAID5 superblocks partly messed up after degradation Frank Baumgart
2007-04-10 23:32 ` Neil Brown
2007-04-13 22:09 ` Frank Baumgart [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=461FFF84.9020400@gmx.net \
--to=frank.baumgart@gmx.net \
--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).