Looking for help after reading the support docs on what to do when a drive appears to have a corrupted file system. My cache pool is BTRFS and not mounting. I can't run scrub to check for fs errors. I was able to follow a guide and copy the data from the pool to the array. 

 

Before I reformat my pool, I'm looking for what's the right thing to do. I'd like a way to mount the drive and run a scrub, but I don't know how. Unraid sees he pool as unmounted. Is there an alternative to potentially fix the filesystem so i don't have to reformat? Since I have a cache pool do I stay with BTRFS if I do have to reformat? 

 

Here is an output from btrfs check status: 

WARNING: filesystem mounted, continuing because of --force [1/7] checking root items

[2/7] checking extents

data extent[12906602496, 53248] referencer count mismatch (root 5 owner 880 offset 7835267072) wanted 0 have 1

data extent[12906602496, 53248] bytenr mimsmatch, extent item bytenr 12906602496 file item bytenr 0

data extent[12906602496, 53248] referencer count mismatch (root 5 owner 1049456 offset 7835267072) wanted 1 have 0

backpointer mismatch on [12906602496 53248]

ERROR: errors found in extent allocation tree or chunk allocation

[3/7] checking free space tree

[4/7] checking fs roots

[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/sdb1

UUID: 875b6278-0c6e-4008-8238-cbd5f850647c

found 88101838848 bytes used, error(s) found

total csum bytes: 85604936

total tree bytes: 262356992

total fs tree bytes: 100745216

total extent tree bytes: 46514176

btree space waste bytes: 61443702

file data blocks allocated: 159848906752

referenced 85299896320

tower-diagnostics-20241027-0032.zip

Problem with the log tree, but there's also data corruption being detected, type:

 

btrfs rescue zero-log /mnt/sdb1

 

Then restart the array, if the pool mounts run a correcting scrub and post the results.

4 hours ago, JorgeB said:

Problem with the log tree, but there's also data corruption being detected, type:

 

btrfs rescue zero-log /mnt/sdb1

 

Then restart the array, if the pool mounts run a correcting scrub and post the results.

Restarted array. Drives still won't mount. 

Post new diags.

Posted

 

Edit: Also: 

 

root@Tower:~# btrfs rescue zero-log /mnt/sdb1
ERROR: mount check: cannot open /mnt/sdb1: No such file or directory
ERROR: could not check mount status: No such file or directory

tower-diagnostics-20241027-1102.zip

Edited October 27, 20241 yr by jay_busacca

Oct 27 08:01:39 Tower kernel: BTRFS error (device sdb1: state MC): nologreplay must be used with ro mount option

 

Pool is now trying to mount read-only, suggest you manually mount it read-only using the 1st option on the link below, and then backup and re-format:

 

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

 

Thank you for the support.