All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: John Stoffel <john@stoffel.org>,
	Salatiel Filho <salatiel.filho@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Input/Output error reading from a clean raid
Date: Mon, 23 Jan 2017 17:23:49 +0000	[thread overview]
Message-ID: <58863C25.9020200@youngman.org.uk> (raw)
In-Reply-To: <22662.14390.551624.557189@quad.stoffel.home>

On 23/01/17 17:07, John Stoffel wrote:
> You have bad disks in your array.  First thing off is that I would go
> buy replacements and then use 'ddrescue' to copy the data from the old
> disks to new disks.  Then I'd try to assemble the NEW disks only into
> an array, and then I'd fsck the filesystem(s).
> 
> You're going to lose data, no doubt about it.  You're now in the mode
> where you're trying to save as much as you can as quickly as possible.
> 
> Personally, I'd be setting up a RAID6 array for your new setup.  Then
> I would also be setting up weekly checks of the raid array as well.
> 
> You're going to lose data no matter what.  So get new disks and start
> copying what you can.

Go read the raid wiki. https://raid.wiki.kernel.org/index.php/Linux_Raid

Especially replacing a failed drive
https://raid.wiki.kernel.org/index.php/Replacing_a_failed_drive

And please - can you get ddrescue's error log that it mentions and email
me a copy. If you've got some Perl or Python or shell skills, maybe you
could even write that script it mentions (which is described in a bit
more detail in programming projects
https://raid.wiki.kernel.org/index.php/Programming_projects) Otherwise
I'll try and write it - might be a good way of learning Python :-) but
at the moment I think I'm learning by jumping in out of my depth, so
we'll see how far I get :-)

Cheers,
Wol



  reply	other threads:[~2017-01-23 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22 14:08 Input/Output error reading from a clean raid Salatiel Filho
2017-01-23  0:18 ` John Stoffel
2017-01-23 14:42   ` Salatiel Filho
2017-01-23 16:12     ` John Stoffel
     [not found] ` <20170123010334.GA7546@metamorpher.de>
2017-01-23 14:02   ` Salatiel Filho
2017-01-23 17:07     ` John Stoffel
2017-01-23 17:23       ` Wols Lists [this message]
2017-01-23 17:34     ` Andreas Klauer
2017-01-24 21:15       ` Salatiel Filho
2017-01-24 21:58         ` Wols Lists
2017-01-25 15:54         ` John Stoffel

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=58863C25.9020200@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=john@stoffel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=salatiel.filho@gmail.com \
    /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.