[opensuse] identifying device in dmesg output

older
Re: [opensuse] Canon CanoScan LiDe...

Istvan Gabor

23 Nov 2016 23 Nov '16

14:25

Hello: Occasionally I experience long, 40-50 secs hangup in my openSUSE 13.1 system. Following such hangup dmesg output contains the following lines at the end: [ 6537.719073] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 6537.719079] ata1.00: failed command: FLUSH CACHE EXT [ 6537.719085] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 6537.719096] ata1.00: status: { DRDY } [ 6537.719101] ata1: hard resetting link [ 6538.025944] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 6538.028155] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.028162] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030462] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.030467] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030558] ata1.00: configured for UDMA/133 [ 6538.030561] ata1.00: retrying FLUSH 0xea Emask 0x4 [ 6538.030599] ata1.00: device reported invalid CHS sector 0 [ 6538.030609] ata1: EH complete [ 6538.269793] show_signal_msg: 81 callbacks suppressed [ 6538.269798] plugin-containe[5320]: segfault at 0 ip 00007f8119a9a785 sp 00007f810e691a30 error 4 in libflashplayer.so[7f8119792000+1193000] Either one of the disks is bad or the motherboard has problem. How can I identify which disk is, or which SATA link/connector is the indicated ata1.00 device? What is/are the exact meaning of the above dmesg error messages? Thanks in advance, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Carlos E. R.

23 Nov 23 Nov

14:34

New subject: [opensuse] identifying device in dmesg output

On 2016-11-23 15:25, Istvan Gabor wrote:

...

Hello:

Occasionally I experience long, 40-50 secs hangup in my openSUSE 13.1 system. Following such hangup dmesg output contains the following lines at the end:

[ 6537.719073] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 6537.719079] ata1.00: failed command: FLUSH CACHE EXT [ 6537.719085] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 6537.719096] ata1.00: status: { DRDY } [ 6537.719101] ata1: hard resetting link [ 6538.025944] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 6538.028155] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.028162] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030462] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.030467] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030558] ata1.00: configured for UDMA/133 [ 6538.030561] ata1.00: retrying FLUSH 0xea Emask 0x4 [ 6538.030599] ata1.00: device reported invalid CHS sector 0 [ 6538.030609] ata1: EH complete [ 6538.269793] show_signal_msg: 81 callbacks suppressed

Either one of the disks is bad or the motherboard has problem.

How can I identify which disk is, or which SATA link/connector is the indicated ata1.00 device?

Maybe looking at the list at "/dev/disk/by-path/" Example: cer@Telcontar:~> l /dev/disk/by-path/ | grep ata-1.0 lrwxrwxrwx 1 root root 9 Nov 17 12:15 pci-0000:00:1f.2-ata-1.0 -> ../../sdb lrwxrwxrwx 1 root root 10 Nov 7 10:47 pci-0000:00:1f.2-ata-1.0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 11 Nov 7 10:47 pci-0000:00:1f.2-ata-1.0-part10 -> ../../sdb10

...

What is/are the exact meaning of the above dmesg error messages?

dunno. Run the smartctl long test on the disk.

...

[ 6538.269798] plugin-containe[5320]: segfault at 0 ip 00007f8119a9a785 sp 00007f810e691a30 error 4 in libflashplayer.so[7f8119792000+1193000]

You also had a flash crash in the browser. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

Istvan Gabor

15:31

New subject: [opensuse] identifying device in dmesg output

"Carlos E. R." írta:

...

On 2016-11-23 15:25, Istvan Gabor wrote:

...
Hello:

Occasionally I experience long, 40-50 secs hangup in my openSUSE 13.1 system. Following such hangup dmesg output contains the following lines at the end:

[ 6537.719073] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 6537.719079] ata1.00: failed command: FLUSH CACHE EXT [ 6537.719085] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 6537.719096] ata1.00: status: { DRDY } [ 6537.719101] ata1: hard resetting link [ 6538.025944] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 6538.028155] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.028162] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030462] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.030467] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030558] ata1.00: configured for UDMA/133 [ 6538.030561] ata1.00: retrying FLUSH 0xea Emask 0x4 [ 6538.030599] ata1.00: device reported invalid CHS sector 0 [ 6538.030609] ata1: EH complete [ 6538.269793] show_signal_msg: 81 callbacks suppressed

