Arch Linux

Hi there,

i am getting strange error messages + a lot of timeouts with 2.6.30-5. Also none of my pata drives (connected to a hpt370) are even there after booting...

Here is a snippet:

...
ata9: lost interrupt (Status 0x7f)
ata9: drained 2048 bytes to clear DRQ.
ata9.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata9.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata9.01: status: { DRDY }
ata9: link is slow to respond, please be patient (ready=0)
ata9: device not ready (errno=-16), forcing hardreset
ata9: soft resetting link
ata9.01: qc timeout (cmd 0xec)
ata9.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata9.01: revalidation failed (errno=-5)
ata9: link is slow to respond, please be patient (ready=0)
ata9: device not ready (errno=-16), forcing hardreset
ata9: soft resetting link
ata9.01: qc timeout (cmd 0xec)
ata9.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata9.01: revalidation failed (errno=-5)
ata9: link is slow to respond, please be patient (ready=0)
ata9: device not ready (errno=-16), forcing hardreset
ata9: soft resetting link
ata9.01: qc timeout (cmd 0xec)
ata9.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata9.01: revalidation failed (errno=-5)
ata9.01: disabled
ata9.00: failed to IDENTIFY (I/O error, err_mask=0x40)
ata9.00: revalidation failed (errno=-5)
ata9: link is slow to respond, please be patient (ready=0)
ata9: device not ready (errno=-16), forcing hardreset
ata9: soft resetting link
ata9.00: failed to IDENTIFY (device reports invalid type, err_mask=0x0)
ata9.00: revalidation failed (errno=-22)
ata9: soft resetting link
ata9.00: failed to IDENTIFY (device reports invalid type, err_mask=0x0)
ata9.00: revalidation failed (errno=-22)
ata9.00: disabled
ata9: EH complete
sd 8:0:0:0: [sdb] Asking for cache data failed
sd 8:0:0:0: [sdb] Assuming drive cache: write through
sd 8:0:0:0: [sdb] READ CAPACITY(16) failed
sd 8:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00
sd 8:0:0:0: [sdb] Sense not available.
sd 8:0:0:0: [sdb] READ CAPACITY failed
sd 8:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00
sd 8:0:0:0: [sdb] Sense not available.
sd 8:0:0:0: [sdb] Asking for cache data failed
sd 8:0:0:0: [sdb] Assuming drive cache: write through
sdb: detected capacity change from 250059350016 to 0
sd 8:0:0:0: [sdb] Attached SCSI disk
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
ldm_validate_partition_table(): Disk read failed.
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
unable to read partition table
sd 8:0:1:0: [sdc] Attached SCSI disk
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 1
Buffer I/O error on device sdc, logical block 2
Buffer I/O error on device sdc, logical block 3
sd 8:0:1:0: [sdc] Unhandled error code
sd 8:0:1:0: [sdc] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sdc, sector 0
...


Neither my HDDs or the cables are broken, i just tested this on Windows too...

Greetings

Jan