linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramon Hofer <ramonhofer@bluewin.ch>
To: linux-raid@vger.kernel.org
Subject: Re: Stacked array data recovery
Date: Sun, 24 Jun 2012 12:15:10 +0000 (UTC)	[thread overview]
Message-ID: <js70ce$fgv$1@dough.gmane.org> (raw)
In-Reply-To: 4FE5B213.5010503@hardwarefreak.com

On Sat, 23 Jun 2012 07:09:55 -0500, Stan Hoeppner wrote:

> On 6/22/2012 9:37 AM, Ramon Hofer wrote:
>> Sorry, I hit the wrong button.On Thu, 21 Jun 2012 22:44:10 +0000, Ramon
>> Hofer wrote:
>> 
>>> Is it possible to start md1 again to be able to start the linear array
>>> md0 so that I can accesss the data?
>> 
>> Stan will probably be angry with me but I did the following:
>> 
>> I found the recovery page in your wiki:
>> https://raid.wiki.kernel.org/index.php/RAID_Recovery
>> 
>> So I followed the process there.
>> This is what I did:
>> 
>> ~$ mdadm --examine /dev/sd[abcd] > raid.status.md1
>> 
>> ~$ mdadm --create --assume-clean -c 128 --level=5 --raid-devices=4
>> /dev/ md1 /dev/sda /dev/sdb /dev/sdc /dev/sdd
>> 
>> It was up and clean.
>> 
>> ~$ mdadm --examine /dev/md[12] > raid.status.md0
>> 
>> ~$ mdadm -C --assume-clean -n2 -l linear /dev/md0 /dev/md[12]
>> 
>> Now I could mount md0 and all my data is still there :-D
> 
> You should have run an "xfs_repair -n" before mounting.  "-n" means no
> modify, making it a check operation.  If it finds errors then rerun it
> without the "-n" so it can make necessary repairs.  Then remount.  Sorry
> I forgot to mention this, or remind you, whichever is the case. :)

Thanks you!

You have mentioned but I forgot to do it.
I did it now and still everything looks good.
At least with the WD blacks and the Samsung drives.

One WD green was again marked faulty when I tried to create an array with 
them.

This is the output of dmesg:
http://pastebin.com/raw.php?i=5aukYJa8

This seems to be not good:
[61142.466334] md/raid:md9: read error not correctable (sector 3758190680 
on sdk).
[61142.466338] md/raid:md9: Disk failure on sdk, disabling device.

What could the reason of this issue be?
Is it because the disk is broken or not suited for raid use?

I'm now running smartctl -t long /dev/sdk.
I have no clue if this helps in any way...

Here's the output of smartctl -a /dev/sdk:
http://pastebin.com/raw.php?i=2ULrx6du


Should I bring the disc to my dealer or is it an issue of using it with 
mdadm?


Best regards
Ramon


  reply	other threads:[~2012-06-24 12:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 22:44 Stacked array data recovery Ramon Hofer
2012-06-22 14:32 ` Ramon Hofer
2012-06-23 12:05   ` Stan Hoeppner
2012-06-22 14:37 ` Ramon Hofer
2012-06-23 12:09   ` Stan Hoeppner
2012-06-24 12:15     ` Ramon Hofer [this message]
2012-06-24 14:12       ` Stan Hoeppner
2012-06-25  3:51         ` Stan Hoeppner
2012-06-25 10:31           ` Ramon Hofer
2012-06-26  1:53             ` Stan Hoeppner
2012-06-26  8:37               ` Ramon Hofer
2012-06-26 20:23                 ` Stan Hoeppner
2012-06-27  9:07                   ` Ramon Hofer
2012-06-27 12:34                     ` Stan Hoeppner
2012-06-27 19:19                       ` Ramon Hofer
2012-06-28 19:57                         ` Stan Hoeppner
2012-06-29  7:58                           ` Ramon Hofer
2012-06-28 18:44                     ` Krzysztof Adamski
2012-06-29  7:44                       ` Ramon Hofer
2012-06-29 10:15                         ` John Robinson
2012-06-29 11:19                           ` Ramon Hofer
2012-07-02 10:12                   ` Ramon Hofer
2012-07-02 11:46                     ` Phil Turmel
2012-07-02 12:18                       ` Ramon Hofer
2012-07-02 21:42                         ` Phil Turmel
2012-07-02 20:27                     ` Stan Hoeppner
2012-07-03  7:16                       ` Ramon Hofer

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='js70ce$fgv$1@dough.gmane.org' \
    --to=ramonhofer@bluewin.ch \
    --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).