From owner-freebsd-hackers Tue Nov 21 16:58:07 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA13494 for hackers-outgoing; Tue, 21 Nov 1995 16:58:07 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA13481 for ; Tue, 21 Nov 1995 16:58:04 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id QAA07511; Tue, 21 Nov 1995 16:57:57 -0800 From: Julian Elischer Message-Id: <199511220057.QAA07511@ref.tfs.com> Subject: Re: Help! I got a bad block.... To: hasty@rah.star-gate.com (Amancio Hasty Jr.) Date: Tue, 21 Nov 1995 16:57:57 -0800 (PST) Cc: hackers@FreeBSD.org In-Reply-To: <199511212145.NAA00231@rah.star-gate.com> from "Amancio Hasty Jr." at Nov 21, 95 01:45:55 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 593 Sender: owner-hackers@FreeBSD.org Precedence: bulk there is a program to do this in -current.. hmm lemme see hmmm I guess it's wrong.. what you need to do is: 1/ try wrote nulls to the block if that succeeds all's well.. fsck the drive 2/ use the scsi 'mode page editor' to set the remapping options ON (man 8 scsi) 3/ try write nulls to the block.. theoretically this hsould succeed, and the block should be automatically remapped.. > > > My system disk is dying and I need to remove an inode -- all I got is > the disk block number which fsck reports . > > BTW: Why can't fsck remove or mark bad scsi blocks? > > Tnks, > Amancio >