Mageia forum

Linux 3.14.24-desktop-1.mga4 #1 SMP Sat Nov 15 23:54:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Log files keep filling up with an error related to ata6:

Code: Select all

grep "ata6" /var/log/dmesg
[    0.396006] ata6: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a380 irq 41
[    2.697562] ata6: SATA link down (SStatus 1 SControl 300)
[    2.704480] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen
[    2.704862] ata6: irq_stat 0x00000040, connection status changed
[    2.705166] ata6: SError: { DevExch }
[    2.705354] ata6: hard resetting link
[    5.273619] ata6: SATA link down (SStatus 1 SControl 300)
[    5.273626] ata6: EH complete
[    5.281044] ata6: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen
[    5.281046] ata6: irq_stat 0x00000040, connection status changed
[    5.281047] ata6: SError: { DevExch }
[    5.281050] ata6: limiting SATA link speed to 1.5 Gbps
[    5.281052] ata6: hard resetting link

Etcetera.

Obviously, ata6 is having some sort of issue. Unfortunately I don't have a clue as to what exactly ata6 is. I do find this in my mcc hardware applet:

Code: Select all

Identification
Vendor: ‎Intel Corporation

Description: ‎8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]

Media class: ‎SATA controller

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎0

PCI device #: ‎31

PCI function #: ‎2

PCI revision: ‎0x05

Vendor ID: ‎0x8086

Device ID: ‎0x8c02

Sub vendor ID: ‎0x1043

Sub device ID: ‎0x8534

Misc
Module: ‎unknown

So, I need to either fix this and put a stop to the log files filling up my /var directory, or squelch these errors somehow to prevent the log files from filling up my /var directory. I'd perfer the first, but since everything seems to be working okay, I'd settle for the second option.

Any ideas?


Mark

looks like one of your disks sata cable is having trouble.

so now that ive said one of your disks, does ata6 mean anything.

I would hazard a guess, that you either have one of the disks on esata,
and as esata is such a physical challenged connector, that the lead is dodgy or too long.

alternatively one of your disks has an exceptionally long sata lead, or one that needs replacing.

it could of course be the disk itself, i get this occasionally because cheap esata cases come with
poor psu's or poor cheaply implemented electronics.

any of the above is a possible cause.
the significant clue is that the sata bus is trying to slow down the speed of the connection to make it more reliable,

from a users perspective, everything probably does look ok.
however there exists a risk, that data corruption could render the data on this disk corrupt.

regards peter

Okay, so bad cable, bad connection, or bad hard drive. I will break into this box when it becomes convenient. Or possibly when the box *requires* that I absolutely, positively have to break into it and see what I can do.

I appreciate the input. All help is welcome.

Thanks!

Mark

Edit: after I posted the origianl message above, I found this:

http://iwtf.net/2011/05/19/western-digi ... der-linux/

Do you think this has any relevance in my case?

Just asking.

Mark

some of those errors do match up,
pull the harddisk (if its not the OS drive) and see if they stop.
unmount any extra partitions you might have added to access that disk first.
thats the simplest test

regards peter

ata6 is referring to the SATA port number I believe on your motherboard.

I could be wrong though