On Mon, Jan 9, 2017 at 11:56 AM, Thomas Wagner wrote:

On 2017-01-09 11:24, Roger Oberholtzer wrote:

...

2017-01-09T11:12:33.002408+01:00 acme kernel: [502427.071523] ata10: SATA link down (SStatus 0 SControl 310) 2017-01-09T11:12:33.002460+01:00 acme kernel: [502427.071544] ata10: EH complete 2017-01-09T11:12:33.029456+01:00 acme kernel: [502427.098802] ata10: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen 2017-01-09T11:12:33.029491+01:00 acme kernel: [502427.098811] ata10: irq_stat 0x80000040, connection status changed 2017-01-09T11:12:33.029495+01:00 acme kernel: [502427.098819] ata10: SError: { CommWake DevExch } 2017-01-09T11:12:33.029499+01:00 acme kernel: [502427.098833] ata10: limiting SATA link speed to 1.5 Gbps 2017-01-09T11:12:33.029502+01:00 acme kernel: [502427.098847] ata10: hard resetting link

Had this also a few times in the last 5 years. The reason was a bunch of cheap SATA-cables I used.

I can say that I don't like the cables in the system. I have run smartctl -a on all disks and all seem happy. All pass, and no errors are reported. Maybe it is time to do some cable replacement. Cables. The bane of my existence. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Monday 2017-01-09 11:56, Thomas Wagner wrote:

On 2017-01-09 11:24, Roger Oberholtzer wrote:

...

2017-01-09T11:12:33.002408+01:00 acme kernel: [502427.071523] ata10: SATA link down (SStatus 0 SControl 310) 2017-01-09T11:12:33.002460+01:00 acme kernel: [502427.071544] ata10: EH complete 2017-01-09T11:12:33.029456+01:00 acme kernel: [502427.098802] ata10: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen 2017-01-09T11:12:33.029491+01:00 acme kernel: [502427.098811] ata10: irq_stat 0x80000040, connection status changed 2017-01-09T11:12:33.029495+01:00 acme kernel: [502427.098819] ata10: SError: { CommWake DevExch } 2017-01-09T11:12:33.029499+01:00 acme kernel: [502427.098833] ata10: limiting SATA link speed to 1.5 Gbps 2017-01-09T11:12:33.029502+01:00 acme kernel: [502427.098847] ata10: hard resetting link Had this also a few times in the last 5 years. The reason was a bunch of cheap SATA-cables I used.

same here.. or bad connection (no well working snap-in). Trouble was over after using the most expensive shielded SATA-cables.. before smartctl also reported loads of UDMA-CRC-Errors. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Monday 2017-01-09 16:01, Dave Plater wrote:

Date: Mon, 9 Jan 2017 16:01:36 From: Dave Plater To: opensuse@opensuse.org Subject: Re: [opensuse] worrisome log messages

On 09/01/2017 12:56, Thomas Wagner wrote:

...

On 2017-01-09 11:24, Roger Oberholtzer wrote:

...

2017-01-09T11:12:33.002408+01:00 acme kernel: [502427.071523] ata10: SATA link down (SStatus 0 SControl 310) 2017-01-09T11:12:33.002460+01:00 acme kernel: [502427.071544] ata10: EH complete 2017-01-09T11:12:33.029456+01:00 acme kernel: [502427.098802] ata10: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen 2017-01-09T11:12:33.029491+01:00 acme kernel: [502427.098811] ata10: irq_stat 0x80000040, connection status changed 2017-01-09T11:12:33.029495+01:00 acme kernel: [502427.098819] ata10: SError: { CommWake DevExch } 2017-01-09T11:12:33.029499+01:00 acme kernel: [502427.098833] ata10: limiting SATA link speed to 1.5 Gbps 2017-01-09T11:12:33.029502+01:00 acme kernel: [502427.098847] ata10: hard resetting link Had this also a few times in the last 5 years. The reason was a bunch of cheap SATA-cables I used.

