From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E9EFD1382C5 for ; Tue, 23 Jun 2020 18:33:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5FD41E0919; Tue, 23 Jun 2020 18:32:58 +0000 (UTC) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E49FDE08D3 for ; Tue, 23 Jun 2020 18:32:57 +0000 (UTC) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id B09559E5 for ; Tue, 23 Jun 2020 14:32:55 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute7.internal (MEProxy); Tue, 23 Jun 2020 14:32:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aeam.us; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=aPZGl0ph1BJIStLJlpQdhq+ljsEMYZS Lg8cGOvWPqpw=; b=gOc8MYxYg5lHaoNXr5wJpc+bz82ic5GKQKuVR43MhrEZfeG qCqu/HW/8yu27eAZG2UTqZ+zvO/MV7A50E6+FBs21S5QkBKTUNNyjvnKSlS3tw/l dy9Vet1a7sv5pXy5sqpM/dHOUZ17tS84KGBxG+bzPED02WYthj4dF+tQJ3b6Oq9B btoop0A3jk1rVWVGGgIU3Tt810u2TgqjwUWu26cmfgizhf4BB6ccWUdMBzQhRfV2 7pxIKMa8NBPouzGZv5jO4zVq62Bxrr6no7OgKyXhWG8oIk7Ac149KfFqOQHzqFoh U5E/0o1jh7rJwW0HuIKCFOVtXhIDcFXNPXQCW0Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=aPZGl0 ph1BJIStLJlpQdhq+ljsEMYZSLg8cGOvWPqpw=; b=p/WGrqHpakIV5geXSCfxrm PqknO69k5qc7AoIGwBBzs2hCY1UjBxUoGp0wcDUpEzRXmPmYtsksZXBVK8PkLy5k lVr9x70EKFFcU2cJgiDQTHGdlJzxrDNCx1J3xVVencDBgCREW5KbWU+sIreXipc7 SIvZY9/RId0ErpQdhz5eemk+OzxOoPg2l7eubk2aG1LeOk8z6yUQWxdB+byBMybd xNcWURce7cvNiIYAjCtp/2EB3QWNj4pRv1MrZr5bj+kqZ7w02EDG64ZuHsP0HE3u vpgoPWEuhv0HTXumhvhn/jKEx327OKesThrwltExwxVoMkxySUF/1oFCgoLGCHJQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudekhedguddttdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreerjeenucfhrhhomhepfdfuihguucfuphhrhidfuceoshhiugesrggvrghmrdhu sheqnecuggftrfgrthhtvghrnhepgeeftddtgfduffdvgedugeelkeeljeefueehhfejge fhfedvkeevueffgfeivdevnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepshhiugesrggvrghmrdhush X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 389E766007F; Tue, 23 Jun 2020 14:32:54 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-dev0-543-gda70334-fm-20200618.004-gda703345 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply Mime-Version: 1.0 Message-Id: <27641ea5-ecc3-4e7c-a799-139680335d6b@www.fastmail.com> In-Reply-To: <51f37de0-c955-c114-56bd-672a9e064e24@gmail.com> References: <6d77acb3-5754-06cb-b8ef-2f1a5d7d8084@gmail.com> <20200615231836.xje3kkkihsxrvhaz@grusum.endjinn.de> <158351d5-27cc-88d0-951c-893d0b5ad8aa@gmail.com> <1be400f1-9f5f-4e4a-ba8d-0fb7f8609a14@www.fastmail.com> <51f37de0-c955-c114-56bd-672a9e064e24@gmail.com> Date: Tue, 23 Jun 2020 13:32:33 -0500 From: "Sid Spry" To: gentoo-user@lists.gentoo.org Subject: =?UTF-8?Q?Re:_[gentoo-user]_Re:_Testing_a_used_hard_drive_to_make_SURE_i?= =?UTF-8?Q?t_is_good.?= Content-Type: text/plain X-Archives-Salt: 6ef612bc-3695-49b8-88c2-4f59bf5d2a16 X-Archives-Hash: 479f26c77ae1804257eca10ee7494ba1 On Tue, Jun 23, 2020, at 12:26 PM, Dale wrote: > SMART can't predict the future so it can only monitor for the things > it can see. If say a spindle bearing is about to lock up suddenly, > SMART most likely can't detect that since it is a hardware failure that > can't really be predicted. We may be able to hear a strange sound if we > lucky but if it happens suddenly, it may not even do that. While SMART > can't predict all points of failures, it can detect a lot of them. Even > if the two drives I had failed with no warning from SMART, I'd still > run it and monitor it. Using SMART can warn you in certain situations. > If a person doesn't run SMART, they will miss those warnings. > > SMART isn't perfect but it is better than not having it all. > Well, in theory SMART should be able to predict hardware failures like that through N-th order effects that percolate up to read and write statistics. In practice it seems to be guessing badly. The danger of SMART is that rate of false negatives is so high (IME) that you might erroneously think a drive is not going to fail and putting off a backup. A good backup policy should mitigate this, but you still might plan around drive lifetime SMART predicts before realizing they are or can be bad predictions.