From owner-freebsd-questions  Tue Jul 16 11:08:11 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA18753
          for questions-outgoing; Tue, 16 Jul 1996 11:08:11 -0700 (PDT)
Received: from nol.net (zac@dazed.nol.net [206.126.32.101])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA18740
          for <freebsd-questions@freebsd.org>; Tue, 16 Jul 1996 11:08:05 -0700 (PDT)
Received: (from zac@localhost) by nol.net (8.7.5/NOL - 8.*) id NAA17387 for freebsd-questions@freebsd.org; Tue, 16 Jul 1996 13:07:07 -0500 (CDT)
Date: Tue, 16 Jul 1996 13:07:07 -0500 (CDT)
From: Doug Swarin <zac@nol.net>
Message-Id: <199607161807.NAA17387@nol.net>
X-AUTH: NOLNET SENDMAIL AUTH
To: freebsd-questions@freebsd.org
Subject: Disk error problem
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm having a problem with my disk (and I'm aware its a hardware problem)
but I cannot use bad144 to mark the sectors that are bad on the disk as
bad. Whenever something tries to read the damaged sectors FreeBSD does
not error out but rather continually gives me:
wd0: soft error reading fsbn 1808??? of 1808???-1808??? (bn 2071117
[track/cyl]) error 1<no_dam>
and I cannot do anything (break out of the program, reboot the machine,
etc) but must reboot.

Does anyone know of a way I can tell FreeBSD that these blocks are bad
without using bad144?

Thanks in advance

Doug