From owner-freebsd-questions  Tue Feb 27 13:06:46 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA03391
          for questions-outgoing; Tue, 27 Feb 1996 13:06:46 -0800 (PST)
Received: from cesium.clock.org (cesium.clock.org [17.255.4.43])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA03380
          Tue, 27 Feb 1996 13:06:41 -0800 (PST)
Received: by cesium.clock.org with SMTP id <5633>; Tue, 27 Feb 1996 13:06:22 -0800
To: Alexander Seth Jones <ajones@ctron.com>
cc: hackers@freefall.freebsd.org, questions@freefall.freebsd.org
Subject: Re: more timeouts 
In-reply-to: Your message of "Fri, 23 Feb 1996 08:31:44 PST."
             <9602231631.AA14380@thoth> 
Date: 	Tue, 27 Feb 1996 13:06:10 -0800
From: Sean Doran <smd@cesium.clock.org>
Message-Id: <96Feb27.130622pst.5633@cesium.clock.org>
Sender: owner-questions@FreeBSD.ORG
Precedence: bulk


In message <9602231631.AA14380@thoth>, Alexander Seth Jones writes:

| I'm also seeing a timeout with my IDE harddrive:
| 
|   wd0: interrupt timeout:
|   wd0: status 58<seekdone,drq> error 0
|   wd0: interrupt timeout:
|   wd0: status 58<seekdone,drq> error 1<no_dam>

I'm also seeing alot of these, although the status numbers
vary in the 50s.  After the "error 1<no_dam>", the 2.1
kernel on the Thinkpad boot.flp that Nate Williams put up
for FTP, and the 2.2 snapshot GENERIC kernel both hang on
any disk operation.  

I'd get this hang after random amounts of disk activity.

I was thinking that it was due to bad blocks, so I tried
bad144 -s -v wd0, which would hang after reporting that it
had gotten to 273420.  (This is reproducible, even after
many bad144 -a commands).

There are some bad blocks on the disk; MS-DOS sees them and
marks them.  Is there any way to translate what, say,
scandisk (or other tools) reports as badblocks into
something I can feed manually or automagically into bad144?

Even if there is a way to do this, is this the source of my
problem?

	Sean.