February 10, 20179 yr Fix common problems found call traces last night. I am newly updated to 6.3.1. Diagnostics attached. Any ideas? hex-diagnostics-20170210-0757.zip
February 10, 20179 yr Community Expert I would suggest that you post up a typical trace call in new post. And describe if the trace call seems to be connected to anything that the server might have been doing at the time. You might also indicate if it is causing any issues with your server.
February 10, 20179 yr Community Expert Squid has been talking about making Traces and MCEs optional for FCP since often they don't cause problems.
February 10, 20179 yr Community Expert Newb to unraid, but how do I find the call trace? In your syslog. You already posted your diagnostics, so we have your sylog. What we don't know is what was happening at that time and if you are actually experiencing a problem when it happens.
February 10, 20179 yr Community Expert You're also having issue with your SSD, check/replace cables: Feb 8 19:16:08 Hex kernel: ata5.00: exception Emask 0x10 SAct 0xe00 SErr 0x400100 action 0x6 frozen Feb 8 19:16:08 Hex kernel: ata5.00: irq_stat 0x08000000, interface fatal error Feb 8 19:16:08 Hex kernel: ata5: SError: { UnrecovData Handshk } Feb 8 19:16:08 Hex kernel: ata5.00: failed command: WRITE FPDMA QUEUED Feb 8 19:16:08 Hex kernel: ata5.00: cmd 61/40:48:40:67:83/00:00:00:00:00/40 tag 9 ncq dma 32768 out Feb 8 19:16:08 Hex kernel: res 40/00:50:90:de:27/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Feb 8 19:16:08 Hex kernel: ata5.00: status: { DRDY } Feb 8 19:16:08 Hex kernel: ata5.00: failed command: WRITE FPDMA QUEUED Feb 8 19:16:08 Hex kernel: ata5.00: cmd 61/10:50:90:de:27/00:00:01:00:00/40 tag 10 ncq dma 8192 out Feb 8 19:16:08 Hex kernel: res 40/00:50:90:de:27/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Feb 8 19:16:08 Hex kernel: ata5.00: status: { DRDY } Feb 8 19:16:08 Hex kernel: ata5.00: failed command: WRITE FPDMA QUEUED Feb 8 19:16:08 Hex kernel: ata5.00: cmd 61/40:58:20:25:c1/00:00:00:00:00/40 tag 11 ncq dma 32768 out Feb 8 19:16:08 Hex kernel: res 40/00:50:90:de:27/00:00:01:00:00/40 Emask 0x10 (ATA bus error) Feb 8 19:16:08 Hex kernel: ata5.00: status: { DRDY } Feb 8 19:16:08 Hex kernel: ata5: hard resetting link Feb 8 19:16:08 Hex kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: supports DRM functions and may not be fully accessible Feb 8 19:16:08 Hex kernel: ata5.00: disabling queued TRIM support Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: supports DRM functions and may not be fully accessible Feb 8 19:16:08 Hex kernel: ata5.00: disabling queued TRIM support Feb 8 19:16:08 Hex kernel: ata5.00: configured for UDMA/133 Feb 8 19:16:08 Hex kernel: ata5: EH complete Feb 8 19:16:08 Hex kernel: ata5.00: exception Emask 0x10 SAct 0x20 SErr 0x400100 action 0x6 frozen Feb 8 19:16:08 Hex kernel: ata5.00: irq_stat 0x08000000, interface fatal error Feb 8 19:16:08 Hex kernel: ata5: SError: { UnrecovData Handshk } Feb 8 19:16:08 Hex kernel: ata5.00: failed command: WRITE FPDMA QUEUED Feb 8 19:16:08 Hex kernel: ata5.00: cmd 61/40:28:c0:25:c1/00:00:00:00:00/40 tag 5 ncq dma 32768 out Feb 8 19:16:08 Hex kernel: res 40/00:28:c0:25:c1/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 8 19:16:08 Hex kernel: ata5.00: status: { DRDY } Feb 8 19:16:08 Hex kernel: ata5: hard resetting link Feb 8 19:16:08 Hex kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: supports DRM functions and may not be fully accessible Feb 8 19:16:08 Hex kernel: ata5.00: disabling queued TRIM support Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Feb 8 19:16:08 Hex kernel: ata5.00: supports DRM functions and may not be fully accessible Feb 8 19:16:08 Hex kernel: ata5.00: disabling queued TRIM support Feb 8 19:16:08 Hex kernel: ata5.00: configured for UDMA/133 Feb 8 19:16:08 Hex kernel: ata5: EH complete Feb 8 19:16:08 Hex root: Ubooquity: started succesfully! Feb 8 19:16:08 Hex kernel: ata5.00: exception Emask 0x10 SAct 0x40 SErr 0x400100 action 0x6 frozen Feb 8 19:16:08 Hex kernel: ata5.00: irq_stat 0x08000000, interface fatal error Feb 8 19:16:08 Hex kernel: ata5: SError: { UnrecovData Handshk } Feb 8 19:16:08 Hex kernel: ata5.00: failed command: WRITE FPDMA QUEUED Feb 8 19:16:08 Hex kernel: ata5.00: cmd 61/60:30:40:6d:83/00:00:00:00:00/40 tag 6 ncq dma 49152 out Feb 8 19:16:08 Hex kernel: res 40/00:30:40:6d:83/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 8 19:16:08 Hex kernel: ata5.00: status: { DRDY } Feb 8 19:16:08 Hex kernel: ata5: hard resetting link Feb 8 19:16:09 Hex kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 8 19:16:09 Hex kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Feb 8 19:16:09 Hex kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Feb 8 19:16:09 Hex kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Feb 8 19:16:09 Hex kernel: ata5.00: supports DRM functions and may not be fully accessible Feb 8 19:16:09 Hex kernel: ata5.00: disabling queued TRIM support Feb 8 19:16:09 Hex kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Feb 8 19:16:09 Hex kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Feb 8 19:16:09 Hex kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Feb 8 19:16:09 Hex kernel: ata5.00: supports DRM functions and may not be fully accessible Feb 8 19:16:09 Hex kernel: ata5.00: disabling queued TRIM support Feb 8 19:16:09 Hex kernel: ata5.00: configured for UDMA/133 Feb 8 19:16:09 Hex kernel: ata5: EH complete Feb 8 19:16:09 Hex kernel: ata5: limiting SATA link speed to 3.0 Gbps Feb 8 19:16:09 Hex kernel: ata5.00: exception Emask 0x10 SAct 0x20000 SErr 0x400100 action 0x6 frozen Feb 8 19:16:09 Hex kernel: ata5.00: irq_stat 0x08000000, interface fatal error Feb 8 19:16:09 Hex kernel: ata5: SError: { UnrecovData Handshk } Feb 8 19:16:09 Hex kernel: ata5.00: failed command: WRITE FPDMA QUEUED Feb 8 19:16:09 Hex kernel: ata5.00: cmd 61/40:88:00:27:c1/00:00:00:00:00/40 tag 17 ncq dma 32768 out Feb 8 19:16:09 Hex kernel: res 40/00:88:00:27:c1/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Feb 8 19:16:09 Hex kernel: ata5.00: status: { DRDY } Feb 8 19:16:09 Hex kernel: ata5: hard resetting link
February 10, 20179 yr Community Expert Newb to unraid, but how do I find the call trace? You go into the diagnostic file. In the logs folder, you will find a file called syslog.txt. Open it in a text editor. Search for 'call trace'. Or, you could just scroll through it until you find it. (The only way you learn Linux is by exploring and doing.)
February 10, 20179 yr Author Hrm. The call trace appears to be related to rebooting a VM. The info about the SSD is interesting, too. I will move that drive to the SAS controller and see if that changes anything. I have had some odd issues where the system experiences long pauses while writing to the cache drive and I wonder if that has anything to do with this.
Archived
This topic is now archived and is closed to further replies.