From owner-freebsd-questions Thu Aug 1 09:38:07 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA23951 for questions-outgoing; Thu, 1 Aug 1996 09:38:07 -0700 (PDT) Received: from al.imforei.apana.org.au (root@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA23946 for ; Thu, 1 Aug 1996 09:38:00 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.7.5/8.7.3) id CAA15348; Fri, 2 Aug 1996 02:07:52 +0930 (CST) From: Peter Childs Message-Id: <199608011637.CAA15348@al.imforei.apana.org.au> Subject: Bad bits on drive... To: sa-feeds@tierzero.apana.org.au Date: Fri, 2 Aug 1996 02:07:51 +0930 (CST) Cc: freebsd-questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL13 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Gday. I've got two old micropolis 330mb scsi drives which i interleave with the ccd device driver (freebsd 2.1.5) and use for my web spool, news spool, and scratch pad. They had been working just fine but now have developed some bad blocks that cause "/kernel MEDIUM ERROR" 's (Unrecovered read errors) I've newfs'd and fsck'd the drives, and it keeps telling me that there are bad blocks, but doesn't seem to mark them bad... (i newfs'd the ccd device) Is there some way i can mark the bad blocks bad and continue with life? Ta. Regards, Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds The internet is full, please try again in half an hour...