cambriancatalyst Posted March 3, 2021 Share Posted March 3, 2021 (edited) Hello all, my server has been crashing pretty consistently (every 10-15 minutes or so after reboot) a couple hours after upgrading from 6.9.0-beta35 to 6.9. I am receiving the following error in Fix Common Problems: "Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged" I have attached my diagnostics. Can anyone provide assistance? Thank you! tower-diagnostics-20210303-0330.zip Edited March 3, 2021 by cambriancatalyst corrected title and body Quote Link to comment
cambriancatalyst Posted March 3, 2021 Author Share Posted March 3, 2021 Just to follow-up. I reverted back to 6.9.0beta35 and the system has been stable with no crashes. I'd really appreciate any feedback regarding the above diagnostic report. I initially thought this was a hardware issue on my end due to the message but given that it seems to be stable on 6.9.0beta35 I'm starting to think otherwise. Any help is appreciated. Thanks. Quote Link to comment
cambriancatalyst Posted March 3, 2021 Author Share Posted March 3, 2021 Thank you trurl! I applied the changes mentioned in the linked thread and have had no crashes since then. I appreciate your help! Quote Link to comment
cambriancatalyst Posted March 4, 2021 Author Share Posted March 4, 2021 It seems I spoke too soon. The system was doing great after setting power supply idle control to typical current idle the rig but after a couple of hours the system entered the same type of sleep pattern. I had setup syslog so I was able to capture the system entering an s3 sleep state. Please see below for logs. Does anyone know how I can prevent this from occurring? Quote Mar 3 21:46:52 Tower kernel: bond0: (slave eth0): making interface the new active one Mar 3 21:46:52 Tower kernel: device eth0 entered promiscuous mode Mar 3 21:46:52 Tower kernel: bond0: active interface up! Mar 3 21:46:52 Tower kernel: br0: port 1(bond0) entered blocking state Mar 3 21:46:52 Tower kernel: br0: port 1(bond0) entered forwarding state Mar 3 21:46:52 Tower kernel: ata2: softreset failed (device not ready) Mar 3 21:46:52 Tower kernel: ata3: softreset failed (device not ready) Mar 3 21:46:52 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 3 21:46:52 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible Mar 3 21:46:52 Tower kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 3 21:46:52 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 3 21:46:52 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible Mar 3 21:46:52 Tower kernel: ata3.00: configured for UDMA/133 Mar 3 21:46:52 Tower kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 3 21:46:52 Tower kernel: ata2.00: configured for UDMA/133 Mar 3 21:46:52 Tower kernel: OOM killer enabled. Mar 3 21:46:52 Tower kernel: Restarting tasks ... done. Mar 3 21:46:52 Tower kernel: PM: suspend exit Mar 3 21:50:02 Tower s3_sleep: ---------------------------------------------- Mar 3 21:50:02 Tower s3_sleep: command-args=-C 1 -h 15 -h 16 -h 17 -h 18 -h 19 -h 20 -a -m 30 -n -e eth0 -N 62500 -D 0 Mar 3 21:50:02 Tower s3_sleep: action mode=sleep Mar 3 21:50:02 Tower s3_sleep: check disks status=yes Mar 3 21:50:02 Tower s3_sleep: check network activity=yes Mar 3 21:50:02 Tower s3_sleep: check active devices=no Mar 3 21:50:02 Tower s3_sleep: check local login=no Mar 3 21:50:02 Tower s3_sleep: check remote login=no Mar 3 21:50:02 Tower s3_sleep: version=3.0.7 Mar 3 21:50:02 Tower s3_sleep: ---------------------------------------------- Mar 3 21:50:02 Tower s3_sleep: included disks= Mar 3 21:50:02 Tower s3_sleep: excluded disks=sda sdb sdc sdd Mar 3 21:50:02 Tower s3_sleep: ---------------------------------------------- Mar 3 21:50:02 Tower s3_sleep: s3_sleep process ID 13239 started, To terminate it, type: s3_sleep -q Quote Link to comment
JorgeB Posted March 4, 2021 Share Posted March 4, 2021 Remove the Dynamix sleep plugin. Quote Link to comment
cambriancatalyst Posted March 5, 2021 Author Share Posted March 5, 2021 This did the trick. Thank you both again! 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.