SATA Error on Linux Kernel 2.6.18-5
 

Hi,

kernel: 2.6.18-5-686
mobo: ASUS P5LD2-VM


I've a problem with my sata on 500G segate drive:
after restarts it works nice but some times later this messages appears in:

localhost kernel: ATA: abnormal status 0x80 on port 0xC487
localhost last message repeated 2 times
localhost kernel: ata2: port is slow to respond, please be patient
localhost kernel: ata2: soft resetting port
localhost kernel: ATA: abnormal status 0x80 on port 0xC487
localhost last message repeated 5 times
localhost kernel: ata2.00: qc timeout (cmd 0xec)
localhost kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
localhost kernel: ata2: failed to recover some devices, retrying in 5 secs
localhost kernel: ata2: port is slow to respond, please be patient
localhost kernel: ata2: soft resetting port
localhost kernel: ATA: abnormal status 0x80 on port 0xC487
localhost last message repeated 5 times
localhost kernel: ata2.00: qc timeout (cmd 0xec)
localhost kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
localhost kernel: ata2: failed to recover some devices, retrying in 5 secs
localhost kernel: ata2: port is slow to respond, please be patient
localhost kernel: ata2: soft resetting port
localhost kernel: ATA: abnormal status 0x80 on port 0xC487
localhost last message repeated 5 times
localhost kernel: ata2.00: qc timeout (cmd 0xec)
localhost kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
localhost kernel: ata2.00: disabled
localhost kernel: ata2: EH complete
localhost kernel: sd 1:0:0:0: SCSI error: return code = 0x00040000
localhost kernel: end_request: I/O error, dev sda, sector 772074399
localhost kernel: lost page write due to I/O error on sda3

and then a lot of:
localhost kernel: end_request: I/O error, dev sda, sector 774170783
localhost kernel: end_request: I/O error, dev sda, sector 774170783

and then:
device hangs

what do you guys think ?



--
Kindly Regards
Davood Firoozian

looks like a controller prob to me, I'd update the controller and hdd firmwares first, and then try with a different controller

no, I don't think so. it seems like a kernel problem or something

kernel errors do not necessarily indicate kernel problems.