Piljekks

Thank you - where do you see that setting?

What is the most interesting is I can browse Disk 1,2 and 4 and see files and folders but if I try to browse disk 3 I get the below:

Thanks for your help - I tried this across all 4 disks (no option to do this on Parity) and all 4 came up with some degree of corruption. I ran the fix across all 4, started the array out of maintenance mode and within seconds there are read errors

Server console is showing a lot of metadata I/O errors but not understanding what this means.

Hi all, Since upgrading to Unraid 7.0.0 my array appears to be broken - it started with a small number (<100) disk errors across all 4 drives and docker being completely unavailable including browsing SMB shares. I've replaced the HBA and all cables with a brand new controller in the hope that it was a HBA issue - with the new HBA, the issue remains. The parity drive would drop off completely and refused to come back. I've stopped the array, started it in safe mode and run a parity check - this completed with 0 errors as it had to do a full parity rebuild after resetting the config. I've rebooted and done another parity check (not in safe mode) and now there are MILLIONS of errors. I'll attach logs of all the different points (with parity drive, without pairty, and the millions of errors after the parity rebuild) Wondering if collectively someone can identify what is going on? millions of errors-pilunraid-diagnostics-20250117-0749.zip WITHOUTPARITYpilunraid-diagnostics-20250115-2106.zip WITHParity-pilunraid-diagnostics-20250115-2028.zip