From owner-freebsd-questions@FreeBSD.ORG Tue Nov 11 02:44:32 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FE1316A4D0 for ; Tue, 11 Nov 2003 02:44:32 -0800 (PST) Received: from highland.isltd.insignia.com (highland.isltd.insignia.com [195.74.141.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9777F43FDD for ; Tue, 11 Nov 2003 02:44:30 -0800 (PST) (envelope-from subscriber@insignia.com) Received: from dailuaine.isltd.insignia.com (dailuaine.isltd.insignia.com [172.16.64.11])hABAiSHw040237 for ; Tue, 11 Nov 2003 10:44:28 GMT (envelope-from subscriber@insignia.com) Received: from tomatin (tomatin [172.16.64.128])hABAiSSX000997 for ; Tue, 11 Nov 2003 10:44:28 GMT (envelope-from subscriber@insignia.com) From: Jim Hatfield To: freebsd-questions@freebsd.org Date: Tue, 11 Nov 2003 10:44:28 +0000 Organization: Insignia Solutions Message-ID: <3le1rv85dgvlb689e76shkqabf5bn4ecok@4ax.com> X-Mailer: Forte Agent 1.91/32.564 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.38 Subject: Any way to lock down disk errors? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 10:44:32 -0000 Strictly speaking OT but the machine is running FreeBSD. While copying a file I got I/O errors. The console shows: >ad0: hard error cmd=3Dread fsbn 31891359 of 31891359-31891486 = status=3D59 error=3D40 >ad0: hard error cmd=3Dread fsbn 31891231 of 31891231-31891486 = status=3D59 error=3D40 Given that the disk is just under three months old, is it worth doing anything other than getting it replaced? I have no other disk big enough to old the data on it so unless the supplier sends me a replacement ahead of me returning the faulty one it will be a pain. I have enough space to empty the partition with the error in, but I couldn't find anything in newfs or fsck which would let me map out selected blocks or to do a full write test of each block and map out bad ones. Is there such a beast?