Hello,

 

I have a cache pool with two identical nvme 970 evo plus drives. Today I have seen that the second nvme of the pool is also showing up on the unassigned devices section. Unfortunately I have not made a screenshot of this. Array or cache pool did not show any faults. I have taken the array offline and put it back online straight away. The pool looked normal as nothing has happened. I then checked the log files and see many of these:

May 10 14:07:47 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 2242775830528 on dev /dev/nvme1n1p1, physical 952075243520, root 5, inode 49729, offset 7172382720, length 4096, links 1 (path: system/docker/docker.img)
May 10 14:07:47 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 7471, rd 7, flush 722, corrupt 11770, gen 186
May 10 14:07:47 Tower kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 2242775830528 on dev /dev/nvme1n1p1

 

I then did a scrub with the option ticked "repair corrupted blocks" which returned with 4 uncorrectable errors.

 

I have checked the logs back to October 2023 and I have not found any of the BTRFS errors in the logs.

I am backing up my appdata daily via the "appdata backup" plugin.

 

I do not want to go any further without asking what the next steps should be. 

 

Best Regards,

Stefan

tower-diagnostics-20240510-1301.zip

If the docker image is the only corrupt file you can recreate it:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

 

Then run another scrub to confirm no more errors.

Hello JorgeB,

 

thank you for looking into this and I appreciate your help. I did recreate the docker image and did another scrub which seems to have the problem solved. 

 

Best Regards,

Stefan