Either one of the disks is bad or the motherboard has problem.

How can I identify which disk is, or which SATA link/connector is the indicated ata1.00 device?

Maybe looking at the list at "/dev/disk/by-path/"

Example:

cer@Telcontar:~> l /dev/disk/by-path/ | grep ata-1.0 lrwxrwxrwx 1 root root 9 Nov 17 12:15 pci-0000:00:1f.2-ata-1.0 -> ../../sdb lrwxrwxrwx 1 root root 10 Nov 7 10:47 pci-0000:00:1f.2-ata-1.0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 11 Nov 7 10:47 pci-0000:00:1f.2-ata-1.0-part10 -> ../../sdb10

Thanks, but I have no any "ata" device in /dev/disk/by-path, only "scsi" in names. See:

...

ls -gG /dev/disk/by-path/ total 0 lrwxrwxrwx 1 9 Nov 23 11:04 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 10 Nov 23 11:04 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sda1 ... lrwxrwxrwx 1 9 Nov 23 11:04 pci-0000:00:1f.2-scsi-1:0:0:0 -> ../../sr0 lrwxrwxrwx 1 9 Nov 23 11:04 pci-0000:00:1f.2-scsi-2:0:0:0 -> ../../sdb lrwxrwxrwx 1 10 Nov 23 11:04 pci-0000:00:1f.2-scsi-2:0:0:0-part1 -> ../../sdb1 ... lrwxrwxrwx 1 9 Nov 23 11:04 pci-0000:00:1f.2-scsi-3:0:0:0 -> ../../sdc lrwxrwxrwx 1 10 Nov 23 11:04 pci-0000:00:1f.2-scsi-3:0:0:0-part1 -> ../../sdc1

How can I match these? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Knurpht - Gertjan Lettink

15:09

Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor:

...

ata1.00: device reported invalid CHS sector 0

A quick search indicates a drive failure / degrading condition. To find out which entry in /dev is meant by ata1 run ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/' -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Istvan Gabor

15:42

Knurpht - Gertjan Lettink írta:

...

Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor:

...
ata1.00: device reported invalid CHS sector 0

A quick search indicates a drive failure / degrading condition. To find out which entry in /dev is meant by ata1 run

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/'

Thanks, running this gives: ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/' ata1 => sda ata3 => sdb ata4 => sdc ls for these devices gives: ls -gG /sys/block/ lrwxrwxrwx 1 0 Nov 23 11:04 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 0 Nov 23 11:04 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb lrwxrwxrwx 1 0 Nov 23 11:04 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc Here there's no .00 in the names like in the dmesg message. What is then ata1.00 exactly? Why is .00 attached to the device name in dmesg? What does it mean? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Malcolm

15:49

New subject: [opensuse] Re: identifying device in dmesg output

On Wed 23 Nov 2016 04:42:15 PM CST, Istvan Gabor wrote:

...

Knurpht - Gertjan Lettink írta:

...
Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor:

...
ata1.00: device reported invalid CHS sector 0

A quick search indicates a drive failure / degrading condition. To find out which entry in /dev is meant by ata1 run

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/'

Thanks, running this gives:

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/' ata1 => sda ata3 => sdb ata4 => sdc

ls for these devices gives:

ls -gG /sys/block/ lrwxrwxrwx 1 0 Nov 23 11:04 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 0 Nov 23 11:04 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb lrwxrwxrwx 1 0 Nov 23 11:04 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc

Here there's no .00 in the names like in the dmesg message. What is then ata1.00 exactly? Why is .00 attached to the device name in dmesg? What does it mean?

Thanks,

Istvan

Hi The hwinfo --disk command should give you all the info, device files etc which should help clarify? -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 3 days 20:33, 3 users, load average: 0.56, 0.41, 0.25 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen

16:13

New subject: [opensuse] Re: identifying device in dmesg output

On November 23, 2016 7:49:57 AM PST, Malcolm wrote:

