![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
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) script (David Haller): ==== ataid_to_drive.sh ==== #!/bin/bash oIFS="$IFS" IFS=$'\n' PATH="/sbin:/usr/sbin:$PATH" CTRLS=( $( lspci | grep 'ATA\|IDE') ) IFS="$oIFS" for arg; do if test -z "${arg/ata*}"; then arg="${arg/ata}" fi if test -z "${arg/*.*}"; then ata="${arg%.*}" subid="$(printf "%i" "${arg##*.}")"; else ata="$arg" fi echo "ata${ata}${subid/*/.$(printf "%02i" $subid)} is:" for ctrl in ${CTRLS[@]%% *}; do idpath="/sys/bus/pci/devices/*${ctrl}/*/*/*/unique_id" grep "^${ata}$" $idpath 2>/dev/null host=$(grep "^${ata}$" $idpath 2>/dev/null | \ sed 's@.*/host\([0-9A-Fa-f]\+\)/.*@\1@') if test -n "$host"; then dmesg | grep "\] s[dr] $host:0:$subid.*Attached" fi done done ==== -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)