I get these errors on my 300GB drives until the server crashes. The server
is a HP Proliant DL385 with Netbsd 2.0(amd64) and an adaptec SCSI
controller. Since its an amd64 server Im using this mail list...

Copied 8 bytes of sense data offset 12: 0xf0 0x0 0x1 0x13 0xbb 0x7b 0x5d
0x28
sd1(ahd0:0:1:0):  Check Condition on CDB: 0x28 00 13 bb 7b 3f 00 00 80 00
    SENSE KEY:  Recovered Error
   INFO FIELD:  331053917
     ASC/ASCQ:  No Additional Sense Information

Details about the SCSI adapter
ahd0 at pci5 dev 7 function 0
ahd0: Enabling 39Bit Addressing
ahd0: interrupting at ioapic3 pin 2 (irq 10)
ahd0: aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs
scsibus0 at ahd0: 16 targets, 8 luns per target

Details about the drive
sd1 at scsibus0 target 1 lun 0: <COMPAQ, BD3008856C, HPB2> disk fixed
sd1: 279 GB, 78753 cyl, 8 head, 930 sec, 512 bytes/sect x 585937500 sectors
sd1: sync (6.25ns offset 127), 16-bit (320.000MB/s) transfers, tagged
queueing

Heres a response from HP tech support...

Quote:
It is uncertain if the adaptec driver for NetBSD can handle the re-mapping
or handle a burst of re-mappings.  It is suspect that the NetBSD adaptec
driver is having trouble remapping unreadable hard drive blocks.  The driver
may be capable of handling an occasional re-map but if a burst of re-maps is
required it may have trouble handling it.   It would be beneficial if you
could contact the NetBSD community to find out if the Adaptec driver handles
re-mapping and if so forward the error information to them for analysis.
Including the firmware revision of the Adaptec card along with the drive
model number and firmware revision would be beneficial to the community.  An
ideal situation would be to use SmartArray controllers, unfortunately NetBSD
only supports the low-end SmartArray controllers from HP.  If the drives
were on SmartArray controllers then the re-mapping functions would be
transparent to the operating system.
Unquote:

Thanks


Derrick