From owner-freebsd-bugs  Wed Mar  5 04:50:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA15454
          for bugs-outgoing; Wed, 5 Mar 1997 04:50:03 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA15448;
          Wed, 5 Mar 1997 04:50:01 -0800 (PST)
Date: Wed, 5 Mar 1997 04:50:01 -0800 (PST)
Message-Id: <199703051250.EAA15448@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: j@uriah.heep.sax.de (J Wunsch)
Subject: Re: kern/2873: Tahiti MO disk and od driver
Reply-To: j@uriah.heep.sax.de (J Wunsch)
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/2873; it has been noted by GNATS.

From: j@uriah.heep.sax.de (J Wunsch)
To: neil.long@materials.oxford.ac.uk
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/2873: Tahiti MO disk and od driver
Date: Wed, 5 Mar 1997 09:48:43 +0100

 As Neil wrote:
 
 > disklabel -r -w od0 auto gives
 > /kernel: od0(aha0:5:0): MEDIUM ERROR info:2 asc:11,0 Unrecovered read error
 > Mar  4 13:14:11 njl /kernel: od0(aha0:5:0): MEDIUM ERROR asc:13,0 Address mark not found for data field
 
 Hmm, that's the second block which is dead (``info: 2'').  I'm not
 sure whether the drive can remap bad blocks.  You could give it a try
 on mode page 1.  Maybe reformatting would be a help?
 
 > The disk is fine when used on a DOS PC (Corel SCSI drivers) or an SGI using 
 > SG's fx and mkfs (uses scsi info not disktab)
 
 Perhaps they implement the equivalent to bad144?  I don't think our
 SCSI device drivers do implement bad144 at all.  Maybe the od driver
 should, however.
 
 Short of this, i don't think FreeBSD can do much with a defect medium.
 I tend to close the PR after the discussion.
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)