Home » PERC H310 Adapter Use the links on this page to download the latest version of PERC H310 Adapter drivers. All drivers available for download have been scanned by antivirus program. Jan 7, 2018 - Installing Windows Drivers: Dell PERC Software Installation Guide. The only official version for PERC H310 for Dell Precision Driver for Windows. Graphics & Video Adapters • Modems & Network Adapters • Printers.
![]()
I did an update on a clients T330 Server from H310 to H710 last night. They have VMWare 5.0 installed with a single VM. Had to add the datastore back in but that was all fine. Improvements weren’t that great.
I enabled adaptive read caching and write back caching for the vdisk – performance after was slightly faster than prior, but I wouldn’t say moonbeams. They only have 2 mirrored SAS disks, so probably just an IOP limitation of the disk.
Still, I would have expected better. I ended up changing the D: and E: (data) drives of the virtual server from VMWare LSI Logic Parallel controller to PVSCSI, performance jumped up for those drives tenfold. I’ve left it on PVSCSI, even though they say PVSCSI isn’t recommended for DAS storage, its just too good not too use. I will need to do this as soon as my PERC H710 replacement controller arrives the first week of 2017. One question for you– did you or anyone else who has done this execute a consistency check after replacing the PERC controller? I have four 3TB drives running RAID 10. Consistency checks take a God-awful long time on my machine.
I am doing this on a Precision workstation, so I do not have the option of using OMSA. Dell only allows OMSA execution on a server. Don’t get me wrong– I do understand the importance of running a CC. I am actually running one right now with my PERC H310. It has been running now for about three days at only 48% complete. This is with it being run directly from the BIOS adapter config utility.
Based on my run time so far, a full CC may take seven complete days. I just replaced the PERC H310 with my new PERC H710. It was extremely easy to do. I did not even have to import an external configuration. The H710 did this automatically with the import option not even enabled in its BIOS. Right now the H710 is performing a patrol read, which the H310 was not able to do.
I will allow that to finish before starting a CC. I enabled write back and adaptive read ahead.
Right now Windows boots up faster with the new controller. The latest MegaRAID is showing that the patrol read for all four drives will be complete in 4 hours and 15 minutes. The only issue I have run into is that MegaRAID showed some error related to the H710’s firmware when Windows had initially started the first time. This same version of MegaRAID never showed this for the H310 controller.
However, I am still able to launch and use MegaRAID successfully. I am ignoring this error for now. I have to use MegaRAID, since I cannot use OMSA on Windows 10 Professional. So far, all is good! My CC through the H710 BIOS config utility completed against the same four hard drives in approximately six hours. This was significantly faster than the H310 could complete it. Finally, the error from MegaRAID I reported above happened only once after changing the PERC controller.
On my next reboot, I did not see the error again. It appears that the MegaRAID services were expecting the H310 controller on the next restart of Windows. Launching MegaRAID again appears to have resolved the issue, so there are probably settings saved locally related to the controller. This is MegaRAID version 16.05.04.
I'm trying to install Windows Server 2008 R2 64-bit for the first time in a Dell PowerEdge R220, using UEFI. At first the installation wouldn't see any disks. Then, I found this: I had never used the 'LifeCycle Controller', but after some experimenting I was able to make the installation see the one virtual disk that I created as RAID-0. However, now it gives me the message that 'Windows cannot be installed to this disk'. It says: Windows needs the driver for device PERC H310 Adapter Windows sees the disk but can't install to them, how do I work around that? I tried 'Load Driver' in the hopes that the driver in the server would be mapped somewhere, but it wasn't able to find it. I'm out of ideas here.:(.
I couldn't find a way to make the server itself tell the Windows installer how to see the disk, but by talking to @joeqwerty in the comments I ended up following this course, which worked:. Download the latest drivers from Dell: I did that from my product's support page, going on 'Drivers & Downloads', category 'Driver for OS Deployment'.
There was one file available, 'Dell OS Driver Pack, Version 14.11.02, A00' which was the same version already in the Lifecycle Controller. The direct link was:. unzip the exe. Inside it, there's a file 'mas021.zip' inside the folder 'payload'. I unzipped it too, and copied to an USB. During the installation, when it reaches the disk part, I selected to 'Load Driver', 'Browse', and went to the folder '48V2R', where windows found the driver for 'PERC H310 Adapter'. After that, I was able to partition the disk and proceed with the installation.
Still in the disk screen, the installer still had a warning saying that 'Windows cannot be installed', and as a reason it says the hardware might not be able to boot on this disk. However, the 'next' button is enabled and I was able to install windows. Also, after installing, I was able to reboot ok, so that warning was wrong. On the good side, I was able to install windows without any further errors. On the bad side, I don't have network: it doesn't even display the network cards. That means I should have drivers for that too, and who knows which other drivers are missing. Probably if I was able to install windows using the Lifecycle Controller properly in the way it was intended, I would now have all the drivers I need, but I couldn't find out how to do it.
Thanks @joeqwerty for suggesting that I update the OS drivers, which led me to this partial solution. P.S.: after I did that, I realized that I was using a Win2008R2 without SP1. I repeated the installation with a new disk with SP1, but the only difference was that I didn't get the message saying that the hardware might not be able to boot on this disk. All the other problems were the same, and the same workaround went fine. Hi I have encountered the same problem today, but it was on Windows Server 2012 R2 so I will explain how I solved it. Download the Latest Drivers for OS.
Unzip the exe with a tool such as 7zip. Inside it, there's also a file called 'mas021.zip' inside the folder 'payload'. Unzip this and copy only the unzipped files from here to an USB, I copied to the installer USB I was using. During the installation, when it reaches the disk part, I selected to 'Load Driver', 'Browse', and went to the folder payload 388D6 w2012r264.
Where it find something different (Not PERC H310 Adapter), there are two of them, I clicked on the first one. Right after this the hard drive was loaded right away and installations are the usual steps.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |