Robladw

Yeah this has fixed it. Thank all of you so much.

UUID: c5d43e74-60bd-4e17-bfae-d14291fd9052 Scrub started: Wed Aug 14 05:36:11 2024 Status: finished Duration: 0:00:37 Total to scrub: 63.73GiB Rate: 1.72GiB/s Error summary: verify=712 csum=1068649 Corrected: 1069361 Uncorrectable: 0 Unverified: 0 Yeah it looks like this was what probably caused it.

Yeah it was one of my NVME drives. I will run it and post it here later.

Here you go and thanks. Sorry pretty new to tower-diagnostics-20240813-2132.zip. Well I have had it for a while without issue. This is my first that has got me scratching my head and frustrated. I know it will be something simple and I am just missing it

Here are the errors I get in the log about it when it fails. Aug 13 17:17:19 Tower root: mount: /var/lib/docker: wrong fs type, bad option, bad superblock on /dev/loop2, missing codepage or helper program, or other error. Aug 13 17:17:19 Tower root: dmesg(1) may have more information after failed mount system call. Aug 13 17:17:19 Tower root: mount error Aug 13 17:17:19 Tower kernel: BTRFS critical (device loop2): corrupt leaf: block=245661696 slot=0 extent bytenr=2749390848 len=12288 invalid generation, have 11383 expect (0, 9084] Aug 13 17:17:19 Tower kernel: BTRFS error (device loop2): read time tree block corruption detected on logical 245661696 mirror 1 Aug 13 17:17:19 Tower kernel: BTRFS critical (device loop2): corrupt leaf: block=245661696 slot=0 extent bytenr=2749390848 len=12288 invalid generation, have 11383 expect (0, 9084] Aug 13 17:17:19 Tower kernel: BTRFS error (device loop2): read time tree block corruption detected on logical 245661696 mirror 2