November 4, 200916 yr Author I'm thinking more and more it's the Syba (I checked and Peter was right as to the brand) PCI-e card that is the problem. I have all my disks connected to the MB up and running and no issues with the parity check. I've replaced cables and such as well. I don't think it's a PSU problem because I currently have had all disks spun up while I've been adding disks to the array and doing parity checks and no issues so far. I did flash the Syba PCI-e card to the non-raid version. The weird thing is my friend has the exact same Unraid set up (same MB, PCI-e card, HD's) and his works fine. He did not flash his PCI-e card to the non-raid version though. I ordered the Rosewill RC-218 from newegg and am RMA'ing the Syba card. We shall see.
November 5, 200916 yr Author Another update. So parity checks out fine when I have all but one of the disks connected to the PCI-e controller card. When I added that 2nd disk, I had the same issue with the parity sync errors. The disk itself seems fine according to the smart reports and I tested a couple of 4gb+ files and the md5 checksums are fine. So it shouldn't be the disk right? I'm doing another parity build/check with just that possibly bad disk and not the other one connected to the PCI-e card to see if it's a disk issue or if it's some issue that crops up when 2 disks are being used on the controller card. Does that make sense though? Can it be the fact that having 2 disks on the PCI-e card causes some issue when reading from both at the same time?? Regardless i ordered the Rosewill RC-218 from newegg as well. Bizarre!
November 5, 200916 yr Author Ok does seem the case when I have 2 active disks on the controller card is when I have the issue. It isn't specific to a disk or port. So I can only assume it's something with the controller card. Oh well, I have my Rosewill RC-218 ready to install anyway. Thanks to those who helped, hopefully some of this info is useful for others.
Archived
This topic is now archived and is closed to further replies.