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 092C713877A for ; Wed, 25 Jun 2014 14:03:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AC624E092F; Wed, 25 Jun 2014 14:03:23 +0000 (UTC) Received: from mail-vc0-f193.google.com (mail-vc0-f193.google.com [209.85.220.193]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A6683E089E for ; Wed, 25 Jun 2014 14:03:12 +0000 (UTC) Received: by mail-vc0-f193.google.com with SMTP id il7so494341vcb.8 for ; Wed, 25 Jun 2014 07:03:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=VE3lw4o7Sn6SXzPZDDDcaXi24GuT/k3J8qtW6DFRRSo=; b=OHJV8pQXGlb9ykGVr153Tgxd2MgYntACpNeTlbCKTe5OwFv+U3rmTygHG2w6fjtgYr 22lmCK649ZcuvVRO1a4FEh1eFy0WjKxhI8jrYqyEhPK11J7pUneYJ4v2Gw7G1o9hB0F0 fUI0oASjAvnQiEGRiuYPEwqhuHFTNQS2mCEiqChZGtQNQOtYh/T+h3iyO4DMocdrO5O2 DBIsE6EUtk2H7UQK6Nio7BXwRPo1vfCG29qN41pHYjXbX5u+8aNywd2g0CXZqwaRYdsZ OddZazTQFVhM9cAWg/MumwNsfQyHhxfiNYdx9oT3MAIZdmXqvt/7jEMSjlGHB+Tp/hQy exBQ== 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 X-Received: by 10.52.135.7 with SMTP id po7mr1609373vdb.50.1403704991919; Wed, 25 Jun 2014 07:03:11 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.52.30.227 with HTTP; Wed, 25 Jun 2014 07:03:11 -0700 (PDT) In-Reply-To: <53AACB8D.6010300@gmail.com> References: <53AA050F.4070907@gmail.com> <49620f42-d9c3-43b1-9f01-1250e52eb950@email.android.com> <53AA587F.8090300@gmail.com> <53AA7D11.6070909@thegeezer.net> <53AA7EF5.2000903@gmail.com> <53AAA791.4050506@thegeezer.net> <53AACB8D.6010300@gmail.com> Date: Wed, 25 Jun 2014 10:03:11 -0400 X-Google-Sender-Auth: ZtxzvJ76GGAa2lSgtp0bjAnfObc Message-ID: Subject: Re: [gentoo-user] smartctrl drive error @60% From: Rich Freeman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: a0544695-8caa-4b17-88a9-cf14f148c867 X-Archives-Hash: b2223422421d7d5da02b246b14527971 On Wed, Jun 25, 2014 at 9:15 AM, Dale wrote: > thegeezer wrote: >> On 06/25/2014 08:49 AM, Dale wrote: >>> thegeezer wrote: >> this says there are 104 pending sectors i.e. bad blocks on the drive >> that have not been reallocatd yet > > Wonder why it hasn't? Isn't it supposed to do that sort of thing itself? > It can't relocate the sectors until it successfully reads them, or until something else writes over them. However, the last few drives I've had this happen to never really relocated things. If I scrubbed the drives mdadm would overwrite the unreadable sectors, which should trigger a relocation, but then a day or two later the errors would show up again. So, the drive firmware must be avoiding relocation or something. Either that or there is a large region of the drive that is failing (which would make sense) and I was just playing whack-a-mole with the bad sectors. In any case, if the drive is under warranty I've yet to have a complaint returning it with a copy of the smartctl output showing the failed test/etc. With advance replacement I can keep the old drive until the new one arrives. > I usually just run the test manually but I sort of had family stuff > going on for the past year, almost a year anyway. Sort of behind on > things although I have been doing my normal updates. rc-update add smartd default I don't know that I even had to configure it - it is set to email root@localhost when there is a problem. I also run mdadm to monitor raid. I don't think anybody makes a monitor for btrfs, though my boot is mirrored across all my btrfs drives using mdadm so a drive failure should be detected in any case. I need to check up on that, though - I'd like an email if something goes wrong with btrfs storage. > > I ordered a drive. It should be here tomorrow. In the meantime, I > shutdown and re-seated all the cables, power too. I got the test running > again but results is a few hours off yet. It did pass the short test > tho. I'm not sure that it means much. Short test generally doesn't do much - you need the long ones. I'd be shocked if it passed with offline uncorrectable sectors. And do check on your warranty. You can migrate all your data to the new drive, and then replace the old one as a backup disk. Either use it with raid, or as an offline backup. If you want to do raid you can set up mdadm with a degraded raid1 so that you can copy your data over from your old drive, and then when it is replaced you just partition the new one, add it to the raid, and watch it rebuild automatically. Rich