Limiting SATA link speed to 1.5 Gbps (Includes Log)

[Hatchtek]

I am getting these errors and just trying to see if someone could help me out.

Apr 26 09:51:30 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
Apr 26 09:51:30 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
Apr 26 09:51:30 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
Apr 26 09:51:30 Tower kernel: ata1.00: configured for UDMA/133
Apr 26 09:51:30 Tower kernel: ata1: EH complete
Apr 26 09:51:30 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps
Apr 26 09:51:30 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Apr 26 09:51:30 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Apr 26 09:51:30 Tower kernel: ata1: SError: { UnrecovData 10B8B BadCRC }
Apr 26 09:51:30 Tower kernel: ata1.00: failed command: READ DMA EXT
Apr 26 09:51:30 Tower kernel: ata1.00: cmd 25/00:00:90:d5:5a/00:04:40:00:00/e0 tag 24 dma 524288 in
Apr 26 09:51:30 Tower kernel: res 50/00:00:8f:d5:5a/00:00:40:00:00/40 Emask 0x10 (ATA bus error)
Apr 26 09:51:30 Tower kernel: ata1.00: status: { DRDY }
Apr 26 09:51:30 Tower kernel: ata1: hard resetting link
Apr 26 09:51:30 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 26 09:51:30 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
Apr 26 09:51:30 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
Apr 26 09:51:30 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
Apr 26 09:51:30 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
Apr 26 09:51:30 Tower kernel: ata1.00: configured for UDMA/133
Apr 26 09:51:30 Tower kernel: ata1: EH complete
Apr 26 09:59:49 Tower kernel: TCP: request_sock_TCP: Possible SYN flooding on port 8080. Sending cookies. Check SNMP counters.
Apr 26 10:38:35 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen
Apr 26 10:38:35 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Apr 26 10:38:35 Tower kernel: ata1: SError: { UnrecovData Handshk }
Apr 26 10:38:35 Tower kernel: ata1.00: failed command: WRITE DMA EXT
Apr 26 10:38:35 Tower kernel: ata1.00: cmd 35/00:40:f0:81:ca/00:05:00:03:00/e0 tag 26 dma 688128 out
Apr 26 10:38:35 Tower kernel: res 50/00:00:47:8d:f1/00:00:44:00:00/40 Emask 0x10 (ATA bus error)
Apr 26 10:38:35 Tower kernel: ata1.00: status: { DRDY }
Apr 26 10:38:35 Tower kernel: ata1: hard resetting link
Apr 26 10:38:35 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 26 10:38:35 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
Apr 26 10:38:35 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
Apr 26 10:38:35 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20170728/psargs-364)
Apr 26 10:38:35 Tower kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT0._GTF, AE_NOT_FOUND (20170728/psparse-550)
Apr 26 10:38:35 Tower kernel: ata1.00: configured for UDMA/133
Apr 26 10:38:35 Tower kernel: ata1: EH complete

 

[trurl]

Tools - Diagnostics, post complete zip

[John_M]

The SATA link is being reset repeatedly. In the absence of further information it's likely to be caused by the SATA cable; or it could be the controller port,  backplane or disk caddy, the hard disk itself or its power connection.

[Hatchtek]

Here are the full logs

tower-diagnostics-20180426-2003.zip

[JorgeB]

Replace the SATA cable for your parity disk, also make sure notifications are enable, you would be getting CRC error notifications.

[Hatchtek]

hmm well, the cable is built into the bay. So that sucks. Thank you for the help :-)

[trurl]

4 hours ago, Hatchtek said:

hmm well, the cable is built into the bay. So that sucks. Thank you for the help :-)

 

So how are you going to proceed? You need to fix problems as soon as you can. You don't want to let a problem go until you have even more problems. Multiple problems are the way to lose data.

 

Be sure to setup Notifications if you haven't since that will tell you when you have something that needs fixing.