Hi all, 

 

I've been moving my files around my drives using unbalance and may have done something wrong? I went to use my plex and it errored out this afternoon, so when i got home i checked my server and it failed to login. So i've checked the system logs and i'm seeing the below, can anyone else explain what particularly has failed (or what I've likely done or how I can fix it... assuming its possible)? it just keeps repeating throught my entire log and only updating the corrupt numbers

 

 

Sep  7 20:52:15 Server kernel: BTRFS info (device loop2): no csum found for inode 588 start 12288
Sep  7 20:52:15 Server kernel: BTRFS warning (device loop2): csum failed root 8193 ino 588 off 12288 csum 0x00c1d612 expected csum 0x00000000 mirror 1
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7656, gen 0
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bad tree block start, want 508821504 have 0
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bad tree block start, want 508821504 have 0
Sep  7 20:52:15 Server kernel: BTRFS info (device loop2): no csum found for inode 588 start 12288
Sep  7 20:52:15 Server kernel: BTRFS warning (device loop2): csum failed root 8193 ino 588 off 12288 csum 0x00c1d612 expected csum 0x00000000 mirror 1
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7657, gen 0
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bad tree block start, want 508821504 have 0
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bad tree block start, want 508821504 have 0
Sep  7 20:52:15 Server kernel: BTRFS info (device loop2): no csum found for inode 588 start 12288
Sep  7 20:52:15 Server kernel: BTRFS warning (device loop2): csum failed root 8193 ino 588 off 12288 csum 0x00c1d612 expected csum 0x00000000 mirror 1
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7658, gen 0
Sep  7 20:52:15 Server kernel: BTRFS info (device loop2): no csum found for inode 588 start 12288
Sep  7 20:52:15 Server kernel: BTRFS warning (device loop2): csum failed root 8193 ino 588 off 12288 csum 0x00c1d612 expected csum 0x00000000 mirror 1
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7659, gen 0
Sep  7 20:52:15 Server kernel: BTRFS info (device loop2): no csum found for inode 588 start 12288
Sep  7 20:52:15 Server kernel: BTRFS warning (device loop2): csum failed root 8193 ino 588 off 12288 csum 0x00c1d612 expected csum 0x00000000 mirror 1
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7660, gen 0
Sep  7 20:52:15 Server kernel: BTRFS info (device loop2): no csum found for inode 588 start 12288
Sep  7 20:52:15 Server kernel: BTRFS warning (device loop2): csum failed root 8193 ino 588 off 12288 csum 0x00c1d612 expected csum 0x00000000 mirror 1
Sep  7 20:52:15 Server kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 7661, gen 0

Attach Diagnostics to NEXT post in this thread.

Hello Trurl,

 

Please find attached, I hope this helps and thanks for taking a look.

diagnostics-20210907-2142.zip

Corrupt docker.img . It doesn't look full now, have you had problems filling it?

 

You will have to delete and recreate docker.img .

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

 

Then reinstall your containers with Previous Apps.

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

Thank you so much Trurl! It work again

 

I realize what I did wrong this morning after reading the links in your message. I also didn't register what the Main menu had shown me, I must have glazed over it. Some how in my transfers with Unbalance, I set a share to "prefer" vs "yes". Meaning it was filling my cache drives with the share files during Mover and filling the cache drive to only a gig or two, ergo my Docker had no space left, hence the errors. 

 

I followed the links and was able to get my dockers up and will be sure to pay more attention to the share's and Main going forward. 

 

I really appreciate you taking the time to read my message and providing me the information I needed to fix my setup, thank you.