The reason that the devicename is bold, is that I’m running Windows Server and not Linux, VMware or another Linux build. The command for this : fio-attach /dev/fct0. I saw it had a problem attaching the fusion to the Operating System. Windows Server was rebooting and it took a very long time to boot (40 minutes instead of 5 seconds) :Īfter 35 minutes (approx) I saw the following error for a few minutes :Īgain a few minutes later I was able to login to the server and saw that following error : I restarted the server to activate the new firmware. It took about 20 minutes and as you can see in the screenshot everything went fine. So enough said, let’s upgrade the firmware : The card was running in minimal mode, this is common behavior and it means that you have to upgrade the firmware. In my case Windows Device Manager found the device after a rescan for drivers and I saw the fusionIO card. Carefully install the FusionIO card and start the server again. After this step turn off the server and unplug the power.

Then I downloaded the latest drivers (version 4.2.1 in my case) here. The first server took for ever to download and install them, so I decided to slipstream all the updates to a newly created Windows installation ISO (maybe another post). I did a clean install and afterwards I installed all the Windows updates. In my case I was dealing with 2 HP D元80H9 Performance servers running Windows Server 2008 R2 (for application purposes). I found the solution for these problems and decided to write a blogpost about it.įirst be sure to install the Operating System with alle the latest updates. Recently I installed 2 FusionIO drives for a client and ran into a few problems.

Hp fusion io driver rhel