Perc H310 Integrated Raid Controller Manual

New Dell Server H330 PERC not able to add SATA drives as RAID. By CheesyBread. This person is a verified professional. The SSDs are connected to the RAID controller not the motherboard controller, right? AFAIK there is no licensing for added functionality on Dell Perc controllers. That is an HP and IBM/Lenovo thing. Sep 4, 2013 - There is no way to control Patrol Reads if it is set to run automatically. You will have to switch to manual and schedule checks. From OMSA CLI: Use. Omreport storage controller to find controller Id. Set Patrol Read Mode to Manual: omconfig storage controller action=setpatrolreadmode controller=XX.

Dell PowerEdge PERC H310 Mini Mono RAID Controller 6Gb/s Dell Part Number(s): K09CJ, 0 K09CJ Dell PERC H310 RAID controller for select 12th generation Dell servers. Tested and pulled from working Dell PowerEdge servers. Specifications.

Low profile, fits in a dedicated storage slot. Works with SATA and SAS hard drives. 8-lane, PCI Express 2.0 compliant. Data transfer rates of up to 6Gb/s per port. RAID levels 0, 1, 5, 10, 50 Dell Documentation Compatible Servers Installed in a dedicated storage slot in the following systems:.

PowerEdge R320. PowerEdge R420. PowerEdge R520. PowerEdge R620. PowerEdge R720. PowerEdge R720xd.

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.

Perc H310 Integrated Raid Controller Manual

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.

Perc H310 Adapter

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.

Perc H310 Integrated Raid Controller Specs

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.

Dell Perc H310 Manual

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.