From owner-freebsd-stable Mon Dec 13 13:46:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 3D9D714FB9 for ; Mon, 13 Dec 1999 13:46:32 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from bolero.rahul.net by bolero-x.rahul.net with SMTP id AA07879 (5.67b8/IDA-1.5 for ); Mon, 13 Dec 1999 13:45:58 -0800 Received: from q.bolero.rahul.net (bolero.rahul.net [192.160.13.1]) by bolero.rahul.net (Postfix) with SMTP id 609873FF03 for ; Mon, 13 Dec 1999 13:45:57 -0800 (PST) Received: (qmail 7874 invoked from network); 13 Dec 1999 21:45:57 -0000 Received: from waltz.rahul.net (192.160.13.9) by bolero.rahul.net with SMTP; 13 Dec 1999 21:45:57 -0000 To: freebsd-stable@freebsd.org Subject: how to rewrite the data field replaceable unit? Date: Mon, 13 Dec 1999 13:45:56 -0800 From: Rahul Dhesi Message-Id: <19991213214557.609873FF03@bolero.rahul.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ FreeBSD 3.0 Release ] I have a scsi disk with two unreadable blocks. The error messages generated by the kernel include this: (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 I would like to follow the recommendation. How do I rewrite the data field replaceable unit? What exactly is a data field replaceable unit? I did check with 'camcontrol modepage -m 1 -P 3' and confirmed that the values of AWRE and ARRE are both 1. So the SCSI disk is already doing all the bad block mapping that it can. No response from freebsd-questions, hence I try here. Also, after I sent the above message, I tried using the 'badsect' program. The partition containing the bad blocks is a ccd device, so I did: cd / mkdir BAD badsect BAD n ... where the list of bad blocks was as reported by fsck. One of the bad blocks did get converted into a file, but for the rest, 'badsect' reported that it was a non-data area and could not be attached. So now I have a ccd filesystem with some bad blocks that can't be collected by badsect, but which do generate read errors during normal operation. Is there any workaround for this? Rahul Dhesi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message