From: "Patrik Dahlström" <risca@powerlamerz.org>
To: Andreas Klauer <Andreas.Klauer@metamorpher.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recover array after I panicked
Date: Sun, 23 Apr 2017 13:12:54 +0200 [thread overview]
Message-ID: <754209bb-9990-2a36-2233-d7d1273c8e37@powerlamerz.org> (raw)
In-Reply-To: <20170423104606.GA4603@metamorpher.de>
On 04/23/2017 12:46 PM, Andreas Klauer wrote:
> On Sun, Apr 23, 2017 at 12:23:17PM +0200, Patrik Dahlström wrote:
>> At this point, it is incorrect.
>
> :-(
>
>> I've lost the output from the working
>> raid too, unless it's located in any log in /var/log/.
>
> If you have kernel logs from before your accident...
> check for stuff like this:
>
> [ 7.328420] md: md6 stopped.
> [ 7.329705] md/raid:md6: device sdb6 operational as raid disk 0
> [ 7.329705] md/raid:md6: device sdg6 operational as raid disk 6
> [ 7.329706] md/raid:md6: device sdh6 operational as raid disk 5
> [ 7.329706] md/raid:md6: device sdf6 operational as raid disk 4
> [ 7.329706] md/raid:md6: device sde6 operational as raid disk 3
> [ 7.329707] md/raid:md6: device sdd6 operational as raid disk 2
> [ 7.329707] md/raid:md6: device sdc6 operational as raid disk 1
> [ 7.329924] md/raid:md6: raid level 5 active with 7 out of 7 devices, algorithm 2
> [ 7.329936] md6: detected capacity change from 0 to 1500282617856
>
> That's not everything but it's something.
I got some of that!
[ 3.100350] md/raid:md1: device sde operational as raid disk 4
[ 3.100350] md/raid:md1: device sdc operational as raid disk 3
[ 3.100350] md/raid:md1: device sdd operational as raid disk 2
[ 3.100351] md/raid:md1: device sda operational as raid disk 0
[ 3.100351] md/raid:md1: device sdb operational as raid disk 1
[ 3.100689] md/raid:md1: allocated 5432kB
[ 3.100699] md/raid:md1: raid level 5 active with 5 out of 5 devices,
algorithm 2
[ 3.100700] RAID conf printout:
[ 3.100700] --- level:5 rd:5 wd:5
[ 3.100700] disk 0, o:1, dev:sda
[ 3.100700] disk 1, o:1, dev:sdb
[ 3.100701] disk 2, o:1, dev:sdd
[ 3.100701] disk 3, o:1, dev:sdc
[ 3.100701] disk 4, o:1, dev:sde
[ 3.101006] created bitmap (44 pages) for device md1
[ 3.102245] md1: bitmap initialized from disk: read 3 pages, set 0 of
89423 bits
[ 3.159019] md1: detected capacity change from 0 to 24004163272704
At least I now know in what order that I should assemble my original 5
drives:
sda, sdb, sdd, sdc, sde
It would only be logical for the new drive (sdf) to be last in that list.
>
> Also in the future for experiments, go with overlays.
>
> https://raid.wiki.kernel.org/index.php/Recovering_a_failed_software_RAID#Making_the_harddisks_read-only_using_an_overlay_file
> (and the overlay manipulation functions below that)
>
> Lets you mess with mdadm --create stuff w/o actually overwriting original metadata.
Will do
>
> Regards
> Andreas Klauer
>
next prev parent reply other threads:[~2017-04-23 11:12 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 9:47 Recover array after I panicked Patrik Dahlström
2017-04-23 10:16 ` Andreas Klauer
2017-04-23 10:23 ` Patrik Dahlström
2017-04-23 10:46 ` Andreas Klauer
2017-04-23 11:12 ` Patrik Dahlström [this message]
2017-04-23 11:36 ` Wols Lists
2017-04-23 11:47 ` Patrik Dahlström
2017-04-23 11:53 ` Reindl Harald
2017-04-23 11:58 ` Roman Mamedov
2017-04-23 12:11 ` Wols Lists
2017-04-23 12:15 ` Patrik Dahlström
2017-04-24 21:04 ` Phil Turmel
2017-04-24 21:56 ` Patrik Dahlström
2017-04-24 23:35 ` Phil Turmel
2017-04-23 13:16 ` Andreas Klauer
2017-04-23 13:49 ` Patrik Dahlström
2017-04-23 14:36 ` Andreas Klauer
2017-04-23 14:45 ` Patrik Dahlström
2017-04-23 12:32 ` Patrik Dahlström
2017-04-23 12:45 ` Andreas Klauer
2017-04-23 12:57 ` Patrik Dahlström
2017-04-23 14:06 ` Brad Campbell
2017-04-23 14:09 ` Patrik Dahlström
2017-04-23 14:20 ` Patrik Dahlström
2017-04-23 14:25 ` Brad Campbell
2017-04-23 14:48 ` Andreas Klauer
2017-04-23 15:11 ` Patrik Dahlström
2017-04-23 15:24 ` Patrik Dahlström
2017-04-23 15:42 ` Andreas Klauer
2017-04-23 16:29 ` Patrik Dahlström
2017-04-23 19:21 ` Patrik Dahlström
2017-04-24 2:09 ` Brad Campbell
2017-04-24 7:34 ` Patrik Dahlström
2017-04-24 11:04 ` Andreas Klauer
2017-04-24 12:13 ` Patrik Dahlström
2017-04-24 12:37 ` Andreas Klauer
2017-04-24 12:54 ` Patrik Dahlström
2017-04-24 13:39 ` Andreas Klauer
2017-04-24 14:05 ` Patrik Dahlström
2017-04-24 14:21 ` Andreas Klauer
2017-04-24 16:00 ` Patrik Dahlström
2017-04-24 23:00 ` Patrik Dahlström
2017-04-25 0:16 ` Andreas Klauer
2017-04-25 8:44 ` Patrik Dahlström
2017-04-25 9:01 ` Andreas Klauer
2017-04-25 10:40 ` Patrik Dahlström
2017-04-25 10:51 ` Patrik Dahlström
2017-04-25 11:08 ` Andreas Klauer
2017-04-25 11:37 ` Patrik Dahlström
2017-04-25 12:41 ` Andreas Klauer
2017-04-25 18:22 ` Wols Lists
2017-04-27 19:57 ` Patrik Dahlström
2017-04-27 23:12 ` Andreas Klauer
2017-04-28 7:11 ` Patrik Dahlström
2017-04-28 9:52 ` Andreas Klauer
2017-04-28 10:31 ` Patrik Dahlström
2017-04-28 11:39 ` Andreas Klauer
2017-04-28 22:46 ` Patrik Dahlström
2017-04-29 9:56 ` Andreas Klauer
2017-05-02 13:08 ` Patrik Dahlström
2017-05-02 13:11 ` Brad Campbell
2017-05-02 15:49 ` Anthony Youngman
2017-04-25 23:01 ` Patrik Dahlström
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=754209bb-9990-2a36-2233-d7d1273c8e37@powerlamerz.org \
--to=risca@powerlamerz.org \
--cc=Andreas.Klauer@metamorpher.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox