From owner-freebsd-questions@freebsd.org Wed Aug 3 12:32:24 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7563CBAA726 for ; Wed, 3 Aug 2016 12:32:24 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4787C19FB for ; Wed, 3 Aug 2016 12:32:23 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-209-65.knology.net [216.186.209.65] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u73CWLNL019126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 3 Aug 2016 07:32:22 -0500 Subject: Re: Ominous smartd messages .... To: freebsd-questions@freebsd.org References: <020caa94-b329-d5a6-5bd4-bfcc575c039f@freebsd.org> From: "William A. Mahaffey III" Message-ID: <10b1ff8b-c738-3cee-30bb-9812f75436c1@hiwaay.net> Date: Wed, 3 Aug 2016 07:37:50 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <020caa94-b329-d5a6-5bd4-bfcc575c039f@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Aug 2016 12:32:24 -0000 On 08/03/16 07:24, Matthew Seaman wrote: > On 08/03/16 04:41, William A. Mahaffey III wrote: >> My question is: Are these messages benign, or am I in the market for >> more hardware ? *ANY* more questions, please ask. TIA & have a good one. > It doesn't look particularly good. Do you run the smartd selftests at > all? Worth giving that a go -- > > # smartctl -t long /dev/ada5 > > This can be done while the disk is in use without upsetting anything. > It will scan the disk for unreadable areas. The disk does have a number > of spare sectors it can use instead of any broken ones, but it generally > needs to see a failed write to the affected area to trigger the > substitution mechanism. Once you run out of substitute sectors, the > disk is basically toast and should be replaced. With modern drives, > seeing that mechanism in use at all typically means the drive is on the > downward spiral and you should plan on replacing it PDQ. > > Cheers, > > Matthew > > Thanks, I kicked that off just now, it says it will take 169 min. to complete, so we'll see. No more new messages overnight, maybe my luck is good .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.