May 18May 18 I have spent over 800 dollars trying to fix this issue. And I think it might be software or config related?!?!?Timeline:Disk 11 20TB drive would just throw constant errors on every parity checkPurchased new 22TB drive ($500 dollars damn what happened to disk prices!)Replaced 20TB with new 22TB and got constant errors again.Put 20TB in my linux workstation and ran scan. Smart ran clean, file scan ran clean. All files still there and accessable. Random opened files and they all worked.Purchased new $200 IT MODE card LSI 9305-16i IT Mode PCIe SATA Expansion Card, 16-Port 12Gbps PCIe 3.0Still errors!Purchased brand new cables for all drivesNow getting errors on three different drives!Attached the latest diagPlease help! thebeast-diagnostics-20260518-0756.zip
May 18May 18 Community Expert Sounds like a cabling issue honestly. Bunch of your disks have UDMA CRC errors which indicates a faulty connection between he disk and the CPU. Double check all the cables are connected properly.Please reboot post new diagnostics. the syslog is 0bytes and the previous syslog is full of disk read errors on disk11 (presumably the old one)
May 18May 18 Community Expert Something to keep in mind, if you dont have active cooling on your HBA it could also be overheating, these things are meant for a server chassis with high airflow and if you are running one of these in a consumer case, it will need a dedicated fan for itself.
May 18May 18 Author 13 minutes ago, MowMdown said:Something to keep in mind, if you dont have active cooling on your HBA it could also be overheating, these things are meant for a server chassis with high airflow and if you are running one of these in a consumer case, it will need a dedicated fan for itself.I did not know that. But yes it's in a very large workstation case that holds 18 disks. I'll do what you suggested.
May 18May 18 Community Expert Your old Disk11 might actually still be healthy but due to the read errors (likely a faulty cable/HBA overheating) it was disabled by unraid. Hopefully you still have the disk and can mount it as an unassigned device and run an extended smart test on it to see what's up once you get your situation stabilized.
May 18May 18 Author 1 hour ago, MowMdown said:Your old Disk11 might actually still be healthy but due to the read errors (likely a faulty cable/HBA overheating) it was disabled by unraid. Hopefully you still have the disk and can mount it as an unassigned device and run an extended smart test on it to see what's up once you get your situation stabilized.Oh yeah it's completely okay. In fact I will add it back as a new disk. I'm looking at getting a raid case
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.