Users Guide

Updating PERC 10 driver for existing Windows Server
2012 R2 and newer
NOTE: Close all applications on your system before you update the driver.
1. Insert the CD, DVD, or USB drive media containing the driver.
2. Select Start > Settings > Control Panel > System.
The System Properties screen is displayed.
NOTE: The path to System might vary depending on the operating system family.
3. Click the Hardware tab.
4. Click Device Manager.
The Device Manager screen is displayed.
NOTE: The path to Device Manager might vary depending on the operating system family.
5. Expand SCSI and RAID Controllers by double-clicking the entry or by clicking on the plus symbol next to SCSI and RAID
Controller.
NOTE: In Windows Server 2012 R2 and newer, the PERC 10 series of cards are listed under Storage Controllers.
6. Double-click the RAID controller for which you want to update the driver.
7. Click the Driver tab and click Update Driver.
The screen to update the device driver wizard is displayed.
8. Select Install from a list or specific location.
9. Click Next.
10. Follow the steps in the wizard and browse to the location of the driver files.
11. Select the INF file from the CD, DVD, or USB drive media.
12. Click Next and continue the installation steps in the wizard.
13. Click Finish to exit the wizard and reboot the system for the changes to take place.
NOTE:
Dell provides the Dell Update Package (DUP) to update drivers on systems running Windows Server 2012 R2 and
newer operating system. DUP is an executable application that updates drivers for specific devices. DUP supports
command line interface and silent execution. For more information, see https://www.dell.com/support.
Linux driver installation
NOTE: PERC 10 series of drivers support PERC 9 family controllers and do not require separate driver installations.
NOTE: The driver update disk (DUD) images are created only for those operating system releases in which the native (in-
box) driver is insufficient for installation. In the event that an operating system is being installed with a corresponding DUD
image, follow the instructions below.
NOTE: To view the complete list of boot loader options, see the installation guide of your operating system.
NOTE: If using out-of-box drivers with RHEL 7 and higher, a tainted kernel message will be displayed in the log. RedHat
does not provide a mechanism to sign external drivers for RHEL. This leads to kernel training whenever external drivers are
loaded in all the versions. Kernel messages can be
megaraid_sas:Loading out-of-tree module taints kernel
megaraid_sas:module verification failed: signature and/or required key missing-
tainting kernel
50 Driver installation