connect0r

Worked!!! Results: UUID: 82c4600e-84bf-4150-bec7-51f5cfca0556 Scrub started: Mon Mar 4 12:54:57 2024 Status: finished Duration: 0:01:14 Total to scrub: 429.28GiB Rate: 5.84GiB/s Error summary: no errors found Rebuilding my docker stacks now. no errors so far. 😭❤️ Thank you so much for your help @JorgeB Server was down for 2 weeks, had late nights with the server in pieces trying to isolate the hardware issues. None of the threads I found guided me to a solution and usually just lead to different errors. After countless parity checks, scrubs and reinstalls I was at a loss of what to do. I ripped the server apart, replaced most hardware and still nothing worked. In panic I nuked the cache, lost data, made some stupid mistakes while sleep deprived and not thinking straight. Thank you for the peace you have brought me.

Thanks for your help ❤️ Here are the results from the correcting scrub run: UUID: 82c4600e-84bf-4150-bec7-51f5cfca0556 Scrub started: Sat Mar 2 18:13:42 2024 Status: finished Duration: 0:01:47 Total to scrub: 650.91GiB Rate: 6.08GiB/s Error summary: csum=6 Corrected: 0 Uncorrectable: 6 Unverified: 0

maven-diagnostics-20240302-1147.zip Attached is my latest diagnostics file. I have a number of backdated ones as well if that is useful.

Hi all, I have read hundreds of threads trying to troubleshoot this issue, swapped out my motherboard, swapped out my power supply but still having issues. some background details: Server was stable for 6+ months, no major changes or updates were made. One day, there was a power outage, and in the following days all docker containers started throwing errors, mostly database errors in the form of I/O errors. After tons of troubleshooting, I ended up wiping everything and rebuilding from scratch. The problem was still there. I stumbled on this thread: where @JorgeB suggested change docker from macvlan to ipvlan when getting "write time tree block corruption" I have made the change to ipvlan yet the problems persist, now I'm not getting any more tree block corruptions. But critical "kernel: BTRFS error (device nvme0n1p1)" is still there. After running dozens of memtests for a few days, I realized one of the RAM modules was throwing errors. Once that module was out of the system, it passed extended 24h memtests. Now, I have formatted the cache drives in the bios, and rebuilt them as new cache disks in unraid. I am still getting the same "kernel: BTRFS error (device nvme0n1p1)" What can I do next?