Woke up this morning and my unraid VM and webgui were sluggish.  Noticed logs were at 100%.    I grabbed a diagnostic, see attached.  I rebooted unraid and the cache drive says unmountable no filesystem.

 

Started array in maintenance mode and ran the btrfs check in readonly mode and got the following:

 

[1/7] checking root items 
[2/7] checking extents data backref 7812329472 root 5 owner 22293485 offset 22859776 num_refs 0 not found in extent tree incorrect 
local backref count on 7812329472 root 5 owner 22293485 offset 22859776 found 1 wanted 0 back 0x3a5e11b0 incorrect local backref 
count on 7812329472 root 5 owner 1125899929136109 offset 22859776 found 0 wanted 1 back 0x392bb5e0 backref disk bytenr does not match
extent record, bytenr=7812329472, ref bytenr=0 backpointer mismatch on [7812329472 4096] data backref 111082958848 root 5 owner 53678 
offset 0 num_refs 0 not found in extent tree incorrect local backref count on 111082958848 root 5 owner 53678 offset 0 found 1 wanted
0 back 0x39470c80 incorrect local backref count on 111082958848 root 5 owner 1125899906896302 offset 0 found 0 wanted 1 back 
0x2fcc10e0 backref disk bytenr does not match extent record, bytenr=111082958848, ref bytenr=0 backpointer mismatch on [111082958848 
274432] ERROR: errors found in extent allocation tree or chunk allocation 
[3/7] checking free space cache 
[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/sdk1 UUID:
3ab3a3ac-3997-416c-a6fd-605cfcd76924 found 249870127104 bytes used, error(s) found total csum bytes: 127993568 total tree bytes: 
1612578816 total fs tree bytes: 1038614528 total extent tree bytes: 365559808 btree space waste bytes: 331072552 file data blocks
allocated: 4561003868160 referenced 205858721792

 

Looking for any suggestions.   

 

Dan

tower-diagnostics-20201221-0712.zip

Edited December 22, 20205 yr by goinsnoopin
Solved

See here for some recovery options, if successful then format cache.

Jorge,

 

Thanks for the link.  I tried method 1 and copied my data to the array, but kept getting an error on my VM image files.  I then unmounted the cache drive and tried method 2 and saved that data to a different place on the array.   I then ran to store and purchased a new ssd with the intent of getting my unraid server back on line with the new SSD and then testing the data.   Before installing the new SSD, I decided to try method 3 with the --repair option.  After completing the repair, I stopped then started the array and everything came back up as expected.  VM started and all docker containers appear to be working as expected.

 

Should I backup the drive to a third location and then format the SSD and copy data back to it or just go with it since its working?

 

Thanks,

Dan

 

If it's working keep it, just make sure you always have up to date backups.

Got it....Thanks again!