July 13, 20232 yr Hi All, I upgraded from 6.11.5 to 6.12.1. As soon as it came back online, i had most of my dockers failed, so I upgraded to 6.12.2, had the same symptoms. So i downgraded back to 6.11.5 (Restore from Backup zip). That didn't help. So now I'm back to 6.12.1 with my Cache drives Unmountable. Help please. I have uploaded both diagnostics (Array Start Mode and Maintenance Mode) btrfs check status: [1/7] checking root items [2/7] checking extents data extent[1237294485504, 8192] referencer count mismatch (root 5 owner 260 offset 1042198528) wanted 0 have 1 data extent[1237294485504, 8192] bytenr mimsmatch, extent item bytenr 1237294485504 file item bytenr 0 data extent[1237294485504, 8192] referencer count mismatch (root 11529215046068469765 owner 72057080813343117 offset 1042198528) wanted 1 have 0 backpointer mismatch on [1237294485504 8192] ref mismatch on [1583247851520 16384] extent item 65535, found 1 tree extent[1583247917056, 16384] root 7 has no backref item in extent tree tree extent[1583247917056, 16384] root 9837529117959913479 has no tree block found incorrect global backref count on 1583247917056 found 2 wanted 1 backpointer mismatch on [1583247917056 16384] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space tree [4/7] checking fs roots warning line 3917 [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdi1 UUID: 145b0bd2-bcab-40f6-b250-f4c725ada4e9 found 491436212224 bytes used, error(s) found total csum bytes: 203538312 total tree bytes: 1631404032 total fs tree bytes: 1235730432 total extent tree bytes: 127582208 btree space waste bytes: 236747903 file data blocks allocated: 1756970487808 referenced 451582554112 Thanks Vithy traid-diagnostics-20230713-1145-Array Start.zip traid-diagnostics-20230713-1154-Maintenance Mode.zip Edited July 13, 20232 yr by Vithy
July 13, 20232 yr Community Expert See if this fixes the log tree and makes the fs mountable, but btrfs check shows other issues, so if it mounts suggest backing up the pool and then reformatting: btrfs rescue zero-log /dev/sdi1
July 13, 20232 yr Author 1 minute ago, JorgeB said: See if this fixes the log tree and makes the fs mountable, but btrfs check shows other issues, so if it mounts suggest backing up the pool and then reformatting: btrfs rescue zero-log /dev/sdi1 Thank you for your response. I'm assuming I do this in Maintenance Mode?
July 13, 20232 yr Community Expert Not needed, you can even do it with the array started, but then need to re-start to see if the pool now mounts.
July 14, 20232 yr Author On 7/13/2023 at 12:34 PM, JorgeB said: Not needed, you can even do it with the array started, but then need to re-start to see if the pool now mounts. I tried the command under maintenance mode then restarted the array. But i'm still getting the filesystem errors. [1/7] checking root items [2/7] checking extents data extent[1237294485504, 8192] referencer count mismatch (root 5 owner 260 offset 1042198528) wanted 0 have 1 data extent[1237294485504, 8192] bytenr mimsmatch, extent item bytenr 1237294485504 file item bytenr 0 data extent[1237294485504, 8192] referencer count mismatch (root 11529215046068469765 owner 72057080813343117 offset 1042198528) wanted 1 have 0 backpointer mismatch on [1237294485504 8192] ref mismatch on [1583247851520 16384] extent item 65535, found 1 tree extent[1583247917056, 16384] root 7 has no backref item in extent tree tree extent[1583247917056, 16384] root 9837529117959913479 has no tree block found incorrect global backref count on 1583247917056 found 2 wanted 1 backpointer mismatch on [1583247917056 16384] ERROR: errors found in extent allocation tree or chunk allocation [3/7] checking free space tree [4/7] checking fs roots warning line 3917 [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/sdi1 UUID: 145b0bd2-bcab-40f6-b250-f4c725ada4e9 found 491507535872 bytes used, error(s) found total csum bytes: 203607832 total tree bytes: 1631535104 total fs tree bytes: 1235763200 total extent tree bytes: 127582208 btree space waste bytes: 236806362 file data blocks allocated: 1757058953216 referenced 451653742592
July 14, 20232 yr Community Expert Suspected as much since the log tree is not the only issue, you can try these recovery options here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
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.