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 5611413877A for ; Sun, 27 Jul 2014 10:24:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EAE40E0C36; Sun, 27 Jul 2014 10:24:02 +0000 (UTC) Received: from mail-yh0-f41.google.com (mail-yh0-f41.google.com [209.85.213.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D9445E0C1C for ; Sun, 27 Jul 2014 10:24:01 +0000 (UTC) Received: by mail-yh0-f41.google.com with SMTP id b6so4168121yha.28 for ; Sun, 27 Jul 2014 03:24:01 -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:content-type:content-transfer-encoding; bh=ZB2p2x6rZWH2XuPWdqdtZoOEg7KeQNuz2IVqWDunCoo=; b=Ip8JyeWj6bdky+9iP6BNOV4dLSZUR4GLlaBrNdM2warLSlHsbRRKMox0an/JXfhSEM XTLOKBOVwm/2N3UYolGAoLZ780sX83EGfW9LP7W0LHNLL1VAhUd6/wvemUVzc0UnH50Y dTEXEMX7+FGscn1vSSi06qA+zac5drAImuDSLw9HNXbDb9CNg5gg9XNZafCttrCTNv6Y Y6ZUgq57Y0DvH16j6vbjF075UBG3seot3chUnO78HiRXWlkXlWbu6o7CYaVGWA3vIPNU E99FzGk5lwZH5+w4jLiAmzbBnIWLBK5uvvNxJr3JjPka3+TlZqTi72WbycLRvMxxnIlm U6Zw== X-Received: by 10.236.119.101 with SMTP id m65mr1891509yhh.136.1406456641011; Sun, 27 Jul 2014 03:24:01 -0700 (PDT) Received: from [192.168.2.5] (adsl-65-0-122-210.jan.bellsouth.net. [65.0.122.210]) by mx.google.com with ESMTPSA id n6sm16021112yha.20.2014.07.27.03.24.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Jul 2014 03:24:00 -0700 (PDT) Message-ID: <53D4D33F.3020007@gmail.com> Date: Sun, 27 Jul 2014 05:23:59 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1 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] Contradictionary behaviour of SMART on hds ?!? References: <20140727101247.GA3817@solfire> In-Reply-To: <20140727101247.GA3817@solfire> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 19ade1c8-6e20-444e-b344-c373e8b14480 X-Archives-Hash: 76d73f2ca2f048e1f893371e36e7182f meino.cramer@gmx.de wrote: > Hi, > > after finding a bad sector on my hd (see previous thread) a read a lot > stuff about SMART, smartctl and such to determine wether and how > severe is a bad sector and how to cope with it. > > There is (at least ;) one thing I dont understand: > > On the one hand, the surface test (extended offline and such) aborts > as soon the first read fgailure happens. > > On the other hand it is said: If the count of bad sectors increases > over time it is time to change the hd. > > How can the second happen, if the first is true??? > > Best regards, > mcc > > I am by no means a expert on this but I'll try to provide some info, which others may correct. ;-) I had a situation similar to yours a few months ago. I had a bad spot that popped up. After some effort, I got the drive to mark that as bad. Now, from my understanding, the drive sort of has some extra space that it can use if needed. However, at some point it will run out if you have spots going bad one after another. Again, my understanding. Let's say it has 200 extra spots. You then run the test or the drive detects on its own and finds a bad spot. It marks that spot as bad and then uses one of the extra spots. So, if you have 201 spots to go bad, you fresh out of luck. Again, that's my understanding of this. Now can someone else that knows even more than me explain this better? :-D Dale :-) :-)