Ok. I have a different mobo with new ram coming in soon.

The Docker img, I never really knew what it should be so I just picked what I thought would be "enough" when I first made it years back.

I can change it to whatever you recommend no problem.

I use disk space manager to balance the array for all my media. Perhaps it moved that as well? If you can tell me how to fix that I will make it happen.

I will run a check on the ram asap in the meantime.

There also appears to be a container constantly restarting; see if you can find out which by looking at all their uptimes.

Ok thanks, i will look for that. I do also see a bunch of nginx errors but don't know what to make of them

Have you done memtest yet?

You must never attempt to run any computer unless memory is working perfectly. Everything goes through RAM. The OS and other executable code. Your DATA! EVERYTHING! The CPU can't do anything with anything until it is loaded into RAM.

I did just run memtest, there were errors but aapparently the list was too long to show all of them in the log.

Also, for the Dockers, there are only 12 that run on startup. They all say 58 minutes ago, but only 2 of them say (healthy), how do I know which ones are the faulty ones that keep restarting?

9 minutes ago, LordShad0w said:

memtest, there were errors

You should quit running your server immediately until you have trustworthy RAM. What you have now is corrupting EVERYTHING!

Can I safely put in the 32GB stick I have in my main machine without hurting anything? It is a known good and tested stick (just did memtest last week) so I would be going from 64 in the server down to 32.

1 minute ago, LordShad0w said:

put in the 32GB stick I have in my main machine without hurting anything?

Do you mean put it in the server with BAD RAM? Why?

You should shut down that server with the BAD RAM and not use it again until it has trustworthy RAM. It can only make things worse the way it is now.

13 minutes ago, LordShad0w said:

Can I safely put in the 32GB stick I have in my main machine without hurting anything? It is a known good and tested stick (just did memtest last week)

It is good RAm and is the same type (DDR5) and I have it on hand. Just wondering if I can use it to get the server back up and running until my new parts come since it will not be until end of May that they arrive.
Server is OFF BTW. I made sure of that since you said to.

Edited April 13Apr 13 by LordShad0w

You mean replace the BAD RAM with known good RAM from another server. That should be OK, but you should do another memtest with the good RAM in that motherboard just to make sure it is working OK before trying to run it again.

Ok cool, Thank You man. I will give that a go.

Ok RAM checks out and is all good with the new stick.

Still had a crap ton of BTRFS errors though. Main Cache was FUBAR.

Shifted everything to the array, powered down, removed bad SSD, installed new one, rebooted, assigned to old slot, formatted, moved data back to Cache from Array then rebooted again. Checked logs with Enhanced Logs and so far, all is well.

I also did a full check on the new SSD itself and it also reports 0 errors.

Thank you so much for helping me through this as I would not have arrived here on my own to start repairing things.

1 hour ago, LordShad0w said:

Still had a crap ton of BTRFS errors though. Main Cache was FUBAR.

Shifted everything to the array, powered down, removed bad SSD, installed new one

Those errors were caused by bad RAM, and they won't go away just because RAM is good now. The bad RAM corrupted your data. Nothing likely wrong with the drive.

If you have appdata backup you can probably recover your dockers.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

4 hours ago, trurl said:

If you have appdata backup you can probably recover your dockers.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

I got the Dockers restored using exactly this. Thanks man!