Fletch79

Just some feedback for the above - @JorgeB was right - my cache drive had been corrupted and set to read only I tried to copy out the data to the array using terminal - That didn;t work for me (i may have been doing it wrong) Using windows network access was giving simialr results I ended up using FTP - pulling the folders off the cache drive before erasing, and reformatting it ZFS and using FTP again to put the files back to the cache Its seems to have all worked well for me I do have an issue with my log files being big now - but i'm gonna reboot and see what happens There may be another post incoming!

Just run a BTRFS Check on the cache drive - Here is the status report [1/7] checking root items [2/7] checking extents data extent[2057591570432, 245760] referencer count mismatch (root 5 owner 5435779 offset 2976559104) wanted 0 have 1 data extent[2057591570432, 245760] bytenr mimsmatch, extent item bytenr 2057591570432 file item bytenr 0 data extent[2057591570432, 245760] referencer count mismatch (root 9537491067117502469 owner 4294936705 offset 2976559104) wanted 1 have 0 backpointer mismatch on [2057591570432 245760] 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/nvme1n1p1 UUID: 1b3bf6c1-e65f-4c8c-abea-ef4408e6f2e2 found 170475630592 bytes used, error(s) found total csum bytes: 128087588 total tree bytes: 677412864 total fs tree bytes: 317341696 total extent tree bytes: 159580160 btree space waste bytes: 162294837 file data blocks allocated: 562199609344 referenced 155704946688

I'm going to preface this with - unraid and command line noob - Will happily learn and take guidance so may need ELI5 a few of my dockers started acting strange today - Restarted the containers and was getting execution failed errors - So rebooted the server and all the dokcers looked like they came back up. Few hours later i realise that while they all look like they came back online they are still not correct - Heimdall crashed out, plex cannot see any media etc So after a little bit of messing about i decide to rebuild my docker image - I've had that issue before so thought i'd give it a try Stop the docker service - But i do not have permission to delete the docker image - Tried Via Windows and via command line (i didin't change permissions on the file or force a delete) try to restart the docker service and it won;t restart. Run fix common problems and it tells me my cache drive is set to read only or full (its not full) Is it possible it has been set read only? How would that have happened? How do i resolve this?? I have attached the diagnostics! Thanks in Advance Fletch storage-diagnostics-20231109-2103.zip

Thank you - I did try and google but had no joy finding that information Its worked perfectly

I'm having issues with UNRAID for the first time - and as a complete amateur i am struggling with what to do I'm afraid you will have to ELI5 Last night i installed a P600 and set it up with the Drivers and setup the plex docker - all was working well and my library was scanning away all night Ran a docker update for a couple of the dockers and i now get this error in the docker page I have tried to stop and remove the dockers - but that fails - i tried to stop them from the terminal - and that also fails The following is whats in the logs - it does repeat over and over What should my next steps be? I've attached my diagnostic Zip Apr 13 17:13:28 Storage kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2142, gen 0 Apr 13 17:13:28 Storage kernel: BTRFS info (device loop2): no csum found for inode 7590 start 0 Apr 13 17:13:28 Storage kernel: BTRFS warning (device loop2): csum failed root 3194 ino 7590 off 0 csum 0xb051893c expected csum 0x00000000 mirror 1 Apr 13 17:13:28 Storage kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2143, gen 0 Apr 13 17:13:29 Storage kernel: verify_parent_transid: 10 callbacks suppressed Apr 13 17:13:29 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:29 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:29 Storage kernel: BTRFS info (device loop2): no csum found for inode 7590 start 0 Apr 13 17:13:29 Storage kernel: BTRFS warning (device loop2): csum failed root 3194 ino 7590 off 0 csum 0xb051893c expected csum 0x00000000 mirror 1 Apr 13 17:13:29 Storage kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2144, gen 0 Apr 13 17:13:29 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:29 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:29 Storage kernel: BTRFS info (device loop2): no csum found for inode 7590 start 0 Apr 13 17:13:29 Storage kernel: BTRFS warning (device loop2): csum failed root 3194 ino 7590 off 0 csum 0xb051893c expected csum 0x00000000 mirror 1 Apr 13 17:13:29 Storage kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2145, gen 0 Apr 13 17:13:30 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:30 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:30 Storage kernel: BTRFS info (device loop2): no csum found for inode 7590 start 0 Apr 13 17:13:30 Storage kernel: BTRFS warning (device loop2): csum failed root 3194 ino 7590 off 0 csum 0xb051893c expected csum 0x00000000 mirror 1 Apr 13 17:13:30 Storage kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2146, gen 0 Apr 13 17:13:30 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:30 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:30 Storage kernel: BTRFS info (device loop2): no csum found for inode 7590 start 0 Apr 13 17:13:30 Storage kernel: BTRFS warning (device loop2): csum failed root 3194 ino 7590 off 0 csum 0xb051893c expected csum 0x00000000 mirror 1 Apr 13 17:13:30 Storage kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 2147, gen 0 Apr 13 17:13:31 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:31 Storage kernel: BTRFS error (device loop2): parent transid verify failed on 5780209664 wanted 5176444 found 5176316 Apr 13 17:13:31 Storage kernel: BTRFS info (device loop2): no csum found for inode 7590 start 0 Apr 13 17:13:31 Storage kernel: BTRFS warning (device loop2): csum failed root 3194 ino 7590 off 0 csum 0xb051893c expected csum 0x00000000 mirror 1 storage-diagnostics-20220413-1832.zip