...

On Wed 23 Nov 2016 04:42:15 PM CST, Istvan Gabor wrote:

...
Knurpht - Gertjan Lettink írta:

...
Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor:

...
ata1.00: device reported invalid CHS sector 0

A quick search indicates a drive failure / degrading condition. To find out which entry in /dev is meant by ata1 run

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/'

Thanks, running this gives:

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/' ata1 => sda ata3 => sdb ata4 => sdc

ls for these devices gives:

ls -gG /sys/block/ lrwxrwxrwx 1 0 Nov 23 11:04 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 0 Nov 23 11:04 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb lrwxrwxrwx 1 0 Nov 23 11:04 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc

Here there's no .00 in the names like in the dmesg message. What is then ata1.00 exactly? Why is .00 attached to the device name in dmesg? What does it mean?

Thanks,

Istvan

Hi The hwinfo --disk command should give you all the info, device files etc which should help clarify?

More to the point he already knows which drive is ata1 and it's time to order a new drive. It's failing. Smartctl might show some info, but to what purpose? He needs to start moving that data now. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Malcolm

16:52

New subject: [opensuse] Re: identifying device in dmesg output

On Wed, 23 Nov 2016 08:13:42 -0800 John Andersen wrote:

...

On November 23, 2016 7:49:57 AM PST, Malcolm wrote:

...
On Wed 23 Nov 2016 04:42:15 PM CST, Istvan Gabor wrote:

...
Knurpht - Gertjan Lettink írta:

...
Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor:

...
ata1.00: device reported invalid CHS sector 0

A quick search indicates a drive failure / degrading condition. To find out which entry in /dev is meant by ata1 run

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/'

Thanks, running this gives:

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/' ata1 => sda ata3 => sdb ata4 => sdc

ls for these devices gives:

ls -gG /sys/block/ lrwxrwxrwx 1 0 Nov 23 11:04 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 0 Nov 23 11:04 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb lrwxrwxrwx 1 0 Nov 23 11:04 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc

Here there's no .00 in the names like in the dmesg message. What is then ata1.00 exactly? Why is .00 attached to the device name in dmesg? What does it mean?

Thanks,

Istvan

Hi The hwinfo --disk command should give you all the info, device files etc which should help clarify?

More to the point he already knows which drive is ata1 and it's time to order a new drive. It's failing.

Smartctl might show some info, but to what purpose?

He needs to start moving that data now.

Hi Could also be the cable or connection... check both connections, swap cables. -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 3 days 21:33, 3 users, load average: 0.36, 0.24, 0.19 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Greg Freemyer

24 Nov 24 Nov

05:10

New subject: [opensuse] Re: identifying device in dmesg output

On Wed, Nov 23, 2016 at 11:13 AM, John Andersen wrote:

...

On November 23, 2016 7:49:57 AM PST, Malcolm wrote:

...
On Wed 23 Nov 2016 04:42:15 PM CST, Istvan Gabor wrote:

...
Knurpht - Gertjan Lettink írta:

...
Op woensdag 23 november 2016 15:25:24 CET schreef Istvan Gabor:

...
ata1.00: device reported invalid CHS sector 0

A quick search indicates a drive failure / degrading condition. To find out which entry in /dev is meant by ata1 run

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/'

Thanks, running this gives:

ls -l /sys/block/sd* | sed 's/.*$sd.*$ -.*$ata.*$\/h.*/\2 => \1/' ata1 => sda ata3 => sdb ata4 => sdc

ls for these devices gives:

ls -gG /sys/block/ lrwxrwxrwx 1 0 Nov 23 11:04 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 0 Nov 23 11:04 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb lrwxrwxrwx 1 0 Nov 23 11:04 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc

Here there's no .00 in the names like in the dmesg message. What is then ata1.00 exactly? Why is .00 attached to the device name in dmesg? What does it mean?

Thanks,

Istvan

Hi The hwinfo --disk command should give you all the info, device files etc which should help clarify?

More to the point he already knows which drive is ata1 and it's time to order a new drive. It's failing.

Smartctl might show some info, but to what purpose?

