July 3, 20242 yr Built a new server a while back and noticed it seemed to lock up every few weeks, as part of building it I upgraded to the newest 6.12.10 version. Now it locks up within hours of starting. Have memscanned it and it all comes up clean. I can get to the GUI but after some number of hours the GUI locks up and the server is inaccessible. I have attached diagnostics and syslog. Any help would be appreciated. The diagnostics was started in clean gui mode after a lock up. If I need to start it up in regular mode let me know, I just wanted to see if it kept freezing up if it was in clean mode. langford-diagnostics-20240703-0746.zip syslog
July 3, 20242 yr Community Expert Nothing relevant that I can see, what is the timecode for the last crash?
July 3, 20242 yr Author It froze last night, so I assume its the last syslog message received at 2:54:24
July 3, 20242 yr Community Expert In that case there's really nothing relevant logged, this can be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
July 4, 20242 yr Author It still crashes doing Parity checks only with the Array started in safe mode. Not sure where to start looking into this, since all the hardware is mostly new. Update: Actually using IPMI this time, it doesn't appear to be fully locked up. Interesting.. I can switch between pages but the dashboard is toast for sure. syslog Edited July 4, 20242 yr by theDrell
July 4, 20242 yr Community Expert You will need to try and swap some parts around to see if you can find the culprit, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.
July 18, 20241 yr Author Solution On 7/4/2024 at 3:23 AM, JorgeB said: You will need to try and swap some parts around to see if you can find the culprit, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM. So. What I ended up doing is here, for anyone else that maybe has a similar issue. What I did was download this. https://www.hirensbootcd.org/ Then booted to it. Installed the Intel Management engine inside it once it was booted. I had already downloaded the Asus firmware with it and put it on the usb stick, and then used that to upgrade the Intel ME. It seems to be running much better now. Also the new bios said to upgrade the Intel ME "Before BIOS update, please download the Intel ME update tool from the ASUS support site and update the ME firmware to Version 16.1.30.2307 to ensure optimized system settings." But that doesn't seem to imply that it has to be done.
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.