From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BF39C13800E for ; Wed, 8 Aug 2012 04:21:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6F48721C059; Wed, 8 Aug 2012 04:20:49 +0000 (UTC) Received: from mail-gg0-f181.google.com (mail-gg0-f181.google.com [209.85.161.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 68C6221C04C for ; Wed, 8 Aug 2012 04:18:46 +0000 (UTC) Received: by ggmb6 with SMTP id b6so392959ggm.40 for ; Tue, 07 Aug 2012 21:18:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=K7zxK2IvzfoSm3+30Fr/z9w7WaBuD5SSyUN0t+tjq+c=; b=jmdDg162AyHjxIF5ckS8hHOLhd6tiz7rhEfRK3qU/5e4yeZBoL5LyoS9Y+IlLl8Nqn gDsUAIJkYkOtX8nsuQ4/jC1iF6EHEd5WPfUea+E1Xe4eDbAQgblUf046zImlRsBtNYnc uY4bUCh+kX081kFoCur4YFrbJVmCIheEr2wChBhxcTYN4/sjCCiV/qncQ7z3zTf9Y4Tz 0E0BNKAEzxCu8N8f7Yf/gSN/mXN4cOZW4W86v/F6QkEY54r8nJchVCSMjAPRj5qUoyiK AEIiNT7omr6DL2yDIRxU3hM5mo1MKfGF3mfgRUFPv42kg4rCD3C24m0BmaXY3/omTwTD 5hqg== Received: by 10.236.143.4 with SMTP id k4mr15688752yhj.111.1344399525919; Tue, 07 Aug 2012 21:18:45 -0700 (PDT) Received: from [192.168.2.5] (adsl-65-0-123-153.jan.bellsouth.net. [65.0.123.153]) by mx.google.com with ESMTPS id k22sm12812464ann.1.2012.08.07.21.18.43 (version=SSLv3 cipher=OTHER); Tue, 07 Aug 2012 21:18:45 -0700 (PDT) Message-ID: <5021E8A2.2090908@gmail.com> Date: Tue, 07 Aug 2012 23:18:42 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Firefox/14.0.1 SeaMonkey/2.11 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Want to seriously test a NEW hard drive References: <501E6AFA.4000205@gmail.com> <50219626.5010806@gmail.com> <5021CC94.3050701@gmail.com> <1344398107.8010.20.camel@moriah> In-Reply-To: <1344398107.8010.20.camel@moriah> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 7feb0d8f-a51c-4197-aa09-952c818d15c9 X-Archives-Hash: 5833739972b085a5dbc036b691878162 William Kenworthy wrote: > On Tue, 2012-08-07 at 21:19 -0500, Dale wrote: >> Paul Hartman wrote: >>> On Tue, Aug 7, 2012 at 5:26 PM, Dale wrote: >>>> I didn't know you could do low level formats anymore. Really? What >>>> package provides that? Hmmm, I'm thinking about those HOURS spent >>>> formatting a 100Mb drive and then thinking about how long it will take >>>> to do a 3Tb drive. O_O I mean really O_O. LOL >>> hdparm provides it. Do a search for "ATA secure erase" or "enhanced >>> secure erase". It is as close as there is to a low-level format in > ... >> I have seen where people use dd to do this sort of thing to. I read >> somewhere that if you do a dd and put in all 1's, then all 0's then back >> again that it is very hard to get any data back off the drive. I think >> if you do it like over a dozen times, it is deemed impossible to get >> anything back. I think that is the Government standard of it's gone. >> >> 4 or 5 hours huh. I guess drives are a lot faster now. Back in the >> late 80's or early 90's, it took that long for those whimpy little 100Mb >> drives. Ooops, my ages is showing again. lol >> >> I got to go read up on hdparm. I already have it installed here. I'm >> not planning to use this part but do want to read up on this. >> >> Thanks. >> >> Dale >> >> :-) :-) >> > > Goggle have a well known document > (http://research.google.com/archive/disk_failures.pdf) where they > analysed hard drive failures for a very large number of drives ... the > basic upshot is that a very large portion of failures happen with no > pre-warning, so testing a drive like you are proposing not going to > prove a thing. > > They also found that smart (is quite dumb) and its tests were of little > use. > > And high temperatures and work loads were also not a reliable guide to > trends in failure rates, both of which which surprised me. > > Some of those bathtub curves that I was trained on when setting > maintenance schedules dont hold water here! > > This anaysis of the paper looks quite good if you want the lite view: > http://storagemojo.com/2007/02/19/googles-disk-failure-experience/ > > BillK > > > > BillK > > Well, I am going by actual real experiences from other users of this model of drive. I don't know what google was testing but I would bet it is not the drive model I just bought. The users who bought this exact model drive report that most failures are either out of the box or within a few weeks to a month. I'm just going to try to increase my odds even if it is just a little bit. Smart may not always predict a failure but it is better than nothing at all. Would you rather have a tool that may predict a failure or no tool at all? Me, I'd rather have something that at least tries too. The one drive I had to go bad, Smart predicted it very well. It said I had about 24 hrs to get my stuff off. Sure enough, the next day, it wouldn't do anything but spin. Without Smart and its prediction, I'd have lost the data on the drive with no warning at all. A couple questions. What if while I am testing this drive, it dies? Does that prove that my testing benefited me then? Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!