Jump to content

CACHE: UNMOUNTABLE: UNSUPPORTED OR NO FILE SYSTEM


Recommended Posts

Ran into this after last update. (I think?) 

 

Any way to salvage cache data? Diags attached, thanks in advance!

 

*Additional info- I had a encrypted BTRFS RAID0 setup for cache. (2 NVME disks) I attached a older backup with everything as it was before...(2023 file)

 

I ran a BTRFS check on the cache (RO) and got this- 
 

parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
[1/7] checking root items
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
[2/7] checking extents
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
ref mismatch on [1553951424512 16384] extent item 65535, found 1
tree extent[1553951440896, 16384] root 7 has no backref item in extent tree
tree extent[1553951440896, 16384] root 9836619805773266951 has no tree block found
incorrect global backref count on 1553951440896 found 2 wanted 1
backpointer mismatch on [1553951440896 16384]
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space tree
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 6670712832 wanted 576460752304546710 found 1123222
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
parent transid verify failed on 7971232710656 wanted 1126103 found 1124055
Ignoring transid failure
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
ERROR: transid errors in file system
Opening filesystem to check...
Checking filesystem on /dev/mapper/nvme0n1p1
UUID: e377b065-8577-4af4-b086-02b3941c5a39
found 1179790974976 bytes used, error(s) found
total csum bytes: 664448872
total tree bytes: 1707376640
total fs tree bytes: 600408064
total extent tree bytes: 245776384
btree space waste bytes: 352470071
file data blocks allocated: 5484646404096
 referenced 1090518487040

zeus-diagnostics-20240222-1945.zip

zeus-diagnostics-20231219-1711.zip

Edited by dja
Link to comment
3 hours ago, JorgeB said:

These are usually fatal, see here for some recovery options, btrfs restore is usually the best option for this:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

 

I believe I took that diagnostic after messing with the cache disks. I had removed, started, stopped and re-added them but forgot to put them in correctly, that being encrypting BTFRS RAID0.  I did the same thing again but with the correct options and after running a repair from command line it restored things. I'm not seeing any loss of data (at the moment...) So I guess it worked? I only had dockers/VMs on that and have multiple backups, so I guess I can restore if need be. (and freeze my backup tools for a bit!! lol) 

 

Thanks for the help. 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...