I installed new RAM yesterday, but it was defect and caused a kernel panic stack trace.
I rebooted multiple times to figure out if the module or the socket is bad and had multiple stack trace errors. After changing a bios i could boot into unraid and started the array. But after an hour a vm had a stack trace error then i stopped the system and removed the new RAM.
After starting again i could not get the array started. In the system log i saw multiple btrfs errors.
I then started the array in maintenance mode and started a parity check. 640 Errors were found and corrected.
Now i still can't start the array (it get's stuck on starting services) without maintenance mode and the btrfs errors didn't change (logs are attached)
I can acces my Filesystem and all files seem OK, but i can't use the array normally.
AMD Ryzen 5 2700 (8 Cores, 16 Threads)
16 GB RAM DDR4-3000 (2x8GB)
(i tried to add 16 GB DDR4-3200)
3 x 2TB HDD Drives
I have 40 Dockers and one VM.
Some of the Data is EXTREMELY important to me (a lot of Source code and a Nextcloud Server)
How can i repair the filesystem ? What went wrong ? Do i need to recreate my filesystem ? I would need a Cloud Storage for Backup, because my server is the biggest storage device i have.
Did i send enough information ?
Thanks in advance
I have seen a few other threads about similar errors, but i didn't understand how they fixed it (how can i rebuild the docker image ?)