I am running 6.1.1.5.  I did a clean shutdown to move my box, and when it came back up, my cache drive now shows "Unmountable: Wrong or no filesystem".  I tried some basic troubleshooting from the info gathered on other similar threads here, but unfortunately no luck so far.  I appreciate any help you might have to offer.

tower-diagnostics-20240502-1112.zip

28 minutes ago, CreamCheeseMan said:

6.1.1.5

6.11.5

 

Disable Docker and VM Manager until you get cache working again. Since there was no filesystem on cache, appdata, domains, system shares have been created on the array.

 

Do you think you might have filled cache? btrfs sometimes seems to have problems if you fill it up. You should set Minimum Free for cache, and for each of your user shares, to larger than the largest file you expect to write to cache or the share.

 

You can try to scrub cache, but I think the usual advice is to reformat.

 

 

I appreciate the feedback. 

 

I went ahead and disabled Docker and VM Manager.

 

It is possible I suppose the cache filled.  It has been running with no issues and I can't think of anything that might have changed, but the Minimum Free is a goof call moving forward.

 

I don't mind a reformat, but would I be correct in assuming that would mean a startover?  As far as I can tell, appdata isn't backed up anywhere that I can find.

 

Thanks for the help!

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- available spare has fallen below threshold
- media has been placed in read only mode

 

NVMe device failed, you may be able to recover the data if you mount the filesystem read-only

15 hours ago, CreamCheeseMan said:

appdata isn't backed up

There is a plugin for that.

 

Looks like you need to work on getting your plugins updated or reinstalled with the latest compatible versions.

ca.backup2.plg - 2022.12.13  (Deprecated)  (Up to date)
community.applications.plg - 2023.09.30  (Update available: 2024.04.28)  (Incompatible)
docker.folder.plg - 2022.09.24  (Update available: 2023.03.18)
unbalance.plg - v2021.04.21  (Unknown to Community Applications)

 

Hey all!  Sorry for the delay in my response.  NVMe definitely the culprit, and I was a fool not to have a backup ready to go.  I was able to recover everything though, and am back up and running.  Will certainly do some things differently!

 

I appreciate all of the advice.

Thanks again!