He needs to start moving that data now.

If smartctl doesn't show historical drive errors, it probably isn't the drive. I've had lots of sata cables fail over the years. Unreliable communications causes strange error reports. Drive's tend to have total failure or bad sectors. If this is a bad drive, I'd say it's a rare failure mode. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

23 Nov 23 Nov

16:43

New subject: [opensuse] identifying device in dmesg output

23.11.2016 18:42, Istvan Gabor пишет:

...

Here there's no .00 in the names like in the dmesg message. What is then ata1.00 exactly?

Device with address 00 on SATA port with running number 1.

...

Why is .00 attached to the device name in dmesg? What does it mean?

While normally SATA is point to point and there is exactly one device on each port (connector), there exist SATA PMP (Port Multiplier - similar to USB hubs) that allows connecting more than one device to SATA port. So number after digit isalmost always 00 except when you have PMP connected. Then it designates specific device connected to PMP. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

David Haller

15:37

Hello, On Wed, 23 Nov 2016, Istvan Gabor wrote: [..]

...

[ 6537.719073] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [..]> How can I identify which disk is, or which SATA link/connector is the indicated ata1.00 device?

==== 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 ==== HTH, -dnh -- A tangled cable is a happy cable. -- R. B. West -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carl Hartung

15:49

On Wed, 23 Nov 2016 15:25:24 +0100 (CET) Istvan Gabor wrote:

...

Hello:

Occasionally I experience long, 40-50 secs hangup in my openSUSE 13.1 system. Following such hangup dmesg output contains the following lines at the end:

[ 6537.719073] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 6537.719079] ata1.00: failed command: FLUSH CACHE EXT [ 6537.719085] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 6537.719096] ata1.00: status: { DRDY } [ 6537.719101] ata1: hard resetting link [ 6538.025944] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 6538.028155] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.028162] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030462] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130517/psargs-359) [ 6538.030467] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node ffff8801189ac790), AE_NOT_FOUND (20130517/psparse-536) [ 6538.030558] ata1.00: configured for UDMA/133 [ 6538.030561] ata1.00: retrying FLUSH 0xea Emask 0x4 [ 6538.030599] ata1.00: device reported invalid CHS sector 0 [ 6538.030609] ata1: EH complete [ 6538.269793] show_signal_msg: 81 callbacks suppressed [ 6538.269798] plugin-containe[5320]: segfault at 0 ip 00007f8119a9a785 sp 00007f810e691a30 error 4 in libflashplayer.so[7f8119792000+1193000]

Either one of the disks is bad or the motherboard has problem.

How can I identify which disk is, or which SATA link/connector is the indicated ata1.00 device?

What is/are the exact meaning of the above dmesg error messages?

Thanks in advance,

Istvan

Hi Istvan, You can invoke dmesg and pipe it to grep to see just the lines containing 'ata1'. Here's one line from my output identifying the device: carlh:~> dmesg | grep ata1 8< - - - - - trimmed - - - - ->8 ***** [ 2.215271] ata1.00: ATA-9: Samsung SSD 840 PRO Series, DXM06B0Q, max UDMA/133 ***** 8< - - - - - trimmed - - - - ->8 This line from your output is concerning:

...

[ 6538.030599] ata1.00: device reported invalid CHS sector 0

Did you confirm when you installed that your BIOS was set to use LBA (Logical Block Addressing) or CHS (Cylinder - Head - Sector) addressing (possibly with LBA > CHS translation?) You should check the manufacturer's setup and BIOS instructions for your motherboard - both in the user guide and on their website and confirm which method this hard drive was originally configured to use. Also see: https://en.wikipedia.org/wiki/Logical_block_addressing and https://en.wikipedia.org/wiki/Cylinder-head-sector in addition to querying smartctl for the status of the drive's health. hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

2717

Age (days ago)

2718

Last active (days ago)

List overview

Download

11 comments

9 participants

participants (9)

Andrei Borzenkov
Carl Hartung
Carlos E. R.
David Haller
Greg Freemyer
Istvan Gabor
John Andersen
Knurpht - Gertjan Lettink
Malcolm