I am a very novice user of Unraid and after the latest update my server keeps crashing. Fix Common Problems is saying I have Out of Memory errors. I've attached my diagnostic like it says and would appreciate any help. Thank you in advance!

isengard-diagnostics-20261012-2107.zip

Not the cause of your problem, but your appdata and system shares have files on the array, and, in fact, are configured to be moved to the array. Better if these shares are on cache or other pool outside the array so Dockers will perform better and so array disks can spin down since these files are always open. Nothing can move open files so you have to disable Docker in Settings before these shares can be managed.

See here for some ideas about configuring your Ryzen server:

Thank you Trurl. I disabled c-states when I originally installed Unraid as my system would crash after an hour. It was up and running for about 2 months solid until the 7.3.3 update and now it's crashing about once a day and the only error I get is the memory error. I disabled appdata and system backup to array as you suggested though. Thanks for the help!

The diagnostics show two things that may or may not be related.

1. The out of memory error is caused by Immich. About 25 minutes after the server booted, the kernel ran out of RAM and killed Immich's background worker, which was using about 9.5GB of your 16 GB on its own. Nothing else was using more than about 0.4 GB. Immich restarted by itself, and the server kept running. Immich often runs heavy jobs after a restart, such as thumbnails, smart search and face detection, and on a 16 GB server with no swap that can use up all available RAM.

To stop this from affecting the rest of the server, limit how much RAM the Immich server container can use. On the Docker tab, edit the Immich server container, switch to Advanced View, and add the following to Extra Parameters:

--memory=6G

If Immich then reaches the limit, only that container is affected, not the whole server. In Immich's Administration → Jobs page, you can also lower the job concurrency so it does less work at once.

2. The daily crash isn't in these diagnostics. They were taken after the reboot, so they don't include what happened before the crash, and the out of memory event alone wouldn't take the server down. Your syslog server is already set to save logs to a share. After the next crash, please post the syslog file from that share that covers the time before the crash. If possible, also post new diagnostics before rebooting. That should show what's actually happening when the server goes down.

11 hours ago, Nothatt said:

I disabled appdata and system backup to array

This suggests a misunderstanding of mover. It isn't doing backup. We can get further into this after your other problems are fixed.

Sorry, I used the wrong terminology. I removed the secondary storage from cache to array. I still have the appdata backup plugin running to backup appdata. So far after limiting Immich to 6G of mem and updating removing the secondary storage from appdata and system there haven't been any crashes. Thank you so much for your patience and I'll give it a day or 2 to see if there are any more crashes. I understand that mover isn't "backing up" the cache to the array rather than using the cache as a temporary storage until mover runs to move the files to the array. I'm one of those who have a local backup, off site backup, and online backup of everything so backups are on my mind I guess haha. Thank you for being so patient with me. I have ran servers before, but they were hardware RAID arrays running Red Hat with VM Wares and WINE... And that was in college 20+ years ago. I started a home server to try and degoogle as much as possible and just getting used to the learning curve. We had a really active support forum for my university and I'm glad to have a similar experience here.