[1138] in linux-scsi channel archive
Re: medium error, what next?
daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Fri Dec 20 11:32:10 1996
Date: Fri, 20 Dec 1996 08:28:18 -0800
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: se@freebsd.org
CC: srb@cuci.nl, linux-scsi@vger.rutgers.edu, ncr53c810@colorado.edu
In-reply-to: <Mutt.19961220151946.se@x14.mi.uni-koeln.de>
Date: Fri, 20 Dec 1996 15:19:46 +0100
From: se@freebsd.org (Stefan Esser)
Set the AWRE and ARRE bits in the drive's SCSI mode page 1.
Then repeat the "dd ..." to scan the drive for bad blocks.
It is possible, that the bad block does persist, until it
is written to the next time. If you can read and write the
RAW device, you can easily accomplish that. Else you may
need to make a backup, recreate the file system and restore
the backup.
Mode page 1 can be edited with the command
scsi -e -m 1 -f /dev/rsd0
under FreeBSD.
If there is no such tool to do this under Linux, you'll have
to resort to one of the public domain DOS tools. (Sorry, can't
help finding such a thing, since I don't run DOS. But I do
know, that they exist ...)
There is indeed such a tool, Eric Youngdale's scsiinfo package:
SCSI Info 1.6 (scsiinfo)
tsx-11.mit.edu
/pub/linux/ALPHA/scsi/scsiinfo-1.6.tar.gz
Leonard
