From owner-freebsd-questions@FreeBSD.ORG Thu Mar 12 16:28:55 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 410741065670 for ; Thu, 12 Mar 2009 16:28:55 +0000 (UTC) (envelope-from robin@reportlab.com) Received: from mail-bw0-f164.google.com (mail-bw0-f164.google.com [209.85.218.164]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9F68FC23 for ; Thu, 12 Mar 2009 16:28:54 +0000 (UTC) (envelope-from robin@reportlab.com) Received: by bwz8 with SMTP id 8so1040354bwz.43 for ; Thu, 12 Mar 2009 09:28:53 -0700 (PDT) Received: by 10.216.3.196 with SMTP id 46mr79956weh.205.1236875333016; Thu, 12 Mar 2009 09:28:53 -0700 (PDT) Received: from ?192.168.0.3? (host-82-44-127-245.static.telewest.net [82.44.127.245]) by mx.google.com with ESMTPS id g12sm1510790nfb.41.2009.03.12.09.28.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 12 Mar 2009 09:28:52 -0700 (PDT) Message-ID: <49B93846.9050703@chamonix.reportlab.co.uk> Date: Thu, 12 Mar 2009 16:28:54 +0000 From: Robin Becker User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: smartd errors again X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2009 16:28:55 -0000 I'm seeing these sorts of messages in syslog output > Mar 12 15:06:10 app3 smartd[519]: Device: /dev/ad4, 6 Currently unreadable (pending) sectors > Mar 12 15:06:10 app3 smartd[519]: Device: /dev/ad4, 6 Offline uncorrectable sectors > Mar 12 15:29:39 app3 kernel: ad4: FAILURE - READ_DMA status=51 error=40 LBA=151607951 > Mar 12 15:29:39 app3 kernel: g_vfs_done():ad4s1f[READ(offset=72458502144, length=16384)]error = 5 > Mar 12 15:30:25 app3 kernel: ad4: FAILURE - READ_DMA status=51 error=40 LBA=151607951 > Mar 12 15:30:25 app3 kernel: g_vfs_done():ad4s1f[READ(offset=72458502144, length=16384)]error = 5 > Mar 12 15:35:43 app3 smartd[519]: Device: /dev/ad4, 6 Currently unreadable (pending) sectors > Mar 12 15:35:43 app3 smartd[519]: Device: /dev/ad4, 6 Offline uncorrectable sectors > Mar 12 15:55:03 app3 kernel: ad4: FAILURE - READ_DMA status=51 error=40 LBA=151607951 > Mar 12 15:55:03 app3 kernel: g_vfs_done():ad4s1f[READ(offset=72458502144, length=114688)]error = 5 > Mar 12 16:05:28 app3 smartd[519]: Device: /dev/ad4, 6 Currently unreadable (pending) sectors > Mar 12 16:05:28 app3 smartd[519]: Device: /dev/ad4, 6 Offline uncorrectable sectors by searching through the filesystem I located a file which appears to contain the error. However, I am unable to write to this file (the recommended cure for bad blocks) I used > # dd if=/dev/zero bs=12544487 count=1 of=wow-22048.dmp.gz conv=notrunc > dd: wow-22048.dmp.gz: Input/output error > 1+0 records in > 0+0 records out > 0 bytes transferred in 1.894545 secs (0 bytes/sec) so am I forced to abandon this hard disk or is their some easy way to actually force a write that will make the disk bad block the wrong sectors. I looked in vain for my old bad blocking tools and indeed it seems lost+found is no longer here. This disk is supposedly only 433 hours old acording to the smartctl output (assuming I do need to regard the Hitachi numbers as being minutes). Any help would be appreciated. -- Robin Becker