From: Cry <cry_regarder@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: Two Drive Failure on RAID-5
Date: Tue, 20 May 2008 15:32:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20080520T145950-804@post.gmane.org> (raw)
In-Reply-To: 48327FC2.1010901@dgreaves.com
David Greaves <david <at> dgreaves.com> writes:
>
> Yep. Don't panic and don't do anything else yet if you're not confident about
> what you're doing.
>
> I'll follow up with more info in a short while.
>
> Info you can provide:
> kernel version
> mdadm version
> cat /proc/mdstat
> mdadm --examine /dev/sd[abcdef]1 (or whatever your array components are)
> relevant smartctl info on the bad drive(s)
> dmesg info about the drive failures
>
> Assuming genuine hardware failure:
> Do you have any spare drives that you can use to replace the components?
>
> David
Thanks for the info. I was able to do a --force --assemble on the array and I
copied off my most critical data. At the moment, I don't have enough drives to
take all the data on the array, so I'm going to be at a bit of a standstill
until new hardware arrives.
Since the copy of that data (about 500Gig of about 2TB) went so well, I decided
to try to sync up the spare again and it died at the same point and the raid
system pulled down the array. I'm trying to decide if I should follow your
suggestion in sister post to copy the failed drive onto my spare or if I should
just format the spare and try to recover another 500 gig of data of the array.
Is there a mdadm or other command to tell the raid system to stay up in the face
of errors? Can the array be assembled in a way that doesn't change the array in
any way (completely read-only)?
I've got the older failed drive also (about 15 hours older). Can that be
leveraged also?
The server isn't networked right now, but I'll try to get the above requested
logs tonight.
By the way, I'm thinking about buying five of these:
Seagate Barracuda 7200.11 1TB ST31000340AS SATA-II 32MB Cache
and one of these:
Supermicro SUPERMICRO CSE-M35T-1 Hot-Swapable SATA HDD Enclosure
http://www.supermicro.com/products/accessories/mobilerack/CSE-M35T-1.cfm
and building a raid-6 array. I'll convert the surviving drives into a backup
for the primary array. Any feedback on the above? Is there a suggestion on an
inexpensive controller to give more SATA ports that is very software raid
compatible?
Any suggestions for optimal configuration (ext3) and tuning for the new array?
My load consists of serving a photo gallery via apache and gallery2 as well as a
local media (audio/video) server so files sizes tend to be large.
Thanks,
Joel
next prev parent reply other threads:[~2008-05-20 15:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 22:49 Two Drive Failure on RAID-5 Cry
2008-05-20 7:37 ` David Greaves
2008-05-20 15:32 ` Cry [this message]
2008-05-20 17:18 ` David Lethe
2008-05-20 19:01 ` Cry
2008-05-20 20:09 ` David Lethe
2008-05-20 23:11 ` Keith Roberts
2008-05-20 19:40 ` Janos Haar
2008-05-20 17:27 ` David Lethe
2008-05-20 19:28 ` Brad Campbell
2008-05-20 9:14 ` David Greaves
2008-05-20 12:17 ` Janos Haar
2008-05-21 14:14 ` Cry
2008-05-21 20:15 ` David Greaves
2008-05-21 20:47 ` Janos Haar
2008-05-21 21:21 ` Cry
2008-05-22 8:38 ` David Greaves
2008-05-31 9:27 ` Cry
2008-05-22 0:05 ` Cry
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 0:24 Re: " David Lethe
2008-05-22 14:42 ` Ric Wheeler
2008-05-22 16:16 ` David Lethe
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=loom.20080520T145950-804@post.gmane.org \
--to=cry_regarder@yahoo.com \
--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).