All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: linux-raid@vger.kernel.org
Subject: Re: Server down-fail​ed RAID5-asking for some assistance
Date: Fri, 22 Apr 2011 13:19:43 +0200	[thread overview]
Message-ID: <ioro8f$bmb$1@dough.gmane.org> (raw)
In-Reply-To: <BANLkTimQXUvU68op8C-W4qPUQzBRzqgP+A@mail.gmail.com>

On 22/04/11 04:32, John Valarti wrote:
> On Thu, Apr 21, 2011 at 1:59 PM, David Brown<david.brown@hesbynett.no>  wrote:
> .
>> My first thought would be to get /all/ the disks, not just the "failed"
>> ones, out of the machine.  You want to make full images of them (with
>> ddrescue or something similar) to files on another disk, and then work with
>> those images.  ..
>> Once you've got some (hopefully most) of your data recovered from the
>> images, buy four /new/ disks to put in the machine, and work on your
>> restore.  You don't want to reuse the failing disks, and probably the other
>> two equally old and worn disks will be high risk too.
>
> OK, I think I understand.
> Does that mean I need to buy 8 disks, all the same size or bigger?
> The originals are 250GB SATA so that should be OK, I guess.
>

The way I would handle this is to get a couple of big disks (2 TB). 
They can be external USB drives if that's the most convenient (I have a 
nice hot-plug USB/eSATA enclosure that I find handy for messing about 
with temporary disks).  Put an ext4 (or xfs if you like) system on these 
disks.

Note that none of this need be done on the original computer - use 
whatever is convenient.  And if you already have lots of temporary disk 
space, you don't need to buy new disks yet.

Make images of your original disks - i.e., copy the whole 250 GB disk 
into a file on your big disk, so that you have four 250 GB files 
"originalA.image", "originalB.image", etc.  You can probably forget 
about the oldest dead disk - if it's been dead since 2009 there is 
little chance of it being useful.

Those "original" files are your safety copies - keep them, so that you 
can always get back to where you started without stressing the original 
disks any more.

Then copy those files to new files "diskA.image", etc.  Attach these to 
loop devices ("losetup /dev/loop1 diskA.image", etc.).  Then use these 
loop devices as devices for re-assembling your raid.  I'm not going to 
make any suggestions for that part - Neil is the expert.

The point is, if you mess up you can simple go back a couple of steps 
and re-copy your "original" image files and try again.  You loose 
nothing but a bit of time.

Once you have a re-assembled raid that looks like it contains your data, 
you can work on the restore process.

Restore is done by buying 4 new disks for the original server, setting 
them up as a new raid5, and copying the data over.  It can be very 
convenient to use something like a system rescue cd during this 
operation, so that you are not trying to run from the disks while doing 
the restore.

Once you are done, you will want to check for missing data or file 
system corruption.


mvh.,

David


> I read some more and found out I should run mdadm --examine.
>
> Should I not be able to just add the one disk partition sdc2 back to the RAID?
>
>


      parent reply	other threads:[~2011-04-22 11:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 18:29 Server down-fail​ed RAID5-asking for some assistance John Valarti
2011-04-21 19:59 ` David Brown
     [not found]   ` <BANLkTim18Sx6JdZO5PiAqnrakDPzy5PNJQ@mail.gmail.com>
2011-04-22  2:32     ` John Valarti
2011-04-22  2:57       ` Server " NeilBrown
2011-04-22  3:31         ` John Valarti
     [not found]         ` <BANLkTin0SoBzRAear8Jt+26MnVJWouXoNA@mail.gmail.com>
     [not found]           ` <20110423074411.78fef94f@notabene.brown>
     [not found]             ` <BANLkTik_ZY4uoV3E=ua1p+tUD9g8xqQDVg@mail.gmail.com>
     [not found]               ` <20110423184824.55ee7893@notabene.brown>
     [not found]                 ` <BANLkTi=sCfFFfmZTzj2g8-aDNhDqVK8e-A@mail.gmail.com>
     [not found]                   ` <20110424075101.6763309f@notabene.brown>
2011-04-24  0:07                     ` John Valarti
2011-04-24  0:37                       ` John Robinson
2011-04-24  1:49                         ` John Valarti
2011-04-24  2:12                           ` John Robinson
2011-04-24  2:28                             ` John Valarti
2011-04-24  2:58                               ` NeilBrown
2011-04-24  6:30                                 ` John Valarti
2011-04-24  2:54                       ` NeilBrown
2011-04-24  7:06                         ` John Valarti
2011-04-24  8:41                           ` NeilBrown
2011-04-24 11:57                             ` John Robinson
2011-04-24 12:29                               ` NeilBrown
2011-04-24 16:04                                 ` John Valarti
2011-04-24 16:15                                   ` John Valarti
2011-04-24 16:31                                     ` Mathias Burén
2011-04-24 18:41                                       ` John Valarti
2011-04-22 11:19       ` David Brown [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='ioro8f$bmb$1@dough.gmane.org' \
    --to=david.brown@hesbynett.no \
    --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 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.