From owner-freebsd-hardware Tue Jun 16 13:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16076 for freebsd-hardware-outgoing; Tue, 16 Jun 1998 13:21:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA16070 for ; Tue, 16 Jun 1998 13:21:17 -0700 (PDT) (envelope-from richard@pegasus.com) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id KAA15243; Tue, 16 Jun 1998 10:20:35 -1000 Date: Tue, 16 Jun 1998 10:20:35 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199806162020.KAA15243@pegasus.com> In-Reply-To: Sean Eric Fagan "scsi disk question" (Jun 16, 10:47am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Sean Eric Fagan , hardware@FreeBSD.ORG Subject: Re: scsi disk question Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org } } I posted about this to -stable this morning, but now it's a hardware question } I think :). } } I've got an IBM DCAS 3216W (2G UW drive) as my root disk, sd0. After a power } failure, /var/news/history.pag contained a non-recoverable bad block -- the } kernel would try four or five times to access it, and then would fail, } resulting in an I/O failure. This persisted after a reboot. } } After I found the file with the bad block, I removed it, and recreated it; } this went well, and, so far, the system has continued to function. It would have been better to rename it to something like .bad-blocks. } } My question is: will the disk now ignore this bad block? Normally, I'd } assume it would (it being an intelligent, scsi disk with Read-Write Error } Recovery enabled), but, well, it didn't before :(. The drive knows nothing of filesystem file creation and deletion. You need to reformat the disk. By deleting the file you've put the bad block back into play. It will probably surface elsewhere. If you're not ready to reformat then you might fill the remaining free space on the disk with small files until the bad block resurfaces, and stash it out of the way. } } I'm currently planning on getting a new disk today, but I'd prefer not to if } possible, obviously :). } } Anyone know for sure? } Dunno. New bad blocks is a bad sign. Reformat and exercise (verify) the drive heavily to see if it will remain stable now. Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message