From: "Majed B." <majedb@gmail.com>
To: Tim Bostrom <tbostrom@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID 5 array recovery - two drives errors in external enclosure
Date: Sat, 19 Sep 2009 02:37:59 +0300 [thread overview]
Message-ID: <70ed7c3e0909181637g35b31926ref7e4a16beaab73c@mail.gmail.com> (raw)
In-Reply-To: <2267211f0909181630r33fcdbe5hb0d158b9bf12924b@mail.gmail.com>
If you're going to take all your data out, I would suggest you do a
clean start and zero out all the disks to force the remapping of bad
sectors, then run smartctl -t offline on all disks and after it's done
(it will take A LONG time), create your filesystem on an array and put
back your data.
On Sat, Sep 19, 2009 at 2:30 AM, Tim Bostrom <tbostrom@gmail.com> wrote:
> THANK YOU!
>
> To all of you who helped with advice. I finally waded through 70MB of
> log files from the last 6 months on my server and finally figured out
> a way to get the correct order. I had a few logs of 'fdisk -l" which
> contained the Disk Identifier. I matched that up against where I had
> the drives in the enclosure and the ata.#'s. I came up with a short
> list of drive letter ordering and just kept trying them with four
> drives at a time moving the _missing_ drive around. Finally, it came
> up.
>
> I'm now up with four drives and RO filesystem. I'm going to try and
> backup as much as possible off-disk. Then I'm thinking that I need to
> add the "missing" drive back in and re-build.
>
> Correct?
>
> Thank you again.
>
> Tim
--
Majed B.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-18 23:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 20:42 RAID 5 array recovery - two drives errors in external enclosure Tim Bostrom
2009-09-17 21:22 ` Robin Hill
2009-09-17 21:35 ` Majed B.
2009-09-17 21:51 ` Tim Bostrom
2009-09-17 22:11 ` Majed B.
2009-09-17 22:23 ` Tim Bostrom
2009-09-18 7:58 ` Robin Hill
2009-09-17 23:11 ` Tim Bostrom
2009-09-17 23:28 ` Majed B.
2009-09-17 23:54 ` Tim Bostrom
2009-09-18 1:31 ` Guy Watkins
2009-09-18 3:50 ` Tim Bostrom
2009-09-18 4:19 ` Tim Bostrom
2009-09-18 8:07 ` Robin Hill
2009-09-18 15:27 ` Tim Bostrom
2009-09-18 15:41 ` Robin Hill
[not found] ` <6b696870909180910q67d8166ay7796321b8cd35809@mail.gmail.com>
[not found] ` <2267211f0909180912p745e4ea0idb5659cb54a6adce@mail.gmail.com>
[not found] ` <6b696870909180923m35f29fa2l857b6f6402eb20be@mail.gmail.com>
[not found] ` <2267211f0909181041o29d6f5eft1e260696c6ab9c57@mail.gmail.com>
[not found] ` <6b696870909181317x777e3c5dsdcf0e7709f9c4979@mail.gmail.com>
2009-09-18 23:30 ` Tim Bostrom
2009-09-18 23:37 ` Majed B. [this message]
2009-09-19 1:17 ` Tom Carlson
2009-09-19 1:35 ` Guy Watkins
2009-09-21 4:40 ` Tim Bostrom
2009-09-21 4:59 ` Guy Watkins
2009-09-21 7:05 ` Majed B.
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=70ed7c3e0909181637g35b31926ref7e4a16beaab73c@mail.gmail.com \
--to=majedb@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=tbostrom@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox