Gragorg Posted October 6, 2022 Share Posted October 6, 2022 A month ago during my parity check my server shut down. Today it did the same thing although not during my monthly parity check. I turned on syslog server to see if I can catch anything. Any input on the best way to troubleshoot this would be appreciated? tower-diagnostics-20221006-0047.zip Quote Link to comment
Solution JorgeB Posted October 6, 2022 Solution Share Posted October 6, 2022 Start by checking cooler and temps, that looks like an overheating CPU. 1 Quote Link to comment
Gragorg Posted October 6, 2022 Author Share Posted October 6, 2022 I popped the side off and it looks likes its been awhile since I dusted. I guess I will do it after Parity check and give it a try. Quote Link to comment
Gragorg Posted November 1, 2022 Author Share Posted November 1, 2022 On 10/6/2022 at 3:49 AM, JorgeB said: Start by checking cooler and temps, that looks like an overheating CPU. This seems to have been the issue there was a lot of dust built up on cooler. However I was watching parity check today and noticed some ata errors in the log. Should I be concerned about these? tower-diagnostics-20221101-1122.zip Quote Link to comment
JorgeB Posted November 1, 2022 Share Posted November 1, 2022 Nothing major for now but start by replacing the cables for that disk. Quote Link to comment
Gragorg Posted November 1, 2022 Author Share Posted November 1, 2022 50 minutes ago, JorgeB said: Nothing major for now but start by replacing the cables for that disk. Sorry to bother you again but where does it specify the disk number? Nov 1 00:09:29 Tower kernel: ata2.00: exception Emask 0x52 SAct 0x0 SErr 0x4890c00 action 0xe frozen Nov 1 00:09:29 Tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed Nov 1 00:09:29 Tower kernel: ata2: SError: { Proto HostInt PHYRdyChg 10B8B LinkSeq DevExch } Nov 1 00:09:29 Tower kernel: ata2.00: failed command: READ DMA EXT Nov 1 00:09:29 Tower kernel: ata2.00: cmd 25/00:c0:f0:f6:d7/00:04:0a:00:00/e0 tag 10 dma 622592 in Nov 1 00:09:29 Tower kernel: res 50/00:00:ef:f6:d7/00:00:0a:00:00/ea Emask 0x52 (ATA bus error) Nov 1 00:09:29 Tower kernel: ata2.00: status: { DRDY } Nov 1 00:09:29 Tower kernel: ata2: hard resetting link Nov 1 00:09:35 Tower kernel: ata2: link is slow to respond, please be patient (ready=0) Nov 1 00:09:36 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 1 00:09:36 Tower kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out Nov 1 00:09:36 Tower kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out Nov 1 00:09:36 Tower kernel: ata2.00: NCQ Send/Recv Log not supported Nov 1 00:09:36 Tower kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out Nov 1 00:09:36 Tower kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out Nov 1 00:09:36 Tower kernel: ata2.00: NCQ Send/Recv Log not supported Nov 1 00:09:36 Tower kernel: ata2.00: configured for UDMA/133 Nov 1 00:09:36 Tower kernel: ata2: EH complete Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.