From owner-freebsd-hackers@freebsd.org Thu Jul 5 14:53:26 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAD971030421 for ; Thu, 5 Jul 2018 14:53:25 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E0C180B3E; Thu, 5 Jul 2018 14:53:25 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.15.2) with ESMTPS id w65EibbK017386 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 5 Jul 2018 16:44:37 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Received: from localhost (puchar-wojtek@localhost) by puchar.net (8.15.2/8.15.2/Submit) with ESMTP id w65EiWew017383; Thu, 5 Jul 2018 16:44:32 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Date: Thu, 5 Jul 2018 16:44:32 +0200 (CEST) From: Wojciech Puchar To: Lev Serebryakov cc: George Mitchell , FreeBSD Hackers Subject: Re: Confusing smartd messages In-Reply-To: <51eb8232-49a7-0b3a-2d0f-9882ebfbfa1d@FreeBSD.org> Message-ID: References: <51eb8232-49a7-0b3a-2d0f-9882ebfbfa1d@FreeBSD.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 14:53:26 -0000 >> okay. What's the recommended action at this point? -- George > > In my experience it is begin of disk death, even if overall status is > PASSED. It could work for month or may be half a year after first > Offline_Uncorrectable is detected (it depends on load), but you best bet > to replace it ASAP and throw away. well my disk had this and live happily for 3 years. It JUST means that some sectors are unreadable which may be a reason that at some some write got wrong because of hardware problem. But this problem may be - and possibly were - powerdown while writing, or power spike. the media itself could be fine. the best action in such case is to force rewrite whole drive with some data. with gmirror it is as easy as first checking second drive for no errors, then forcing remirror.