I keep providing diagnostic files and I'm not getting anywhere with them, just being told to rebuild docker or the diagnostics don't have contents because of a restart. My server is currently completely inaccessible again, I obviously can't get logs. I've:

• Blasted away duplicate docker shares

• Cleaned up remnant docker shares from disks (and appdata)

  • This did speed things up with the UI in general, lots less loading screens when opening docker tab and such, dockers and commands respond very well now, not sluggish.

• Switched docker from virtual disk to direct to disk because I had to keep rebuilding the corrupt docker share, so far this has helped prevent me from having to rebuild

Observations

• Server stays up about 24-72 hours before failing.

• Seems to happen overnight, fine during the day.

• It was ok after making some of the above docker adjustments for longer than it had been until I had a power outage, powered it off safely, and it has started the 24-72 hour crashing again.

I still cannot grasp why UnRaid cannot protect itself from whatever is going on, let alone write some log files. Edit: I do appreciate all suggestions and assistance thus far, I've worked through some odd changes I made as a result of this crashing and it has helped the user experience for me, but it hasn't helped the failures.

Edited July 31Jul 31 by moka939

My KVM showed no signal from unraid, I hit the power button once and this is where it is stuck during the power down.

Set up the Syslog server.

https://docs.unraid.net/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs/#persistent-logs-syslog-server

In your situation, I would use the Boot disk for storage.

Also include your diagnostics file when you post up the syslog after the next crash.

Does running unraid in safe mode with docker service disabled produce the same results?

At a minimum you need to rule out docker entirely by leaving it off for an extended period of time.

Edited August 1Aug 1 by MowMdown