Disconnected and flashed, unfortunately same result. The case is not hot at all, in fact the top has been open for the most part. Still blinking blue LED and says there are only 8 channels are available.Is it very hot in your case? Based on the symptoms it almost sounds like either the expander chip is overheating or just flaky. Expander chip is under the heatsink closest to the back of the board where the SFF-8087 connectors are. Assuming the expander chip is good and within temp limits, only other explanation for raid build issues is likely those WD20EARS drives, but could also be an issue with mixing/matching the EARS with the F4. I've only ever had problems with EARS drives on hardware raid controllers, though that was on the previous gen 1680 controllers, and plenty of other people report no troubles with EARS in hardware raid.
1. Disconnect SFF-8087 cables from card and re-flash all four firmware files via ethernet management port, then reboot card and make sure SES2 is set to "Enabled".
2. When your drives are able to be seen again then try creating a RAID5 or RAID6 with just the WD drives (F4 excluded), see if it finishes. Hopefully that will narrow whether mixing&matching is culprit, or EARS drives, again assuming its not expander.
The double beep is probably from the motherboard sending the PCIe reset signal twice on boot. It should be completely harmless, if somewhat anoying.I've tried the cold boot, power drain, several times, no success. Always greeted by double beep and blinking blue LED.
I bought the 4G card because Newegg had it for 15% off, which made it cheaper than the 1GB version. Yes this is mainly just a file server, but I also will be running a VM or two, and most importantly, I wanted ECC reliability throughout. I've used a mix of motherboard hardware and software RAID for a couple years now, and I have had every array fail at some point in time, so I figured it's time to buy the best. Of course it's my luck that the card is defective (and I agree it's the expander chip, makes the most sense as to why every drive would drop at once, and then reappear at once, and now it only sees 8 slots).*deleted* double post due to glitchy forum.
What's wrong with those numbers? 62 hours to build an array that large makes perfect sense, assuming they are 2TB disks. 65 MBps over the network is slow, but your metrics are right on, so it may be read performance limits from the source disk.
Anyone have issues trying to install mcraid archttp v1.83_81103? Specifically getting "javaw.exe has stopped working" when running the install.exe.
Interestingly I installed it fine before on my old build but since reformatting I can't seem to install this anymore.
EDIT - I installed it in safe mode and it works fine. Not sure why I was having issues with it though.
I expanded my raid6 array from 4tb to 6tb on my Areca 1880i. Why would windows 7 64 ultimate not reconize the full 6tb after the expansion in my computer? All drive sizes read correct in windows manager and in the mcaraid software there a way to correct?
I dont see the expand volume set. There is expand raid set,or modify volume set. I see 6tb fine in windows storage manager. I think it was mbr I cannot see that, where would I find info? My partion wizard software does not see that drive letter for that array for some reason. It wont let the space to be redistributed because it sees the correct amount in manager. The isssue is justin My computer area
I've gotten two timeout errors on my 1680 this week on two different disks. How can I test if the problem is the card or the disks? I've been running for the past year mostly with no problems, but in the past few months I've been getting timeout errors and I'm not sure if it's because my disks are dying or I'm just pushing the array too hard. Power management has been disabled on the array.