On Fri, Mar 09, 2007 at 09:26:49AM -0800, Anil Gopinath wrote:
> 
> I have two maxtor disks showing a similar problem. Not
> sure if its exactly the same issue. smartctl tests
> indicated that the disks are ok. I will try your patch
> and let you know if it fixes the issues.
> 
> More detailed info:
> 
> satalink0: port 0: device present, speed: 1.5Gb/s
> wd0 at atabus0 drive 0: <Maxtor 6V160E0>
> wd0: drive supports 16-sector PIO transfers, LBA48
> addressing
> wd0: 149 GB, 310101 cyl, 16 head, 63 sec, 512
> bytes/sect x 312581808 sectors
> wd0: 32-bit data port
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA
> mode 6 (Ultra/133)
> wd0(satalink0:0:0): using PIO mode 4, Ultra-DMA mode 6
> (Ultra/133) (using DMA)
> boot device: wd0
> 
> <snip>
> 
> satalink0:0:0: lost interrupt
>         type: ata tc_bcount: 51200 tc_skip: 0
> satalink0:0:0: bus-master DMA error: missing
> interrupt, status=0x21
> satalink0:0:0: device timeout, c_bcount=51200, c_skip0
> wd0k: device timeout writing fsbn 18342834 of
> 18342834-18342933 (wd0 bn 45613236
> ; cn 45251 tn 3 sn 39), retrying

Probably not the same issue; the block numbers don't match the 128GB
limit, and the issue doesn't lead to a timeout. I suspect hardware
issue here: SATA cable, power supply not strong enough, etc  ...

> 
> <snip> after a reboot and several hours later: 
> 
> satalink0:0:0: lost interrupt
>         type: ata tc_bcount: 51200 tc_skip: 0
> satalink0:0:0: bus-master DMA error: missing
> interrupt, status=0x21
> wd0k: device timeout writing fsbn 18342834 of
> 18342834-18342933 (wd0 bn 45613236
> ; cn 45251 tn 3 sn 39), retrying
> satalink0 channel 0: reset failed for drive 0
> satalink0:0:0: wait timed out
> wd0k: device timeout writing fs

It seesm to always have trouble at the same place; maybe it's a media issue
after all.
Does a dd if=/dev/rwd0d of=/dev/null bs=64k always fail at the same place ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--