LSI Logic PERC 3/x, 4/x, 4e/x, CERC ATA 100 Driver
Restart required AUTO INSTALLED This file was automatically installed as part of a recent update. If you are experiencing any issues, you can manually download and reinstall.This package provides the LSI Logic PERC 3/SC, 4/DC, 4/SC, CERC ATA 100 Driver and is supported on the Enterprise Servers and Powervault models that are running the following Operating System: Red Hat Enterprise Linux 2.1 and Red Hat Enterprise Linux 3.
Recommended
Find the best download for your system
Please enter your product details to view the latest driver information for your systemSearch support
Enter your Dell Service Tag or model
Want to look up your product? Enter a product identifier. Show me how
This driver is not compatible
This driver is not applicable for the selected product. Choose another product to re-enter your product details for this driver or visit the Product Support page to view all drivers for a different product.
Sign in to Windows as an admin to use automatic scan. If your're already signed in as an admin and seeing this message, please reboot. Your system is managed by your IT admin and features might be limited.
Find more updates. Use SupportAssist to find all the latest driver updates for your device.
Fixes & Enhancements
Fixes
- Fixed an issue to resolve random deletion errors.
- Fixed tape drive issue: for any Direct CDB command to a physical device, including tape, timeout value set by the driver was 10 minutes. With this value, most commands will return within the timeout. However, for those commands like ERASE or FORMAT, it takes more than an hour depending on capacity of the device and the command could be terminated before it completes. To address this issue, the 'timeout' field in the DCDB command will have NO TIMEOUT value as its timeout on DCDB command.
- Fixed prevention for kernel panic for Test Unit Ready (TUR) commands when installing from SCSI CDROMs.
Enhancements
- Enhanced timeout value to prevent kernel watchdog timer expiration.
Read More- Fixed an issue to resolve random deletion errors.
- Fixed tape drive issue: for any Direct CDB command to a physical device, including tape, timeout value set by the driver was 10 minutes. With this value, most commands will return within the timeout. However, for those commands like ERASE or FORMAT, it takes more than an hour depending on capacity of the device and the command could be terminated before it completes. To address this issue, the 'timeout' field in the DCDB command will have NO TIMEOUT value as its timeout on DCDB command.
- Fixed prevention for kernel panic for Test Unit Ready (TUR) commands when installing from SCSI CDROMs.
Enhancements
- Enhanced timeout value to prevent kernel watchdog timer expiration.
Version
2.10.10.1, A11
Release date
17 Jan 2014
Download Type
Driver
Category
SCSI RAID
Importance
RecommendedDell Technologies recommends applying this update during your next scheduled update cycle. The update contains changes to maintain overall system health. It ensures that the system software remains current and compatible with other system modules (firmware, BIOS, drivers, and software) and may include other new features.
Available formats View Important Information
File Format: One or more self extracting disk images inside of a self extracting zip
File Name: perc-2.10.10.1-A11.exe
File Size: 643.26 KB
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
This file contains a compressed (or zipped) set of files. Download the file to a folder on your hard drive, then double-click it to unzip the set of files. Follow the instructions to complete the installation.
To ensure the integrity of your download, please verify the checksum value.
MD5:
Not available
SHA1:
Not available
SHA-256:
Not available
File Format: External release notes
File Name: perc-2.10.10.1-A11.txt
File Size: 28.35 KB
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
This file format contains plain text which can be viewed with a standard text editor.
To ensure the integrity of your download, please verify the checksum value.
MD5:
Not available
SHA1:
Not available
SHA-256:
Not available
File Format: A tar file for software installation
File Name: perc-2.10.10.1-A11.tar.gz
File Size: 542.39 KB
This is a large file. Depending on your connection speed, it may take some time to download.
Format Description:
This file is an archive of compressed files for software installation.
To ensure the integrity of your download, please verify the checksum value.
MD5:
Not available
SHA1:
Not available
SHA-256:
Not available
By downloading, you accept the terms of the Dell Software License Agreement.
Supported Operating Systems
Red Hat® Ent Linux 2.1
Red Hat® Ent Linux 3
Looking for a different OS? View the list of Dell supported operating systems
Applies to
�
PERC 4/DC
PERC 4/SC
PERC3/SC
Installation instructions
Install Instructions
Download the .tgz file
Installing the Driver for the PERC
============
Updating the Driver Using RPM After OS is Installed
=============
This procedure installs the megaraid2 and DKMS RPM packages contained in this
Dell driver release. If the system is not running one of the supported kernels
listed in Section 2.1, kernel source must be installed in order for the driver
module to be installed for the running kernel.
1. Create the driver diskette by following the steps in Section 2.1.
2. Type the following commands from a Linux command shell:
mount /dev/fd0 /mnt/floppy
cd /mnt/floppy
source install.sh
NOTE: The floppy drive in the system may not be enumerated as fd0. For example,
a USB floppy drive may have a device name of /dev/sda. Determine the
device name for the floppy drive and substitute fd0 with the proper device
name in the command above.
3. Reboot the system for the changes to take effect.
NOTE: The megaraid2 module is only installed for the kernel currently running.
Updating the Driver Using DKMS After OS is Installed or Updated
===========================
NOTE: The DKMS package is necessary to install the driver in the following scenarios:
1. When multiple kernel versions co-exist on the same system and the user wants
to install the driver for the non-running kernel versions (assuming the
driver RPM package does not contain such driver modules).
2. If the kernel is updated after installing the megaraid2 driver and the user
wants to install the megaraid2 driver for the updated kernel.
To build the megaraid2 driver for any kernel, the following prerequisite packages must
be installed:
- The megaraid2 RPM included in this package (see Section 2.2.1)
- Kernel source for the kernel in question
- Kernel building tools such as gcc
1. Add module source into the DKMS tree.
# dkms add -m megaraid2 -v
Where is the version of the megaraid2 driver.
E.g. v2.10.10.1
2. Build driver module for the kernel to be installed.
# dkms build -m megaraid2 -v
Where is the version of the megaraid2 driver.
E.g. v2.10.10.1
Where is the kernel version.
E.g. 2.4.21-4.EL
Repeat the DKMS build command for each kernel version to be packaged.
NOTE: If a kernel version is not specified on command line, the module will
only be built for the current running kernel.
3. Install the driver module.
# dkms install -m megaraid2 -v -k
Where is the version of the megaraid2 driver.
E.g. v2.10.10.1
Where is the kernel version.
E.g. 2.4.21-4.EL
Note: If kernel version is not specified on command line, the module will
only be installed for the current running kernel.
4. Check DKMS status.
# dkms status
Should show the module is installed in the specific kernel version.
5. Reboot into that kernel for the changes to load the driver module.
Refer to the DKMS man page for more information.
# man dkms
Reboot will be required
Download the .tgz file
Installing the Driver for the PERC
============
Updating the Driver Using RPM After OS is Installed
=============
This procedure installs the megaraid2 and DKMS RPM packages contained in this
Dell driver release. If the system is not running one of the supported kernels
listed in Section 2.1, kernel source must be installed in order for the driver
module to be installed for the running kernel.
1. Create the driver diskette by following the steps in Section 2.1.
2. Type the following commands from a Linux command shell:
mount /dev/fd0 /mnt/floppy
cd /mnt/floppy
source install.sh
NOTE: The floppy drive in the system may not be enumerated as fd0. For example,
a USB floppy drive may have a device name of /dev/sda. Determine the
device name for the floppy drive and substitute fd0 with the proper device
name in the command above.
3. Reboot the system for the changes to take effect.
NOTE: The megaraid2 module is only installed for the kernel currently running.
Updating the Driver Using DKMS After OS is Installed or Updated
===========================
NOTE: The DKMS package is necessary to install the driver in the following scenarios:
1. When multiple kernel versions co-exist on the same system and the user wants
to install the driver for the non-running kernel versions (assuming the
driver RPM package does not contain such driver modules).
2. If the kernel is updated after installing the megaraid2 driver and the user
wants to install the megaraid2 driver for the updated kernel.
To build the megaraid2 driver for any kernel, the following prerequisite packages must
be installed:
- The megaraid2 RPM included in this package (see Section 2.2.1)
- Kernel source for the kernel in question
- Kernel building tools such as gcc
1. Add module source into the DKMS tree.
# dkms add -m megaraid2 -v
Where
E.g. v2.10.10.1
2. Build driver module for the kernel to be installed.
# dkms build -m megaraid2 -v
Where
E.g. v2.10.10.1
Where
E.g. 2.4.21-4.EL
Repeat the DKMS build command for each kernel version to be packaged.
NOTE: If a kernel version is not specified on command line, the module will
only be built for the current running kernel.
3. Install the driver module.
# dkms install -m megaraid2 -v
Where
E.g. v2.10.10.1
Where
E.g. 2.4.21-4.EL
Note: If kernel version is not specified on command line, the module will
only be installed for the current running kernel.
4. Check DKMS status.
# dkms status
Should show the module is installed in the specific kernel version.
5. Reboot into that kernel for the changes to load the driver module.
Refer to the DKMS man page for more information.
# man dkms
Reboot will be required
Drivers help and tutorials
For more downloads go to the Drivers and downloads. For help on using the information on this page, please visit Driver Help and Tutorials.