January 6, 20242 yr Problem: No problems with Unraid or hardware for several years. Server was turned off around July, then turned back on in September. Server began to randomly restart resulting in needing to run a parity check all the time. Eventually began to pinpoint it to using Jellyfin and server crashing while watching higher quality files that might have been more intensive for transcoding. Turned off transcoding and it felt like the crashes stopped. Starting a few weeks ago the server would restart in the middle of the night or randomly in the day when not using Jellyfin. So while it definitely crashed while using Jellyfin, that's either not the main cause, or there's now additional causes. Things I've tried changing transcoding settings. Updating Unraid/hoping an update might fix the problem if software Changing macvlan to ipvlan Syslog to server. I don't see anything showing an error before it restarts. For example (see below), It looks like it updated plugins at midnight. A little later drives spun down, a trim process happened an hour or two later, things spun down again, and then around 6:00 the server restarted (I'm assuming that's what this indicates) Jan 5 20:17:39 Tower monitor: Stop running nchan processes Jan 5 22:00:07 Tower emhttpd: read SMART /dev/sdh Jan 6 00:00:01 Tower Plugin Auto Update: Checking for available plugin updates Jan 6 00:00:09 Tower Plugin Auto Update: NerdTools.plg version 2024.01.06 does not meet age requirements to update - 0 days old Jan 6 00:00:09 Tower Plugin Auto Update: Checking for language updates Jan 6 00:00:09 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Jan 6 00:05:41 Tower emhttpd: spinning down /dev/sdc Jan 6 00:16:01 Tower emhttpd: spinning down /dev/sde Jan 6 00:17:00 Tower emhttpd: spinning down /dev/sdd Jan 6 00:17:02 Tower emhttpd: spinning down /dev/sdg Jan 6 01:02:28 Tower root: /var/lib/docker: 11.3 GiB (12100575232 bytes) trimmed on /dev/loop2 Jan 6 01:02:28 Tower root: /mnt/cache: 38 GiB (40803491840 bytes) trimmed on /dev/sdf1 Jan 6 02:02:22 Tower emhttpd: spinning down /dev/sdh Jan 6 06:03:32 Tower file.activity: Starting File Activity Jan 6 06:03:32 Tower emhttpd: Starting File Activity... Jan 6 06:03:32 Tower file.activity: File Activity inotify starting Jan 6 06:03:32 Tower inotifywait[14355]: Setting up watches. Beware: since -r was given, this may take a while! I'm currently not sure if this is a software problem (it seemed like there were problems with Unraid OS update over the summer/fall for some people) or a hardware problem (I've run a ram test. not sure why there's not an error before shutdown). No idea what else to try or how why I'm not finding errors, but I don't know how to read the diagnostic logs to understand this further. Any help would be greatly appreciated! tower-diagnostics-20240106-0643.zip
January 7, 20242 yr Community Expert Server restarting by itself, vs crashing or hanging, is almost always a hardware issue (or power).
January 7, 20242 yr Author I probably worded it poorly but I assume it's restarting after a crash. How would I know the difference? I'm not seeing any errors before it does an unclean restart. If it is hardware is there anything in the diagnostics I can look at to determine? I see nothing in the syslog.
January 8, 20242 yr Community Expert You can enable the syslog server and post that after a crash, but like mentioned if it's rebooting on its own it's likely a hardware issue and most likely there won't be anything logged.
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.