On Wed, 2 Apr 2008, Tejun Heo wrote:
I've never really seen transmission errors resulting in FLUSH failure.
All that needs to be transferred is the opcode and according to the
SMART log, the drive got the command right but still aborted it. The
only thing I can think of right now is that dd over the whole disk put
sanity into the disk but it's just a wild speculation.
The entire disk was overwriten from /dev/zero once, no errors and no
re-allocated sectors.
Yeap, I would love to see whether the problem reproduces itself when
moved back to the original port.
Please note that this problem did start with the disk on the third port,
and that it is currently on the second port. same errors on both port, but
only with this specific disk. the three other disks have not logged any
errors.
I got 3 errors during the night, first one (same again) pasted here:
Apr 2 04:14:17 envy kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 2 04:14:17 envy kernel: ata2.00: irq_stat 0x40000001
Apr 2 04:14:17 envy kernel: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Apr 2 04:14:17 envy kernel: res 51/04:00:0a:24:f9/00:00:00:00:00/a9 Emask 0x1 (device error)
Apr 2 04:14:17 envy kernel: ata2.00: status: { DRDY ERR }
Apr 2 04:14:17 envy kernel: ata2.00: error: { ABRT }
Apr 2 04:14:17 envy kernel: ata2.00: configured for UDMA/133
Apr 2 04:14:18 envy kernel: ata2: EH complete
Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB)
Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] Write Protect is off
Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
There has been some other errors aswell, i am uploading the entire
"kern.log" to http://tlund.pp.se/envy4_kern.txt
//tlund
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
