Microsemi Adaptec / HP SmartHBA 2100-4i4e - converting HP to non-HP

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

alamone

New Member
Aug 17, 2022
1
3
3
I don't see much info about this card so I thought I'd start a thread. This is a nice 12G SAS HBA that is suitable for TrueNAS (detected natively), and has one internal 12G port and one external 12G port. Pair them with a cheap 12G SAS expander, like AEC-82885T ($75 on ebay), and you can access lots of internal or external storage.

Most of the ones out there on ebay are HP branded ones, which have a slightly different firmware that only accepts HP firmware. If you try to update with ARCCONF or Maxview, you will get a generic error or a security error. HP have stopped updating the firmware and I can't even find it on their website anymore.

The Microsemi / Adaptec firmware goes all the way up to 5.32 (August 11, 2022). There is a significant performance difference between the older and newer firmware. For example, doing a robocopy of 30G worth of data to a 6 drive RAID0 on a SAS expander, the older firmware (1.60) only managed 172 MB/sec, whereas the newer firmware (5.32) was able to get 382 MB/sec, which pretty much matched LSI 9207-8i performance. It was probably bottlenecked by the source (a 3 drive RAID0).

There's one seller on ebay (his username starts with "Hex") that is selling the regular, non-HP version. I purchased a few from him, but one of them was defunct. Since I have one of the HP branded ones, I tried swapping the chip on the backside of the card that has the firmware version sticker on it. It didn't seem to do anything and the firmware version remained the same (HP 1.60). On the second time, I tried swapping the memory chip on the front to the right of the heatsink (MX25U25635FMI-10G). This time, I got a message about NVRAM being restored on boot. Good sign. Then I tried using ARCCONF to update the firmware, and it worked. Unfortunately, I don't have any programmer that can read/write this particular memory chip, but this is one way to convert a HP version to a non-HP version. Probably an easier way would be some kind of software hack in ARCCONF so that it will cross-flash HP version to non-HP version, but I'm not that familiar with reverse engineering of x86 programs.

I attached some photos so you can tell the normal VS the HP version. The HP version will have a sticker on the front and back that says " / HPWS".
Ignore the missing chips on the non-HP version as I used them to convert my HP version to non-HP version.

IMG_2609.jpgIMG_2608.jpg
 

i386

Well-Known Member
Mar 18, 2016
4,941
1,949
113
37
Germany
Probably an easier way would be some kind of software hack in ARCCONF
Arcconf has a "force" parameter for firmware upgrades/downgrades. Wondering if that could be enough for "crossflashing" the firmware....
 

fd1

New Member
Jul 8, 2023
2
3
3
Does the HP version card can used on non-HP PC?
Yes, I've used it successfully in: 1) HPE rack servers, 2) self-built Xeon E-2300 TrueNAS SCALE server, and 3) Supermicro X10SDV.

For several years I've been looking for a way to break out of the firmware. Unfortunately, nothing has worked and I've been convinced that there is no documented way to do that.
 

faninx

New Member
Feb 28, 2020
24
8
3
Yes, I've used it successfully in: 1) HPE rack servers, 2) self-built Xeon E-2300 TrueNAS SCALE server, and 3) Supermicro X10SDV.

For several years I've been looking for a way to break out of the firmware. Unfortunately, nothing has worked and I've been convinced that there is no documented way to do that.
Yes, I have also tested it and it works. Previously, when I asked the question, it was because I inserted a card and it couldn't be used. Later, I confirmed that the card was broken.
 

Hellsfoul

New Member
Aug 31, 2026
2
0
1
Thanks for sharing the infos!
I have also fallen into the HP trap. I did not know, that there are such significant differences in firmware support. HP only supported the card for almost 2 years. Crazy! My brand new LTO-8 drive throws some errors, which is most likely caused by the ancient firmware on the card.
Here in Germany I cannot find any non branded versions on ebay or elsewhere. Maybe because the card is EOL now. I managed to hook up a CH341 programmer with 1,8V adapter and was able to extract the HP version firmware 1.98a (32MB) without desoldering it Link. I then compared it with the downloaded HP firmware 1.98a (~12MB).
As one can see on the filesize, it is not so easy to just flash the stock firmware to the chip, as much stuff is missing (e.g. bootloader, recovery partition, and so on). I could find the section on the dump, where the firmware resides. But arcconf alters some bits in the firmware, when flashing it to the chip. Maybe to get some checksums correct.
I am stuck now, and cannot procede, as I have no stock card available to read the flash chip from there. Also a stock 1.98 firmware could help, so I could compare it to the HP version to maybe find the vendor ids. But as the HP version does not support Raid5, this might not help anyways, as the firmware differs significantly. There are also one time register on the flash chip to store serial numbers. Not sure, if that saves the vendor id. In that case we would need to get a fresh flash chip and program that.
When reading the flashchip in circuit, it is important to pull up Pin3 to 1,8V, so it does not reset all the time.
 
Last edited:

RageBone

Active Member
Jul 11, 2017
712
187
43
How is aspm with those cards?

They seem to at least share the same PCB.
With some dumps it should be possible to figure out what goes where and make it happen with an external prpgrammer.

Are the eeprom sizes the same?
 

Hellsfoul

New Member
Aug 31, 2026
2
0
1
According to the support document, there are three memory chips on the board:
* Flash: MX25U25635FMI-10G (contains the firmware)
* MRAM: MR10Q010SC (most likely used just for logging)
* EEPROM: I don't know

I can't say anything about ASPM, as I only use it for my tape drive.