What does this mean (Messages log)?

Edward78

Edward78

Edward78

Soldato
Joined
19 Oct 2002
Posts
5,780
Nov 1 10:52:19 edward78-desktop kernel: [ 1647.000028] ata3: lost interrupt (Status 0x51)
Nov 1 10:52:24 edward78-desktop kernel: [ 1652.000042] ata3.00: qc timeout (cmd 0xa0)
Nov 1 10:52:24 edward78-desktop kernel: [ 1652.000056] sr 2:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
Nov 1 10:52:24 edward78-desktop kernel: [ 1652.000094] ata3: soft resetting link
Nov 1 10:52:24 edward78-desktop kernel: [ 1652.180255] ata3.00: configured for UDMA/33
Nov 1 10:52:29 edward78-desktop kernel: [ 1657.180030] ata3.00: qc timeout (cmd 0xa0)
Nov 1 10:52:29 edward78-desktop kernel: [ 1657.180036] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
Nov 1 10:52:29 edward78-desktop kernel: [ 1657.180056] ata3: soft resetting link
Nov 1 10:52:29 edward78-desktop kernel: [ 1657.360260] ata3.00: configured for UDMA/33
Nov 1 10:52:34 edward78-desktop kernel: [ 1662.360037] ata3.00: qc timeout (cmd 0xa0)
Nov 1 10:52:34 edward78-desktop kernel: [ 1662.360043] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
Nov 1 10:52:34 edward78-desktop kernel: [ 1662.360046] ata3.00: limiting speed to UDMA/33:PIO3
Nov 1 10:52:34 edward78-desktop kernel: [ 1662.360064] ata3: soft resetting link
Nov 1 10:52:34 edward78-desktop kernel: [ 1662.540247] ata3.00: configured for UDMA/33
Nov 1 10:52:39 edward78-desktop kernel: [ 1667.540028] ata3.00: qc timeout (cmd 0xa0)
Nov 1 10:52:39 edward78-desktop kernel: [ 1667.540034] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
Nov 1 10:52:39 edward78-desktop kernel: [ 1667.540036] ata3.00: disabled
Nov 1 10:52:39 edward78-desktop kernel: [ 1667.540062] ata3: soft resetting link
Nov 1 10:52:39 edward78-desktop kernel: [ 1667.696158] ata3: EH complete
 
tntcoder said:
Unless you have specific issues do not worry about it, the kernel spews out no end of audit/log information.

Those are related to the configuration of ATA devices, e.g hdds/cdroms.
Click to expand...

So my HDD is not going bad?? That was the first time it happened, I have never seen it before.
 
Essexraptor said:
Looks to be the kernel establishing a link with your drive during as already stated.

If your using the ever popular Ubuntu just use the disk utility to check the condition and status of your drives

System > Administration > Disk Utility

:)
Click to expand...

Hmm, it failed (read) the short self test.
 
dlmalloc said:
Hmmm, post lspci? Any details about why it failed the test?
Click to expand...

00:00.0 Host bridge: nVidia Corporation C55 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a2)
00:00.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.7 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:03.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:06.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:07.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
01:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800 GTS 512] (rev a2)

This time it completed ok on the short self test. :confused: Should I benchmark the drive??

Are you sure the info from the log file in the first post is harmless, cause I found that after a reboot when it froze & it just happened a few minutes ago again. Time was exactly when it froze & errors appeared. Only the mouse seems to freeze, is there a way to unfreeze it with a command in the terminal?
 
Last edited:
dlmalloc said:
Your system is reporting two sata controllers. Do you have two sata controllers? Have you tried a different sata controller?
Click to expand...

Nope haven't tried the other & when I first booted today, I got a checking disk for errors. When it finished I got the Ubuntu splash screen for prob. a minute in a half before I decided to hard reboot. So is my drive going bad or is it the main board controller?? Is there a for sure way to see with a app. of some kind??
 
memyselfandi said:
It is far more likely to be the disk than the mainboard controller, (the other option being a dodgy SATA cable).

As has been said above, backup any content and run the manufacturers diagnostic utility against the disk.

I'd have probably left it for quite a bit longer than 1.5mins before hard rebooting though.
Click to expand...

My drive model brings up nothing on the manufactures site.

JonJ678 said:
Semi-related:
Ubuntu told me that my hard drive is dying. It didn't put a foot wrong in the 3 days of read write testing that followed. Think ill be ignoring ubuntu's opinion for a while.
Click to expand...

So Ubuntu is not to be trusted..

Is there a utility that would spot a prob. for sure. A Disktest86+ (memtest 86+ for hdds would be awesome)
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom