09.01.2017 17:56, Roger Oberholtzer пишет:
On Mon, Jan 9, 2017 at 2:55 PM, Carlos E. R. <robin.listas@telefonica.net> 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...
Do you have ata10 at all? find /sys/devices/ -name ata\* -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org