From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Justin Stephenson <justin@evensteveninc.com>, linux-raid@vger.kernel.org
Subject: Re: Issue removing failed drive and re adding on raid 6
Date: Sun, 05 Jul 2015 16:58:35 -0600 [thread overview]
Message-ID: <1769278.0JzAUmkQ4M@balsa> (raw)
In-Reply-To: <emf8fb4dd8-3843-4c1c-b8e4-35b5028b3f14@littlez>
On Sat 04 Jul 2015 04:38:18 PM you wrote:
> >>6.00: ATA-8: ST3000DM001-9YN166, CC4H, max UDMA/133
> >>
> >> ata6.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> >> ata7.00: ATA-9: ST3000DM001-1CH166, CC27, max UDMA/133
> >> ata7.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> >> ata8.00: ATA-9: ST3000DM001-1CH166, CC27, max UDMA/133
> >> ata8.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> >> ata5.00: ATA-9: ST3000DM001-1CH166, CC27, max UDMA/133
> >> ata5.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> >> ata6.00: configured for UDMA/133
> >> ata4.00: ATA-9: ST3000DM001-1CH166, CC27, max UDMA/133
> >> ata4.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> >
> >OWWWWW OWWWWWW OWWWWW
> >
> >Are these 3TB Seagate Barracudas? (Same as mine). You DO NOT want to be
> >running raid 5 or 6 on these things !!!! They're desktop drives not
> >meant for raid.
> >
> >They do not support ERC. *One* *soft* failure on these and you run a
> >good chance of trashing your array !!!!
> >
> >Make sure you've got your raid timeout increased - there's plenty of
> >threads about how to do it - otherwise one disk hiccup for any reason
> >is
> >likely to cause a cascade of failures !!!!
> >
> >You need to upgrade them to Western Digital Reds or similar asap.
> >
> >Cheers,
> >Wol
>
> Hi Wol,
>
> Yes, these are the 3GB Seagates. They have been running 24/7 for about 3
> years now. I lose a drive occasionally, replace and rebuild. I will
> consider the REDs for the next time I do an upgrade - I imagin I would
> have to replace all 7 drives at once. How about the Seagate NAS HDDs?
I've just been replacing my desktop drives (all seagates, 1, 2 and 3 TB) as
they fail. I've got 5 WD REDs now, in two separate arrays. I think 2 2TB REDs
(out of 7 drives total) in my main NAS raid5 array (If I had room for one more
drive, I'd make it a raid6), and 3 3TB REDS (out of 6 main drives, one hot
spare, and one cold spare) in my backup raid6 array.
Yeah, I've become paranoid enough that I have a full backup of the main NAS
array now. I actually had to use it recently, due to a really stupid mistake
I'd rather not talk about that wiped the filesystem ;D probably half of the
array "failures" I've had were pebkac, so having a full backup copy is
incredibly important for me. The backup array also stores backups of my
/important/ rsnapshot backups of my machine configs, documents, and other
important things.
> I will look at the the raid timeout. Thank-you for the tip.
>
> - Justin
>
> --
> 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
--
Thomas Fjellstrom
thomas@fjellstrom.ca
prev parent reply other threads:[~2015-07-05 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 15:44 Issue removing failed drive and re adding on raid 6 Justin Stephenson
2015-07-03 20:47 ` Mikael Abrahamsson
2015-07-03 22:20 ` Re[2]: " Justin Stephenson
2015-07-04 5:11 ` Mikael Abrahamsson
2015-07-04 6:10 ` Re[3]: " Justin Stephenson
2015-07-04 6:58 ` Mikael Abrahamsson
2015-07-04 7:12 ` Re[4]: " Justin Stephenson
2015-07-04 7:25 ` Mikael Abrahamsson
2015-07-04 7:58 ` Wols Lists
2015-07-04 8:10 ` Mikael Abrahamsson
2015-07-04 9:23 ` Wols Lists
2015-07-05 10:27 ` Roman Mamedov
2015-07-06 0:15 ` Re[2]: " Justin Stephenson
2015-07-04 16:38 ` Justin Stephenson
2015-07-05 22:58 ` Thomas Fjellstrom [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=1769278.0JzAUmkQ4M@balsa \
--to=thomas@fjellstrom.ca \
--cc=justin@evensteveninc.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 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.