![]() See this page on instructions on how to upgrade. This can be fixed however by upgrading ESXi and uninstalling/reinstall the driver again if you run into this issue. Also, the RAID won't actually be used then. This is bad if you have data on the RAID drives already you can't access them then. Then you will still be able to access your hard drives but only through VMWare's own AHCI/SATA driver, and will ignore the RAID configuration. I've noticed if you have an older version, that uninstalling/replacing the driver may make the HP VSA driver fail to load. I've used them myself and it works perfectly, though.īefore you continue check that you have ESXi 6.5 Build 5310538. Files you'll needįirst of all, I take no responsibility for any damage or problems if you follow these instructions. Whatever the problem is, below is how to solve it. But with a different driver I get normal performance and with an up-to-date driver I get shit performance. Let me just say that, yes, I know these are entry-level servers. both servers run controller: HP ProLiant b120i SmartArray.I don't know if this issue exists in other configurations but what I've seen so far it affects these configurations 88), I was able to get around 170MB/s write performance. 101 or 102 or so I believe) and just installed the old driver (version. When I uninstalled the new HPVSA driver (version. For example one of my HP MicroServer gen8 servers has 2x8TB WD RED disks in RAID-1, and gave me around 30MB/s performance at best. This is a situation I can reproduce on multiple servers with various disk configurations. All I do know is that when I replace it with an older driver, my server's disk performance is fine again. I have no idea why as I haven't dug into it in detail. Turns out that for some reason the HPVSA driver for ESXi has some issues. ![]() And totally unexpected, because with ESXi 5 and 5.5, it worked just fine, staying a steady 110MB/s all the way through. ![]() I'm on a gigabit network and copying files from my Windows computer to a Linux Samba instance, and it started out at 110MB/s, then tanked to 25MB/s after half a minute. Imagine getting only about 25 megabytes per second of write speed on it. ![]() For some reason the disk performance was suddenly just atrocious. It had always been working fine until I started using ESXi 6 and 6.5 on it. Even though this post is fairly dated, I will leave this post online just in case anyone still has an HP ProLiant M元10e or MicroServer Gen8 server with terrible disk performance. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |