ATA error messages reported in syslog

Bug #267306 reported by dmoyne
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

My syslog file keeps filling with this type of messages related to ATA :

07.09.2008 02:58:09 azun kernel [ 1867.188568] ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
07.09.2008 02:58:09 azun kernel [ 1867.188574] ata2.01: cmd a0/00:00:00:00:01/00:00:00:00:00/b0 tag 0 pio 255 in
07.09.2008 02:58:09 azun kernel [ 1867.188575] cdb 5a 00 3f 00 00 00 00 00 ff 00 00 00 00 00 00 00
07.09.2008 02:58:09 azun kernel [ 1867.188576] res 51/50:03:00:00:01/00:00:00:00:00/b0 Emask 0x1 (device error)
07.09.2008 02:58:09 azun kernel [ 1867.188579] ata2.01: status: { DRDY ERR }
07.09.2008 02:58:09 azun kernel [ 1867.188587] sd 2:0:1:0: [sda] Test WP failed, assume Write Enabled
07.09.2008 02:58:09 azun kernel [ 1867.189192] ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
07.09.2008 02:58:09 azun kernel [ 1867.189198] ata2.01: cmd a0/00:00:00:08:00/00:00:00:00:00/b0 tag 0 pio 8 in
07.09.2008 02:58:09 azun kernel [ 1867.189199] cdb 5a 00 08 00 00 00 00 00 08 00 00 00 00 00 00 00
07.09.2008 02:58:09 azun kernel [ 1867.189200] res 51/50:03:00:08:00/00:00:00:00:00/b0 Emask 0x1 (device error)
07.09.2008 02:58:09 azun kernel [ 1867.189203] ata2.01: status: { DRDY ERR }
07.09.2008 02:58:09 azun kernel [ 1867.189211] sd 2:0:1:0: [sda] Asking for cache data failed
07.09.2008 02:58:09 azun kernel [ 1867.189213] sd 2:0:1:0: [sda] Assuming drive cache: write through
07.09.2008 02:58:09 azun kernel [ 1867.189989] ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
07.09.2008 02:58:09 azun kernel [ 1867.189996] ata2.01: cmd a0/00:00:00:00:00/00:00:00:00:00/b0 tag 0
07.09.2008 02:58:09 azun kernel [ 1867.189997] cdb 1e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
07.09.2008 02:58:09 azun kernel [ 1867.189998] res 51/50:03:00:00:00/00:00:00:00:00/b0 Emask 0x1 (device error)
07.09.2008 02:58:09 azun kernel [ 1867.190001] ata2.01: status: { DRDY ERR }
07.09.2008 02:58:09 azun kernel [ 1867.190010] sd 2:0:1:0: ioctl_internal_command return code = 8000002
07.09.2008 02:58:09 azun kernel [ 1867.190012] : Sense Key : Aborted Command [current] [descriptor]
07.09.2008 02:58:09 azun kernel [ 1867.190014] : Add. Sense: Recorded entity not found

This might be the same bug as bug #129709 but here I have a Hardy 64 bit system with kernel 2.6.24.19-generic

I have 2 ATA Hd's but apparently the problem is only abot the one "sda"

Is the syslog file going to clean itself or must I clean it myself

Any fix ?

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

Revision history for this message
dmoyne (daniel-moyne) wrote :

Here are some more information as demanded :
(1)
$ uname -a
Linux azun 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux

(2) dmseg.log attached

Revision history for this message
dmoyne (daniel-moyne) wrote :

Here are some more information as demanded :
(3) lspci-vvnn.log attached

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks but we need the dmesg output just after a fresh boot in order to capture kernel boot messages. This will help us to track down your problem.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi dmoyne,

Would you also be willing to test the latest Alpha5 release for the upcoming Intrepid Ibex 8.10? It contains a newer 2.6.27 based kernel and I'd like to know if this will be an issue for Intrepid. You should be able to test using a LiveCD. For more information regarding Alpha5 please refer to http://www.ubuntu.com/testing . Thanks.

Revision history for this message
dmoyne (daniel-moyne) wrote :

Log after boot attached
Regarding the test it is second priority compared to the need to change my SATA HD if a harware problem can only explain the error messages reported ; I will do once this issue is resolved or at least diagnosed

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks. What is the device on ata2.01 (ata2.01: ATAPI: IOMEGA) ? It seems to be the culprit.

Revision history for this message
dmoyne (daniel-moyne) wrote :

Bingo : it is actually my drive IOMEGA IDE that I have recovered on an old computer and installed in an empty slot in my computer that is the problem ; I will remove it as I do not use it ;
thanks ; conclusion : hardware problem on IOMEGA IDE to be dumped.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for the update. I'm closing this report due to your last comment regarding this being caused by a faulty hardware.

Don't hesitate to submit any new bug.

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.