Terebi
-
Posts
124 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Terebi
-
-
I had a similar issue, but just clicking a bunch at various places in the text box eventually let me type into it.
-
Ive made a new post, in support rather than bug as I have identified the root cause as my parity drive
-
Unfortunately its an asustor prebuilt nas, so my ability to diagnose/fix hardware is a bit limited. I will turn off each of the NVMEs in turn to see if that fixes it, and if neither does, try without cache/parity for a day.
I thought the 3 hour memtest would be enough, but I can run it for longer
I had previously (months ago) been playing with enabling cstates, and did notice when they were enabled, stability was VERY bad (multiple crashes per day). I thought I had disabled all of that, but I will take a second look.
The part that is really confusing to me is why it only crashes at night. If it was hardware, I would expect it to be happening randomly at any time of day, or especially during high usage.
-
The cpu increase started at 11:47, thats right when "hourly" tasks are started per cron
But its interesting to me that this problem does not happen every hour.
I do have the userscripts plugin, and there is one hourly task, but it is a single line script that runs curl to update duckdns.
The /etc/cron.hourly dir has a single script called user.script.start.hourly.sh which was pre-existing. it calls /usr/local/emhttp/plugins/user.scripts/startSchedule.php
From what I can read, that is just calling the hourly user scripts scripts. And as I said, I only have the one.
[6.12.4] Server hangs once a day since updating to 6.12.4
in Stable Releases
Posted
I had a very similar issue, and even though my memtest for 8 hours passed, it was still bad/misconfigured ram.
I took out one of the ram dimms, and it completely resolved my problem