From owner-freebsd-fs@FreeBSD.ORG Sat Jan 21 10:33:24 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 897AF106566C for ; Sat, 21 Jan 2012 10:33:24 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id 113C68FC0C for ; Sat, 21 Jan 2012 10:33:23 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.5/8.14.5) with ESMTP id q0LAXDG5085194 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 21 Jan 2012 12:33:19 +0200 (EET) (envelope-from daniel@digsys.bg) Message-ID: <4F1A9469.1060605@digsys.bg> Date: Sat, 21 Jan 2012 12:33:13 +0200 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111228 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <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> In-Reply-To: <1327117388.29408.24.camel@btw.pki2.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: sanity check: is 9211-8i, on 8.3, with IT firmware still "the one" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 10:33:24 -0000 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