Hi Piete,
>>I cannot see "03/11" anywhere -- did you reverse map "MEDIUM ERROR" ?
Yes, long years of painful experience. 03/11 is reported by the drive when
read retries are exhausted and a sector is not readable.
>>SO: Read (10) 00 00 7d a6 c0 00 00 80 00
>>... + ?1 ?2 ?3 +
In a message dated 99-11-29 06:03:16 EST, you write:
<< The report was:
scsi0: MEDIUM ERROR on channel 0, id 5, lun 0, CDB:
Read (10) 00 00 7d a6 c0 00 00 80 00
Current error sd08:50: sense key Medium Error
Additional sense indicates Unrecovered read error
scsidisk I/O
Your comments were quite right, until recently. UDMA33 and 66 approach very
closely their theoretical rate on the bus. The overheads are very low, and
on good drives, the burst is maintained for the entire transfer. IBM has
included the new Qing protocol in their IDE drives. Even on a single
Hmm,
If the controller is built right, there is some potential for a performance
increase. The idea is to have more than one drive simultaneously reading
into it's buffer (they run about .5M these days). Assuming each drive stays
busy, ie, as would be the case in large sequential transfers,
