Sigh.  My nice little 486DX/33 PC installation of NetBSD/i386 1.0 was doing
just fine until recently, when all of a sudden it started getting struck by a
rash of disk errors.

On practically every sync() now, I get a small rash of the error messages in
the Subject: field; more specifically, the last few have been:

ias-pc:1:30 [/var/log] % tail -5 messages
Apr 21 23:29:01 /netbsd: sd0(aha0:0:0): medium error, info = 441482 (decimal)
Apr 21 23:29:01 /netbsd: sd0(aha0:0:0): medium error, info = 441482 (decimal)
Apr 21 23:29:22 /netbsd: sd0(aha0:0:0): medium error, info = 441494 (decimal)
Apr 21 23:29:23 /netbsd: sd0(aha0:0:0): medium error, info = 441494 (decimal)
Apr 21 23:29:29 /netbsd: sd0(aha0:0:0): medium error, info = 441496 (decimal)

(Removed the machine name to fit inside 80 columns)

The machine has an Adaptec 1542CF SCSI controller and a Seagate ST31200N 1.06
Gb disk drive:

...
Apr 21 17:25:20 ias-pc /netbsd: aha0: 1542C/CF detected, unlocking mailbox
Apr 21 17:25:20 ias-pc /netbsd: aha0 at isa0 port 0x330-0x333 irq 11 drq 5
Apr 21 17:25:20 ias-pc /netbsd: scsibus0 at aha0
Apr 21 17:25:21 ias-pc /netbsd: aha0 targ 0 lun 0: <SEAGATE ST31200N      8630>
SCSI2 direct fixed
Apr 21 17:25:21 ias-pc /netbsd: sd0 at scsibus0: 1006MB, 2700 cyl, 9 head, 84
sec, 512 bytes/sec
...

These messages have been happening for the last week or so, and all the "info"
numbers (are these physical disk sector numbers?) are all around this 4414xx
range.

As I'm a SPARC person by nature and a NetBSD/i386 neophyte, any suggestions
regarding how & what to do to deal with this would be appreciated.  My naive
reading says that the disk is returning a hard media error at those blocks,
and somehow I'll have to do a sort | uniq on those "info" numbers to glean a
list of numbers that (I presume) will have to be fed to "badsect" or "bad144"
or somesuch ... Yes?

Please reply to me directly as I'm not (yet) on the port-i386 list ...

Thanks,

	- Greg