exceptional-ant1068

Great! Thank you for your help!

Oooh wow, Docker has started up again and I'm seeing the shares. The new diagnostics are attached. Should I be looking into swapping the SSD? gtower-diagnostics-20230906-1245.zip

OK - I ran with -L and here's what was displayed:

I've run the filesystem check (without -n) and it immediately shows this status: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

I was on 6.12.3 before the downgrade but I believe it downgraded to 6.12.1. Diagnostics attached gtower-diagnostics-20230906-1119.zip

I accidentally hit the downgrade button from the Tools tab, restarted to allow the downgrade to happen, then upgraded to 6.12.4. Everything seemed fine, so this morning I updated my docker containers which resulted in major issues. One of them had an issue updating which then resulted in all of the containers showing as unavailable. I rebooted the machine and now the docker tab says 'Docker Service failed to start.'. The Fix Common Problems has many issues shown: ERROR: Unable to write to cache. Suggested fix: Drive mounted read-only or completely full. (it is not full) WARNING: Share Applications references non existed pool cache WARNING: Share data references non existing pool cache WARNING: Share Downloads references non existent pool cache WARNING: Share VirtualMachines references non existent pool cache There's no mention of appdata but it seems gone as well. Would welcome any suggestions.