I had this, first from one disk that developed bad sectors then another, they were secondary disks so I removed them. Then when I moved my computer my main disk failed and I discovered that the 5Volt wire was faulty, repaired it and it seems that was the problem all along. Both of the other disks are fine. So don't discount your power supply. Dave P

This is correct.. I had a bunch of disks failing with error messages like above. After powering down to check cabling, the power supply failed completely.. After replacing it, i looked into monitored voltages in the past (recorded by cacti), and voltages have dropped down over time dramatically. From then on nagios also watches these voltages. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Mon, Jan 9, 2017 at 2:55 PM, Carlos E. R. wrote:

On 2017-01-09 11:24, Roger Oberholtzer wrote:

...

I have started seeing this sequence of log messages in my system log. They occur every 2 minutes:

2017-01-09T11:12:33.002408+01:00 acme kernel: [502427.071523] ata10: SATA link down (SStatus 0 SControl 310) 2017-01-09T11:12:33.002460+01:00 acme kernel: [502427.071544] ata10: EH complete 2017-01-09T11:12:33.029456+01:00 acme kernel: [502427.098802] ata10: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen 2017-01-09T11:12:33.029491+01:00 acme kernel: [502427.098811] ata10: irq_stat 0x80000040, connection status changed 2017-01-09T11:12:33.029495+01:00 acme kernel: [502427.098819] ata10: SError: { CommWake DevExch } 2017-01-09T11:12:33.029499+01:00 acme kernel: [502427.098833] ata10: limiting SATA link speed to 1.5 Gbps 2017-01-09T11:12:33.029502+01:00 acme kernel: [502427.098847] ata10: hard resetting link

This cannot be good ;) How can I find out which disk is the cause of whatever this is?

Check this thread "identifying device in dmesg output" of last November.

Suggestions:

ls -l /sys/block/sd* | sed 's/.*\(sd.*\) -.*\(ata.*\)\/h.*/\2 => \1/' (Knurpht - Gertjan Lettink)

I get this: ata1 => sda ata2 => sdb ata3 => sdc ata4 => sdd ata5 => sde ata9 => sdf no ata10. How odd. Time to see what's really connected in the box... -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2017-01-09 18:21, Andrei Borzenkov wrote:

09.01.2017 17:56, Roger Oberholtzer пишет:

...

On Mon, Jan 9, 2017 at 2:55 PM, Carlos E. R. <> wrote:

...

...

Check this thread "identifying device in dmesg output" of last November.

Suggestions:

ls -l /sys/block/sd* | sed 's/.*\(sd.*\) -.*\(ata.*\)\/h.*/\2 => \1/' (Knurpht - Gertjan Lettink)

I get this:

ata1 => sda ata2 => sdb ata3 => sdc ata4 => sdd ata5 => sde ata9 => sdf

no ata10. How odd. Time to see what's really connected in the box...

Do you have ata10 at all?

find /sys/devices/ -name ata\*

We could be chasing ghosts, you know ;-) It could be flashdisk which had the problem, and now it is not connected. It happened to me. Or so I thought. :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

On 2017-01-10 10:11, Roger Oberholtzer wrote:

On Mon, Jan 9, 2017 at 6:21 PM, Andrei Borzenkov wrote:

...

...

I get this:

ata1 => sda ata2 => sdb ata3 => sdc ata4 => sdd ata5 => sde ata9 => sdf

no ata10. How odd. Time to see what's really connected in the box...

Do you have ata10 at all?

find /sys/devices/ -name ata\*

I have 1 thru 12 listed there.

The command only lists those in actual use at the moment. This is my current result: Telcontar:~ # ls -l /sys/block/sd* | sed 's/.*\(sd.*\) -.*\(ata.*\)\/h.*/\2 => \1/' ata8 => sda ata9 => sdb ata9 => sdc ata10 => sdd ata10 => sde Telcontar:~ # 1..7 are missing. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)