During a reinstallation of Windows with an active RAID array, the operating system may prompt for a storage controller driver. The driver must be installed before the software may be loaded. If the operating system Image does not include the correct RAID controller driver, Windows cannot see the hard drives to begin installation.
We recently did a conversion to vmware from a hyper-V host. After conversion and driver cleanup, we noticed that we were suffering from very slow read speeds on our new VM host. We were unsure if this was due to a bad conversion, etc, so we decided to create a new VM and test out the speeds. The results were the same.
There are two different arrays on our server. One is a raid 10 consisting of 4 10k SAS drives, the other is 4 SSDs specifically: ( All Products: Shop Hard Drives, SSDs, USBs, & Memory Cards Western Digital ) . The SSDs are in a RAID 5. Both arrays get around the same write speeds on the server, with the raid 10 being slower by a few mbps. Write-Back is enabled on the raid 5 array, verified this morning before production began.
Could this be a config issue with vmware? I have found many instances where updating 6.5 to latest should help the issue, but alas, we are already updated to update1 . I have also tried toggling the trim internally on the windows server. Any Ideas on what this could be? Thanks for your time.
I meant in Windows is it going to the page file instead of memory (usually when memory utilization is high or maxed). Swap is essentially ESXi paging. It is usually a result of memory contention (not enough memory).
Trim from windows is only going to do something if you have updated VMtools and VM hardware and can shrink the VM (it will be a negative performance impact but not huge as it should be throttled). TRIM/UNMAP will not work to the SSD drives as they are behind RAID and TRIM gets dropped.
I would agree with this, except that we are getting the same type of slow read speeds on a raid 10, the raid is made up of 4 300gb 10k SAS drives and Hyper-V performance was not this bad for writes. A side note, the firmware was updated to the latest version: Support Western Digital
The firmware on the controller is version 21.3.5-0002 Driver version : 6.910.18.00 ----- That is the correct firmware adapter, however when looking at Dell support page, there is a custom made ISO for vsphere 6.5u1 for that server. Should I be using these custom images? I used the image from vmware.com ------- =F4FY1
c80f0f1006