June 11, 20206 yr So my machine was running for a year, when I had to shut it down for electrical work I was reminded I had to buy a key ( totally forgot since it worked great for so long). thing Is now my server seem to keep crashing after a bit more then 5 hours ( I was checking the webgui for that long, not sure how long after it crashed). its been repeating for the past week or so. any idea what would be the issue ?
June 12, 20206 yr Author alright ill try that, but isnt it wierd it worked for a year then when installing the key, it stop working ?
June 12, 20206 yr 44 minutes ago, amadnei said: alright ill try that, but isnt it wierd it worked for a year then when installing the key, it stop working ? first write updates to USB thumb drive in a while when applying key pushes it over the edge? I might try a backup and restore onto new installation on new USB drive and see how it goes,,,,
June 12, 20206 yr Community Expert 6 hours ago, amadnei said: but isnt it wierd it worked for a year then when installing the key, it stop working ? It certainly has nothing to do with the key.
June 20, 20206 yr Author On 6/11/2020 at 3:30 PM, johnnie.black said: Try this, it might catch something. I used the syslog tool, but I don't know how to read it to know where it bugged. I believe It crashed a few hours after I booted it again, not sure if it crashed more time after that ( went to sleep ). syslog
June 20, 20206 yr Community Expert It crashed here: Jun 20 03:40:01 Tower crond[2025]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null Jun 20 08:16:28 Tower kernel: Linux version 4.19.107-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Mar 5 13:55:57 PST 2020 There's nothing logged pointing to the issue, likely a hardware problem, since it's a Ryzen server have you seen this?
June 20, 20206 yr Author 1 hour ago, johnnie.black said: It crashed here: Jun 20 03:40:01 Tower crond[2025]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null Jun 20 08:16:28 Tower kernel: Linux version 4.19.107-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Mar 5 13:55:57 PST 2020 There's nothing logged pointing to the issue, likely a hardware problem, since it's a Ryzen server have you seen this? alright Ill try this tomorow, Im using 4 dimms ( 32gb ) at 3000mhz I believe, ill underclock to 1866. in the mean time I change from my UPS to a regular plug, maybe thats causing some issues.
June 28, 20206 yr Author On 6/20/2020 at 11:48 AM, johnnie.black said: It crashed here: Jun 20 03:40:01 Tower crond[2025]: exit status 3 from user root /usr/local/sbin/mover &> /dev/null Jun 20 08:16:28 Tower kernel: Linux version 4.19.107-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Mar 5 13:55:57 PST 2020 There's nothing logged pointing to the issue, likely a hardware problem, since it's a Ryzen server have you seen this? I dropped the ram to 1866, but I keep getting crashs, any idea what I should check next ?
June 29, 20206 yr Community Expert 15 hours ago, amadnei said: I dropped the ram to 1866, but I keep getting crashs, any idea what I should check next ? Did you also set the "power supply idle control" to the recommended setting? Other than that it might be a real hardware issue.
Archived
This topic is now archived and is closed to further replies.