From: Anthonys Lists <antlists@youngman.org.uk>
To: bobzer <bobzer@gmail.com>,
linux-raid <linux-raid@vger.kernel.org>,
Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: raid 5 crashed
Date: Mon, 30 May 2016 20:04:25 +0100 [thread overview]
Message-ID: <574C8EB9.3070706@youngman.org.uk> (raw)
In-Reply-To: <CADzS=are4kkK5Lpm2WTAnqhE1D3XuMFwTKbO8_FzDbGtmqu2Dw@mail.gmail.com>
On 30/05/2016 16:01, bobzer wrote:
> HI,
>
> i did a dd_rescue which recovered a lot but not everything :
> # Rescue Logfile. Created by GNU ddrescue version 1.19
> # Command line: ddrescue -d -f -r3 /dev/sdf1
> wdc/9bececcb-d520-ca38-fd88-d9565718e361.dd
> wdc/9bececcb-d520-ca38-fd88-d9565718e361.mapfile
> # Start time: 2016-05-29 22:32:38
> # Current time: 2016-05-29 23:04:49
> # Finished
> # current_pos current_status
> 0x129F7DB6000 +
> # pos size status
> 0x00000000 0x1118E2AB200 +
> 0x1118E2AB200 0x00001000 -
> 0x1118E2AC200 0x00090000 +
> 0x1118E33C200 0x00001000 -
> 0x1118E33D200 0x00817000 +
> 0x1118EB54200 0x00001000 -
> 0x1118EB55200 0x0016B000 +
> 0x1118ECC0200 0x00001000 -
> 0x1118ECC1200 0x641976000 +
> 0x117D0637200 0x00001000 -
> 0x117D0638200 0x000FE000 +
> 0x117D0736200 0x00001000 -
> 0x117D0737200 0x000EC000 +
> 0x117D0823200 0x00001000 -
> 0x117D0824200 0x0010C000 +
> 0x117D0930200 0x00001000 -
> 0x117D0931200 0x0010C000 +
> 0x117D0A3D200 0x00001000 -
> 0x117D0A3E200 0x00375000 +
> 0x117D0DB3200 0x00001000 -
> 0x117D0DB4200 0x0010B000 +
> 0x117D0EBF200 0x00002000 -
> 0x117D0EC1200 0x0010C000 +
> 0x117D0FCD200 0x00001000 -
> 0x117D0FCE200 0x001EB000 +
> 0x117D11B9200 0x00001000 -
> 0x117D11BA200 0x00112000 +
> 0x117D12CC200 0x00001000 -
> 0x117D12CD200 0x00077000 +
> 0x117D1344200 0x00001000 -
> 0x117D1345200 0x000EB000 +
> 0x117D1430200 0x00001000 -
> 0x117D1431200 0x000FD000 +
> 0x117D152E200 0x00001000 -
> 0x117D152F200 0x0010C000 +
> 0x117D163B200 0x00001000 -
> 0x117D163C200 0x00251000 +
> 0x117D188D200 0x00002000 -
> 0x117D188F200 0x12264B3000 +
> 0x129F7D42200 0x00001000 -
> 0x129F7D43200 0x0004F000 +
> 0x129F7D92200 0x00001000 -
> 0x129F7D93200 0x00022000 +
> 0x129F7DB5200 0x00001000 -
> 0x129F7DB6200 0xA7C90DA200 +
>
> i don't know if i can recover more but i tried to reassemble the raid
> and it work but during the rebuilding the sdb1 failed again
> so my data are there but i'm not sure to know what to do to get them all.
>
> thanks
>
>
Did you follow Mikael's advice? Can you do smartctl on the drive (I
think the option you want is "smartctl -x" - display "extended all") and
post the output?
We're assuming you're using proper raid-capable drives, but if you
aren't then the drives could be fine but giving up under load and
causing your raid problems. On the other hand, if your drives are proper
raid drives, then they're probably not fit for anything more than the
scrapheap.
Cheers,
Wol
next prev parent reply other threads:[~2016-05-30 19:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 21:28 raid 5 crashed bobzer
2016-05-11 12:09 ` Mikael Abrahamsson
2016-05-11 13:15 ` Robin Hill
2016-05-26 3:06 ` bobzer
2016-05-27 19:19 ` bobzer
2016-05-30 15:01 ` bobzer
2016-05-30 19:04 ` Anthonys Lists [this message]
2016-05-30 22:00 ` bobzer
2016-05-31 13:45 ` Phil Turmel
2016-05-31 18:49 ` Wols Lists
2016-06-01 1:48 ` Brad Campbell
2016-06-01 3:46 ` Edward Kuns
2016-06-01 4:07 ` Brad Campbell
2016-06-01 5:23 ` Edward Kuns
2016-06-01 5:28 ` Brad Campbell
2016-06-01 15:36 ` Wols Lists
2016-06-01 23:15 ` Brad Campbell
2016-06-02 5:52 ` Mikael Abrahamsson
2016-06-02 14:01 ` Wols Lists
2016-06-02 15:27 ` Andreas Klauer
2016-06-03 1:05 ` Brad Campbell
2016-06-03 7:52 ` Mikael Abrahamsson
2016-06-03 15:27 ` bobzer
2016-06-03 16:31 ` Sarah Newman
2016-06-04 2:56 ` bobzer
2016-06-01 15:42 ` Wols Lists
2016-06-01 17:28 ` Phil Turmel
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=574C8EB9.3070706@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=bobzer@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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).