lockdown571

I just installed this SATA controller: https://www.amazon.com/gp/product/B07ST9CPND/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1. Ran a parity check without a single error. This is the fourth SATA controller I have tried. Hopefully the fourth time is the charm.

I am fairly certain at this point the Jmicron controller is the issue. None of the hard drives seem to like that port. I had an issue with a hard drive that wasn't using the controller, but that seemed to have resolved itself. I think that just confused the picture. Pretty annoying since this is the third PCI-E SATA controller I have tried. I suppose the only other possibility is a problem with the PCI-E bus itself. I was using a PCI-E riser cable and tried switching that out, but that didn't fix it. This is the last time a build a server that depends on SATA expansion cards.

Thanks, I will give that a try. Unfortunately this will be the third SATA controller I've been through in a short amount of time 😠

Still getting read errors on multiple drives (the problem seems to jump from one drive to the other). I took the drives completely out of the case (to bypass the backplane on the HDD cage), used fresh Sata cables, made sure the cables were firmly connected without bends, and used different SATA power connectors on the PSU. Still getting UDMA CRC error counts. I do seem to be getting just a few now though instead of thousands. It doesn't seem to be a matter of if I get these errors but how many. So annoying. By the time I replace various parts on the server to troubleshoot the issue further, I might as well have just built an entirely new server.

Thanks, I will check the connections again. Unfortunately in the middle of me troubleshooting the mover decided to start. It's taking forever, I think because I'm getting thousands of read errors.

I have now replaced the hard drive, the SATA cable, the SATA controller, and the power supply, and I am still getting udma crc error counts. What a headache. Any more ideas before I nuke the server from orbit? 😠 tower-diagnostics-20200815-0854.zip

So I was getting some read errors on a hard drive, and it finally went into an error state in Unraid. I figured the drive was bad, so I replaced it. Rebuilt the array without issues. A few hours later though, that new hard drive went into an error state. Is the new hard drive really a dud? I replaced the SATA cable, same thing. I also just replaced this SATA controller a few months ago. Any ideas before I send the new hard drive back? syslog.txt ST8000DM004-2CX188_ZCT2P6ND-20200802-1041.txt tower-diagnostics-20200802-0936.zip

Updated my mobo BIOS and nothing. The card doesn't even post. I swear every time I update my Unraid server version I end up with a totally bizarre chain of issues. I wish I would learn my lesson. I will try a JMB582 card.

Tried the ASM1061 card. Of course that did not work. Would have been way too easy. My mobo won't detect it at all. Any other SATA controllers you recommend?

Thanks! Something like this? Also, glancing through some other forum posts, I should be able to shutdown the server, replaced the SATA controller, and reboot? Anything else I need to do to the array before replacing the sata controller?

Did three consecutive parity checks (all had errors). No reboot in between. Grabbed the diags after each check (1536 is the most recent). Really appreciate the help! tower-diagnostics-20200412-1950.zip tower-diagnostics-20200413-2137.zip tower-diagnostics-20200415-1536.zip

Those were from last week, but from what I remember those were back to back without rebooting the server. I will run it a couple more times consecutively and post the new diags later this week.

Here are two. Running another now. tower-diagnostics-20200406-1853.zip tower-diagnostics-20200409-1635.zip

I assume memtest just runs indefinitely? I've been running it over 24 hours now (13 passes) without any errors. What should be my next step in troubleshooting?

Thanks! I will try that out and report back.