Gentoo Archives: gentoo-user

From: Mick <michaelkintzios@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] hp H222 SAS controller
Date: Mon, 15 Jul 2013 12:20:11
Message-Id: 201307150839.34368.michaelkintzios@gmail.com
In Reply to: Re: [gentoo-user] hp H222 SAS controller by Paul Hartman
1 On Sunday 14 Jul 2013 23:35:50 Paul Hartman wrote:
2 > On Mon, Jul 8, 2013 at 10:58 AM, Alan McKinnon <alan.mckinnon@×××××.com>
3 wrote:
4 > > On 08/07/2013 17:39, Paul Hartman wrote:
5 > >> On Thu, Jul 4, 2013 at 9:04 PM, Paul Hartman
6 > >>
7 > >> <paul.hartman+gentoo@×××××.com> wrote:
8 > >>> ST4000DM000
9 > >>
10 > >> As a side-note these two Seagate 4TB "Desktop" edition drives I bought
11 > >> already, after about than 100 hours of power-on usage, both drives
12 > >> have each encountered dozens of unreadable sectors so far. I was able
13 > >> to correct them (force reallocation) using hdparm... So it should be
14 > >> "fixed", and I'm reading that this is "normal" with newer drives and
15 > >> "don't worry about it", but I'm still coming from the time when 1 bad
16 > >> sector = red alert, replace the drive ASAP. I guess I will need to
17 > >> monitor and see if it gets worse.
18 > >
19 > > Way back when in the bad old days of drives measured in 100s of megs,
20 > > you'd get a few bad sectors now and then, and would have to mark them as
21 > > faulty. This didn't bother us then much
22 > >
23 > > Nowadays we have drives that are 8,000 bigger than that so all other
24 > > things being equal we'd expect sectors to fail 8,000 time more (more
25 > > being a very fuzzy concept, and I know full well I'm using it loosely :-)
26 > > )
27 > >
28 > > Our drives nowadays also have smart firmware, something we had to
29 > > introduce when CHS no longer cut it, this lead to sector failures being
30 > > somewhat "invisible" leaving us with the happy delusion that drives were
31 > > vastly reliable etc etc etc. But you know all this.
32 > >
33 > > A mere few dozen failures in the first 100 hours is a failure rate of
34 > > (Alan whips out the trust sci calculator) 4.8E-6%. Pretty damn
35 > > spectacular if you ask me and WELL within probabilities.
36 > >
37 > > There is likely nothing wrong with your drives. If they are faulty, it's
38 > > highly likely a systemic manufacturing fault of the mechanicals (servo
39 > > systems, motor bearing etc)
40 > >
41 > > You do realize that modern hard drives have for the longest time been up
42 > > there in the Top X list of Most Reliable Devices Made By Mankind Ever?
43 >
44 > An update: the Seagate drives have both continued to spit more
45 > unrecoverable errors and find more and more bad sectors. Including
46 > some end-to-end errors indicated as critical "FAILING NOW" status in
47 > SMART. From what I have read that error means the drive's internal
48 > cache did not match the data written to disk, which seems like a
49 > serious flaw. The threshold is 1 which means if it happens at all, the
50 > drive should be replaced. It has happened half a dozen times on each
51 > disk so far (but not at the exact same time, so I don't think it is a
52 > host controller problem -- and other disks on the same controller and
53 > cable have had no issues). They have also been disconnecting and
54 > resetting randomly, sometimes requiring me to pull the drive and
55 > reinsert it into the enclosure to make it reappear. It happens even
56 > after I disabled APM, so I know it isn't a spin-down/idle timeout
57 > thing. Temperatures are actually very good (low 30's) so they are not
58 > overheating.
59 >
60 > I think I will try to trade them in to Seagate for a new pair under
61 > warranty replacement. And then probably try to sell the replacements
62 > and be rid of them.
63 >
64 > Meanwhile, during that experiment, I bought 2 brand new Western
65 > Digital Red 3TB drives last week. No problems in SMART testing or
66 > creating LVM/RAID/Filesystems. I have now been running the destructive
67 > write/read badblocks tests for 24+ hours and they have been perfect so
68 > far, exactly 0 errors. They are more expensive (3TB for the same price
69 > as the 4TB seagate) and slightly slower read/write speed (150MB/sec
70 > peak vs 170MB/sec peak), but I value reliability over all other
71 > factors.
72 >
73 > These Seagate drives must have some kind of manufacturing defect, or
74 > perhaps were damaged in shipping... UPS have been known to treat
75 > packages like a football!
76
77 I've been watching this thread with interest, because I've been trying to find
78 out which HDD I should be buying for a new PC. For every person reporting
79 problematic Seagates there's another person complaining about Western Digital
80 being too noisy, failing, or in the case of the black versions, far too
81 expensive.
82
83 Amidst all the anecdotal aphorisms against one or the other manufacturer, I
84 saw mentioned that the likelihood of failure doubles up when you go from 1TB
85 to 2 TB. If true, I guess that the 3TB would have fewer failures than 4TB
86 drive.
87
88 For what it's worth I have had a number of Seagates failing on me, but since
89 this was in the 90's. On my laptop a Seagate Momentus 7200.4 (ST9500420ASG)
90 is running fine for the last 3.5 years so, I was thinking of taking a punt on
91 a 'Seagate Barracuda 3.5 inch 2TB 7200 RPM 64MB 6GB/S Internal SATA'. But
92 what you're mentioning here gives me cause to pause.
93
94 --
95 Regards,
96 Mick

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-user] hp H222 SAS controller Paul Hartman <paul.hartman+gentoo@×××××.com>
Re: [gentoo-user] hp H222 SAS controller "J. Roeleveld" <joost@××××××××.org>