Erasmus

I'm now pretty sure you're right and it was a power/connection issue. I don't know what the issue was... I had already tried re-seating all the cables and it hadn't helped, but I did it again and it's now happily rebuilding the parity drives so I guess we'll all good! Or rebooting just happened to fix the issue, I guess, but human error seems more likely. Thanks for the suggestions everyone!

Hi all! On my server both parity drives have simultaneously failed. Though it's possible it's hardware and both drives happened to fail at the same time, that seems unlikely to me, especially since they're the newest drives in the server... but it's always possible the server was physically jostled or something. I've tried removing them both from the array and re-adding them both individually and together, and swapping parity 1 and 2, but it always fails in the parity rebuild. It then does a read check, which passes. Both drives pass SMART tests, though honestly I don't know how meaningful that is. The rebuild seems to fail at a different point as well, sometimes getting several million writes on the parity drives, sometimes only a few thousand. Any clues as to how to diagnose this, or confirm the drives have actually failed would be appreciated. Thanks

Hi, This is probably a false positive, but thought I'd check, and even if it is you'd probably want to be aware that a common antivirus program has a problem with an Unraid page. On the docker settings page when I hit the SCRUB button, Bitdefender blocks the action and warns there's a web threat "Exploit.CommandInjection.Gen.123". I'm accessing Unraid 6.9.1 from the latest Firefox in Windows 10. Not sure if this is repeatable on other systems or against other Unraid servers... I can check from my other Windows PC later if it's helpful, but I only have one Unraid server to check against. Searching the forum shows that other buttons in the Unraid UI have historically been affected by this issue... ...which indicates there might be a problem here worth addressing.

Couldn't get it working on DOS, but found an old Win10 machine with a spare PCIe slot. One firmware and BIOS flash later it's all working perfectly. Thank you!

<diag deleted> Would an LSI firmware update be something I could do from unraid? I don't have another machine up and running with a spare PCIe slot

Hi all, I just got a new LSI SAS controller for my Unraid server, but when I plug my drives into it instead of the old controller they are recognised, but recognised as different drives with the same names. It insists that the right drives are the wrong drives. Is there a way to force Unraid to assume this is valid and boot up anyway? Thanks!