TessyPowder Posted May 6, 2020 Posted May 6, 2020 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. Server Specs: 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 No cache 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 ?) greenytron-diagnostics-20200506-0948.zip greenytron-syslog-20200506-0802.zip Quote
TessyPowder Posted May 6, 2020 Author Posted May 6, 2020 (edited) And would that solve my problem ? Is loop2 the docker.img ? EDIT: I found the answer in another thread. " loop2 is your docker.img Easiest, pain free solution is to stop the docker service (settings) delete the image (advanced view) re-enable the service, then check off all your apps via Apps - Previous Apps section and hit install. Couple of minutes later you're back in business Probably caused by unclean shutdowns." I will try to recreate the docker.img. Edited May 6, 2020 by TessyPowder Quote
TessyPowder Posted May 6, 2020 Author Posted May 6, 2020 I forgot to mention, that i am currently running my unraid in safe mode. Quote
JorgeB Posted May 6, 2020 Posted May 6, 2020 19 minutes ago, TessyPowder said: Is loop2 the docker.img ? Yes Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.