Date: Sat, 21 Jan 2012 12:33:13 +0200 From: Daniel Kalchev <daniel@digsys.bg> To: freebsd-fs@freebsd.org Subject: Re: sanity check: is 9211-8i, on 8.3, with IT firmware still "the one" Message-ID: <4F1A9469.1060605@digsys.bg> In-Reply-To: <1327117388.29408.24.camel@btw.pki2.com> References: <alpine.BSF.2.00.1201191604510.19710@kozubik.com> <4F192ADA.5020903@brockmann-consult.de> <1327069331.29444.4.camel@btw.pki2.com> <20120120153129.GA97746@icarus.home.lan> <1327077094.29408.11.camel@btw.pki2.com> <20120120181828.GA1049@icarus.home.lan> <1327117388.29408.24.camel@btw.pki2.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21.01.12 05:43, Dennis Glatting wrote: > I used Seatools on one of the disks from the first set > (ST1000DL002-9TT153). On a long test the tools declared there were > errors that it could not fix. I didn't see much point in trying the > second disk. You should be able to run the long tests via SMART using the smartmontools (smartctl) as well, in FreeBSD. There are a number of different tests (see man page) each doing different things -- unfortunately, they rarely do the same things on different make/model disks as well. But it is better to test the second disk to check if it has the same type of problem. > So, two separately purchased disks from the same vendor bad? > (TigerDirect) What's the odds of that? Hmm... It is not only possible, it is typical. This is why the recommendation to build dependable array is to use disks from different vendors/lots. It may be the manufacturing lot having undetected defects. It may be that during shipping, that group of disks experienced bad handling etc -- you may have purchased the disks at different times, yet they may come from the same manufacturing lot and shipment. Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F1A9469.1060605>