Areca SAS expander on 1880 bricked

amarton

n00b
Joined
Jun 7, 2016
Messages
6
I updated the SAS expander firmware on my ARC-1880ix via the serial interface and something went very wrong.

The RAID controller itself is fine, but the SAS expander seems bricked so the card doesn't see any drives.

I may have uploaded the wrong firmware. Areca's website has a "8026.zip" file for download from the 1880's support page, but the expander itself says (via serial) that it's an 8018, so I grabbed the download for the 8018 from Areca instead as it was much more recent, and also seemed a better fit.

Anyhow, "fdl code" and "fdl mfgb" as usual, reboot, and... nothing.

Well, this is what comes up through the serial interface when resetting the system, but it stops there and it won't respond to any input:

cubby.com

I was wondering if there's any way to fix this. Maybe recovery mode somehow? It's an older card but they're still pretty expensive and it was doing good work for me.
 
You'll probably have to contact Areca for help. There may be some sort of recovery procedure, but if not, you're probably looking at having it serviced by them or Tekram. I personally never bothered updating the expander on any of my cards due to how little documentation they had on them at the time.
 
Thanks for the response. I emailed them and they said it has to go in for repairs. It's out of warranty though, I don't know if anyone will bother to fix it. They asked for the serial number in order to determine the distributor, so not all hope is lost, yet.

I wanted to upgrade the expander firmware because I have an 8-bay enclosure with 2 minisas inputs, and if I externalized one of the controller's internal ports with a bracket, adapter and internal cable (so I can have 2 external ports on the Areca) the card would randomly fail disks attached to the internal port, but only those disks. I tried different adapters, cables, different internal ports, and the only common factor for failing disks was the use of the adapter/bracket. I'm fairly certain that the problems were due to the lower signal strength used on the internal ports. The expander firmware was from 2010, so even if it wouldn't allow for cable length adjustment in the firmware (some models do, some don't) I was hoping the 2016 code would do it some good.
 
Back
Top