revjim23

This worked temporarily but the drive would still not mount after a reboot, and when it was mounted it was read only. Maybe that's by design, I do not know. I formatted the cache pool as suggested. I run KluthR's excellent appdata backup plugin [here] and I have plenty of good backups. The last time everything worked properly was 9/20/2023 so I restored an appdata from 9/19/2023 and everything seems to be working fine. All dockers loaded on the first try and they seem to be completely back to normal. Thanks very much for the guidance, JorgeB!

My cache pool is unmountable, screen shot and diagnostics below. I have read through many similar threads but still not sure on the least destructive / recommended steps for a situation like this. Results of a check --readonly: [1/7] checking root items [2/7] checking extents data extent[850904604672, 4096] referencer count mismatch (root 5 owner 3169127 offset 76865536) wanted 0 have 1 data extent[850904604672, 4096] bytenr mimsmatch, extent item bytenr 850904604672 file item bytenr 0 data extent[850904604672, 4096] referencer count mismatch (root 1152921504606846981 owner 72057080810406003 offset 76865536) wanted 1 have 0 backpointer mismatch on [850904604672 4096] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space tree [4/7] checking fs roots root 5 inode 25835 errors 200, dir isize wrong root 5 inode 4381459 errors 1, no inode item unresolved ref dir 25835 index 371604 namelen 23 name torrents.fastresume.bak filetype 1 errors 5, no dir item, no inode ref root 5 inode 4381460 errors 1, no inode item unresolved ref dir 25835 index 371605 namelen 19 name torrents.fastresume filetype 1 errors 5, no dir item, no inode ref unresolved ref dir 25835 index 371607 namelen 23 name torrents.fastresume.bak filetype 1 errors 5, no dir item, no inode ref root 5 inode 4381463 errors 1, no inode item unresolved ref dir 25835 index 371606 namelen 23 name torrents.fastresume.tmp filetype 1 errors 5, no dir item, no inode ref unresolved ref dir 25835 index 371608 namelen 19 name torrents.fastresume filetype 1 errors 5, no dir item, no inode ref unresolved ref dir 25835 index 371610 namelen 23 name torrents.fastresume.bak filetype 1 errors 5, no dir item, no inode ref root 5 inode 4381464 errors 1, no inode item unresolved ref dir 25835 index 371609 namelen 23 name torrents.fastresume.tmp filetype 1 errors 5, no dir item, no inode ref unresolved ref dir 25835 index 371611 namelen 19 name torrents.fastresume filetype 1 errors 5, no dir item, no inode ref unresolved ref dir 25835 index 371613 namelen 23 name torrents.fastresume.bak filetype 1 errors 5, no dir item, no inode ref root 5 inode 4381465 errors 1, no inode item unresolved ref dir 25835 index 371612 namelen 23 name torrents.fastresume.tmp filetype 1 errors 5, no dir item, no inode ref unresolved ref dir 25835 index 371614 namelen 19 name torrents.fastresume filetype 1 errors 5, no dir item, no inode ref root 5 inode 4381466 errors 1, no inode item unresolved ref dir 25835 index 371615 namelen 23 name torrents.fastresume.tmp filetype 1 errors 5, no dir item, no inode ref ERROR: errors found in fs roots Opening filesystem to check... Checking filesystem on /dev/sdg1 UUID: 28e3b912-680c-46a6-b0b7-ea1ee4f1a015 found 176285323264 bytes used, error(s) found total csum bytes: 154503256 total tree bytes: 410517504 total fs tree bytes: 151732224 total extent tree bytes: 58130432 btree space waste bytes: 84860553 file data blocks allocated: 2828066377728 referenced 151608881152 I could really use some help figuring out the next steps. Thanks everyone. gargoyle-diagnostics-20231118-1008.zip