ribbitman

Like the title says, Docker service now won't start at all in 6.12.10. I've been having problems for the past couple months with my cache pool (2x 1TB ssd) coming up unmountable. At first, the pool was an NVME and an SSD. When the drives came up unmountable, unassigning the drives, starting/stopping the array, then reassigning the drives fixed it a couple times. After it kept happening, I unmounted the NVME and installed a second SSD so the pool was 2 SSDs. When they came up unmountable again, I'd reformat the drives and restore from appdata backups, and that would fix it for a while. I replaced both SSDs, and the pool drives have not come up unmountable since. Instead, certain docker containers would become unresponsive about weekly and wouldn't restart, so rebooting the server fixed it. Now Docker won't start at all. Any suggestions? tower-syslog-20240729-0541.zip

Commenting to get notification if this is ever solved. I have the exact same question.

Seeing a lot of this around here lately -- a power outage made my cache pool unmountable, which is where domains and appdata were. I was running VM Backup before the outage, and despite having set it to backup to the array monthly and keep 2 backups, it kept 12. I copied/renamed the latest vdisk image back to domains and the xml file back to /etc/libvirt/qemu, but when the vm starts, it asks where it's supposed to boot from, and wants to reinstall WIndows. What step am I missing?