wbgolden

It's been pretty frustrating. I'd be open to any suggestions, including reformatting the two devices in the cache pool. I know I'd have to rebuild everything. I just don't want to lose the files on the HDDs!

Hi again. My original problem is back! After getting the cache pool back online yesterday with Jorge's help, now I'm back to the original cache problem where it's mounted read only, and unraid is unable to write to the Docker image (on the cache pool so that makes sense). Docker service is failing to start. This happened when I was going through spaceinvader's video to fix my Plex database. I'm starting to think about starting from scratch but hoping it's fixable. I pulled the attached diagnostics right after getting the last error. Thanks! EDIT: Actually just noticed that this time Docker DID launch, but none of the containers are working. Getting execution error when trying to start the containers. tower-diagnostics-20230214-1519.zip

Thanks, Jorge!

That looks to have gotten the cache pool back online! New diagnostics attached. tower-diagnostics-20230214-0757.zip

Diagnostics attached. I should have known better! Also, I'm sorry I forgot to mention that I restored the flash drive from an earlier backup and that's when the cache pool drives came up as no file system. I was trying to remember all the steps and that possibly very important part slipped my mind. tower-diagnostics-20230213-1330.zip

Hello! First post Over the last few days, some of my Docker containers would just stop and would not restart. I'd do a safe reboot and cross fingers when this happened. Eventually it degraded to the point where Docker could not launch, so I stopped it and deleted the image. I was able to rebuild the containers as before. Then I'd get errors (sorry I don't have them anymore). After the last reboot, my cache pool devices, two WD NVMe SSD's, are coming up as unmountable: no file system. I tried the recovery process in the FAQ but couldn't get it to work (possibly due to my lack of Linux knowledge). Hoping I can get some help with recovery! syslog attached syslog.txt