Hi, I've set up Unraid 6.12.4 and have only really started to properly use it in the last few days, and am still on a Trial license. This has involved setting up the main array of 4x 18TB drives (xfs, one as parity), and a pair of 1TB SSD for the cache (zfs, mirrored). For apps I have a few - Unassigned Devices/Plus, the nVidia driver/GPU stats, Dynamix System Temp, Tasmota Power Monitor, and lastly Krusader, for moving my data from my old FreeNAS box to Unraid via a SMB share to the FreeNAS machine. The problem is that the Unraid server has now suffered three unclean shutdows during this time, and is currently on its second (24 hour) cache rebuild, the second unclean shutdown didn't need one for some reason. After I discovered the logs are kept in memory (?!) I put another SSD in the system to write the log files to, however these don't seem to have captured anything useful, mostly being full of 'unRAID-main kernel: CIFS: __readahead_batch() returned xxx' entries up until 05:03 when the shutdown seems to have occurred and didn't record anything further until I logged in again the next morning and started the array.. Checking the Syslog via Unraid (attached) doesn't seem to reveal much more, these begin at 05:11 and seem to capture the startup.

 

On the first and third unclean shutdowns Krusader was probably still copying data across (which is maybe why these occurrances needed the cache rebuild?) but on the second one it must certainly have completed copying, so I'm not sure Krusader and/or copying data is the issue.

 

Any ideas why this has happened? Is there any other logging I can enable to see what is happening?

unraid-main-syslog-20231119-1140.zip

If the server is rebooting on its own, instead of crashing or hanging, it suggests a power or hardware issue.

Thanks for your reply. It seems to be some sort of crash, the server is not set to reboot (deliberately) and in it's previous role it would stay running for months on end. All that has really changed is that it is now running Unraid. It has redundant PSUs which are both ok, and the FreeNAS box is running off the same power and it is staying up, so it hasn't been due to a powercut.

Without anything relevant logged and the server rebooting on its own don't see how it can be an Unraid issue.

So no clues then. Well, thanks anyway.

Edited November 19, 20232 yr by OneFour

One thing you can try is to boot the server in safe mode with all docker/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.