Comment 17 for bug 279693

Revision history for this message
Jaime R. Garza (garzaj) wrote :

I have the same problem using Intrepid on amd64, but only with one of my disks, I have three disks, all in the same system, two work perfectly well and one cannot be mounted. They are all resierfs, so I checked the disk with "fsck.resierfs /dev/sdc1" and it takes toooo long but finally says is fine. The problem is that I get:

Jan 21 17:29:59 deflagmator kernel: [ 86.604101] ata4.00: status: { DRDY }
Jan 21 17:29:59 deflagmator kernel: [ 86.604113] ata4: hard resetting link
Jan 21 17:30:00 deflagmator kernel: [ 87.080072] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 21 17:30:00 deflagmator kernel: [ 87.105231] ata4.00: configured for UDMA/33
Jan 21 17:30:00 deflagmator kernel: [ 87.105262] ata4: EH complete

This problem has nothing to do with the chipset as many implied, I changed cables, moved all three disks around and only one disk failed, the problem is the Harddisk:

Maxtor DiamondMax 10
Model:6V250F0
250GB SATA 3.0Gb HDD

My other two disks are also SATA, one Seagate Baracuda 500GB and one Hitachi 164GB, both work perfectly well on the same system.

I noticed using Hardy, this problem will come, but only with soft restart. If I turned the computer completely off, this problem didn't happen on Hardy.

Cheers!