SOFTPAQ NUMBER: N/A PART NUMBER: N/A FILE NAME: cpq_cciss_RedHat72-2.4.30-1.i386.rpm TITLE: Compaq Linux driver for the Smart Array 5i, 5300 Series for Red Hat Linux 7.2 VERSION: 2.4.30-1 LANGUAGE: English CATEGORY: Storage Controllers DIVISIONS: N/A PRODUCTS AFFECTED: ProLiant DL760 All Models ProLiant DL580 (667-1000MHz) ProLiant DL380 G2 (1133MHz+), (667-1000MHz) ProLiant DL380 Packaged Cluster G2 (1266MHz) ProLiant DL360 G2 (1400MHz+), (667-1266MHz) ProLiant DL320 All Models ProLiant ML750 All Models ProLiant ML570 (667-1000MHz) ProLiant ML530 (667-1000MHz) ProLiant ML370 G2 (1133MHz+), (667-1000MHz) ProLiant ML350 G2 (1133MHz+), (700MHz -1GHz) ProLiant ML330e All Models ProLiant ML330 G2 (1000MHz+), (667-999MHz) ProLiant 8500 All Models ProLiant 8000 All Models OPERATING SYSTEM: Red Hat Linux 7.2 SYSTEM CONFIGURATION: All shipping configurations PREREQUISITES: N/A EFFECTIVE DATE: March 29, 2002 ELECTRONIC DISTRIBUTION ALLOWED: Yes SOFTPAQ UTILITY VERSION: N/A SUPERSEDES: cpq_cciss_RedHat72-2.4.24-1 DESCRIPTION: This RPM Package Manager (RPM) is used to provide binary driver modules that have been pre-built for Red Hat Linux 7.2 to enable Compaq Smart Array 53xx and Smart Array 5i controllers. This RPM provides a customer friendly approach to install a pre-built binary drivers. Enhancements: * Fixed panic problem on doing fdisk on /dev/cciss/c0d0 with no physical disks * Added "engage scsi" code for tape support * Fixed problem with tape drives beyond the 16th physical LUN not appearing. * Fixed races and problems related to driver's logical volume usage counters in the area of (de)registering disks. (symptoms of problem were ACU could not register/deregister logical volumes sometimes.) * Added support for Smart Array 5312 adapter. * Added support for SCSI tape drives and medium changers. * Added support for dynamically adding and removing logical volumes; * Added ioctl for rescanning a disk where READ_CAPACITY failed during init, (Used in certain failover configurations). * Misc changes to geometry related ioctls. * Added GETLUNID and GETLUNINFO ioctls * Flush battery-backed cache on driver unload. * Reserve and release i/o memory ranges * Replaced use of schedule_timeout() loop with completions * Replaced use of obsolete suser() with capable() A changelog for the Smart Array 5300 Series drivers is available at: ftp://ftp.compaq.com/pub/products/drivers/linux/released/cciss/cciss_history.htm IMPORTANT: Additional instructions may be viewed: rpm -q -i -p cpq_cciss_RedHat72-2.4.30-1.rpm | more Please read this section before proceeding. This RPM will install binary drivers that will only work with the default Red Hat Linux 7.2 kernel version and configuration that they have been built for. Earlier or later versions of Red Hat Linux are not supported. Special actions are required if you have modified the default kernel configuration that Red Hat ships for their Red Hat 7.2 product. If you have modified the default kernel configuration you will need to rebuild the kernel to use the updated drivers after installing the RPM with the --noscripts option. For directions to patch the existing driver and rebuild your kernel please refer to the Red Hat documentation. The driver patches will be available in a gzipped tar file in the /opt/compaq/storage_drivers directory after installing the RPM with the --noscripts option. The CCISS driver RPM will not install if it detects that your configuration is different than the Red Hat 7.2 default Server configuration. This driver RPM will not install if the loopback device is not configured but the initrd image is requested since the loopback device is required to create the initrd image. If this RPM is used to update a CCISS driver.o module that has a version number less than 2.4.6 please be aware of the following changes: Because of changes to the PCI API used in the 2.4 kernel, this RPM will replace the existing driver with a driver that changes the way the controllers are numbered after the PCI bus is scanned. If you have multiple CCISS storage controllers installed and you have the combination of a Smart Array 5300 and either a Smart Array 5i or a Smart Array 532, when the server reboots you could possibly see the message "Cannot mount root". The section titled: Work-around for Controller Number Change, provides detailed instructions how to correct the problem. HOW TO USE: 1. Login as the system administrator (root), download the RPM to a directory on your hard drive and change to that directory. 2. Prior to installing (or un-installing) the RPM, if your system is LILO-based enter the following: # export SUPPRESSGRUB=y Likewise if your system is GRUB-based, enter the following: # export SUPPRESSLILO=y If the above command was not entered, on installing the RPM, the installation is initiated but will not be successfully completed (an error status is printed to the screen). The user then needs to remove the RPM (see step 8 below), enter the SUPPRESSGRUB (or SUPPRESSLILO) command and then re-initiate the installation process. 3. To install the driver type: # rpm -ivh cpq_cciss_RedHat72-2.4.30-1.i386.rpm You can expect to see a message similar to: # rpm -ivh cpq_cciss_RedHat72-2.4.30-1.i386.rpm Preparing... ################################################################################################### [100%] ################################################################################################### [100%] Attempting dry run first... ./install --drivers cciss --lilo --initrd --noskip --dry-run ---> THIS IS A DRY RUN <--- LILO_CONF = /etc/lilo.conf Kernel image is vmlinuz-2.4.7-10smp mkdir -p /usr/src/COMPAQ/driver_backup mkdir -p /usr/src/COMPAQ/driver_backup//./lib/modules/2.4.7-10/kernel/drivers/block cp -p /./lib/modules/2.4.7-10/kernel/drivers/block/cciss.o /usr/src/COMPAQ/driver_backup//./lib/modules/2.4.7-10/kernel/drivers/block/cciss.o Installing cciss for 2.4.7-10 kernel... cp -p ./lib/modules/2.4.7-10/kernel/drivers/block/cciss.o /./lib/modules/2.4.7-10/kernel/drivers/block/cciss.o done mkdir -p /usr/src/COMPAQ/driver_backup//./lib/modules/2.4.7-10smp/kernel/drivers/block cp -p /./lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o /usr/src/COMPAQ/driver_backup//./lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o Installing cciss for 2.4.7-10smp kernel... cp -p ./lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o /./lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o done /sbin/mkinitrd /boot/cpq-initrd-2.4.7-10smp.img 2.4.7-10smp Modifying /tmp/lilofile.1293, adding cpq-2.4.7-10 Testing lilo configuration (/sbin/lilo -t). We always run /sbin/lilo -t, even for --dry-run /sbin/lilo -t -C /etc/lilo.conf > /dev/null 2>&1 Modifying default lilo entry /sbin/lilo -t -C /etc/lilo.conf > /dev/null 2>&1 lilo configuration appears OK. /sbin/lilo -t succeeded, so we would normally really run lilo at this point if it were not a dry-run The following patch would have been made to /etc/lilo.conf --- /etc/lilo.conf Wed Apr 3 13:31:17 2002 +++ /tmp/lilofile.1293 Wed Apr 3 13:37:16 2002 @@ -1,6 +1,6 @@ prompt timeout=50 -default=linux +default=cpq-2.4.7-10 # (previously, default=linux) boot=/dev/sda map=/boot/map install=/boot/boot.b @@ -18,3 +18,10 @@ initrd=/boot/initrd-2.4.7-10.img read-only root=/dev/sda2 + +# The following entry was added by Compaq HBA install script +image=/boot/vmlinuz-2.4.7-10smp +label=cpq-2.4.7-10 +initrd=/boot/cpq-initrd-2.4.7-10smp.img +read-only +root=/dev/sda2 ---> THIS WAS A DRY RUN <--- Dry run succeeded, installing for real... ./install --drivers cciss --lilo --initrd --noskip LILO_CONF = /etc/lilo.conf Kernel image is vmlinuz-2.4.7-10smp Installing cciss for 2.4.7-10 kernel...done Installing cciss for 2.4.7-10smp kernel...done /sbin/mkinitrd /boot/cpq-initrd-2.4.7-10smp.img 2.4.7-10smp Modifying /etc/lilo.conf, adding cpq-2.4.7-10 Testing lilo configuration (/sbin/lilo -t). Modifying default lilo entry /sbin/lilo -t -C /etc/lilo.conf > /dev/null 2>&1 lilo configuration appears OK. Added linux Added linux-up Added cpq-2.4.7-10 * # Setup Is Now Complete. Please REBOOT Your Computer NOW!! NOTE: If the installation fails or if you see any warning or error messages, STOP, do NOT reboot the computer. The driver will not be operational and you must uninstall the driver by typing the following command: # rpm -e cpq_cciss_RedHat72-2.4.30-1 The removal of the RPM restores the original cciss.o module, and builds a new initrd image with the previous driver object module (if any) and adds yet another grub or lilo entry. You can then boot using this newest lilo or grub entry, (provided the building of the new initrd image goes well), or your original lilo or grub entry. The successful installation will replace the driver that shipped with Red Hat 7.2 with the 2.4.30 version of the driver, create a new Initial RAM Disk Image (initrd) that contains the 2.4.30 version of the driver and modify /etc/lilo.conf (or /boot/grub/menu.lst) to allow the Linux Loader, lilo (or grub) to boot using the new ramdisk image. The installation of this RPM modifies the following files: /etc/lilo.conf (or /boot/grub/menu.lst) /etc/lilo.conf.bak-* (backup files) /boot/grub/menu.lst.bak-* (backup files) /boot/cpq-initrd-*.img-* (initrd images) if you have multiple processors installed in your server expect: /lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o if you have a single processor server expect: /lib/modules/2.4.7-10/kernel/drivers/block/cciss.o if your server uses the Red Hat Enterprise kernel expect: /lib/modules/2.4.7-10enterprise/kernel/drivers/block/cciss.o Backups of your previous files will be kept in the /usr/src/COMPAQ/driver_backup directory. The driver version can be verified by typing: # strings /lib/modules/2.4.7-10/kernel/drivers/block/cciss.o | grep Compaq Expect output similar to: %s: Compaq %s Controller Compaq CISS Driver (v 2.4.30) 4. The driver will be inserted in the Initial RAM Disk Image (initrd) and is automatically loaded every time the server boots, provided it is listed in /etc/modules.conf, which, normally, it is. 5. To load the module use the insmod command. Type: # insmod cciss Expect the following output if you have Symmetric Multi-Processing support enabled: Using /lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o Expect the following output if you have a single processor server: Using /lib/modules/2.4.7-10/kernel/drivers/block/cciss.o Expect the following output if your server is using the Red Hat Enterprise kernel: Using /lib/modules/2.4.7-10enterprise/kernel/drivers/block/cciss.o NOTE: You will experience error messages if the Smart Array controller is not installed. Please ensure that the hardware is installed properly. NOTE: If the hardware is properly installed and you experience error messages loading the modules, remove the entire RPM by typing: # rpm -e cpq_cciss_RedHat72-2.4.30-1 The removal of the RPM will restore the driver modules, and rebuild and initrd image for the running kernel and create appropriate entries in /etc/lilo.conf (or /boot/grub/menu.lst). Additionally you should still be able to boot using the previous entries still in /etc/lilo.conf or /boot/grub/menu.lst, provided the driver modules are restored, or were (and thus still are) in the initrd image. 6. To check whether the driver is loaded properly, type: # lsmod Expect to see the module name cciss displayed 7. If you attempt to install the RPM on an unsupported system, you will get an error message. The driver will not be operational and must be uninstalled by typing the following command: # rpm -e cpq_ciss_RedHat72-2.4.30-1 8. To remove the RPM package use the following command: # rpm -e cpq_cciss_RedHat72-2.4.30-1 Expect to see output similar to: # rpm -e cpq_cciss_RedHat72-2.4.30-1 Attempting dry run first... ---> THIS IS A DRY RUN <--- LILO_CONF = /etc/lilo.conf Kernel image is vmlinuz-2.4.7-10smp mkdir -p /usr/src/COMPAQ/driver_backup Uninstalling /lib/modules/2.4.7-10/kernel/drivers/block/cciss.o mv /lib/modules/2.4.7-10/kernel/drivers/block/cciss.o /tmp/cciss.o.old.1758 Restoring previous cciss.o from backup. cp -f /usr/src/COMPAQ/driver_backup//lib/modules/2.4.7-10/kernel/drivers/block/cciss.o /lib/modules/2.4.7-10/kernel/drivers/block/cciss.o rm -f /usr/src/COMPAQ/driver_backup//lib/modules/2.4.7-10/kernel/drivers/block/cciss.o rm -f /tmp/cciss.o.old.1758 Uninstalling /lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o mv /lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o /tmp/cciss.o.old.1758 Restoring previous cciss.o from backup. cp -f /usr/src/COMPAQ/driver_backup//lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o /lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o rm -f /usr/src/COMPAQ/driver_backup//lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o rm -f /tmp/cciss.o.old.1758 /sbin/mkinitrd /boot/cpq-initrd-2.4.7-10smp.img-0 2.4.7-10smp Modifying /tmp/lilofile.1758, adding cpq-2.4.7-10-0 Testing lilo configuration (/sbin/lilo -t). We always run /sbin/lilo -t, even for --dry-run /sbin/lilo -t -C /etc/lilo.conf > /dev/null 2>&1 Modifying default lilo entry /sbin/lilo -t -C /etc/lilo.conf > /dev/null 2>&1 lilo configuration appears OK. /sbin/lilo -t succeeded, so we would normally really run lilo at this point if it were not a dry-run The following patch would have been made to /etc/lilo.conf --- /etc/lilo.conf Wed Apr 3 13:37:19 2002 +++ /tmp/lilofile.1758 Wed Apr 3 13:39:08 2002 @@ -1,6 +1,6 @@ prompt timeout=50 -default=cpq-2.4.7-10 # (previously, default=linux) +default=cpq-2.4.7-10-0 # (previously, default=cpq-2.4.7-10) boot=/dev/sda map=/boot/map install=/boot/boot.b @@ -25,3 +25,10 @@ initrd=/boot/cpq-initrd-2.4.7-10smp.img read-only root=/dev/sda2 + +# The following entry was added by Compaq HBA install script +image=/boot/vmlinuz-2.4.7-10smp +label=cpq-2.4.7-10-0 +initrd=/boot/cpq-initrd-2.4.7-10smp.img-0 +read-only +root=/dev/sda2 ---> THIS WAS A DRY RUN <--- ./uninstall --drivers cciss --lilo --initrd --noskip --dry-run Dry run succeeded, uninstalling for real... ./uninstall --drivers cciss --lilo --initrd --noskip LILO_CONF = /etc/lilo.conf Kernel image is vmlinuz-2.4.7-10smp Uninstalling /lib/modules/2.4.7-10/kernel/drivers/block/cciss.o Restoring previous cciss.o from backup. Uninstalling /lib/modules/2.4.7-10smp/kernel/drivers/block/cciss.o Restoring previous cciss.o from backup. /sbin/mkinitrd /boot/cpq-initrd-2.4.7-10smp.img-0 2.4.7-10smp Modifying /etc/lilo.conf, adding cpq-2.4.7-10-0 Testing lilo configuration (/sbin/lilo -t). Modifying default lilo entry /sbin/lilo -t -C /etc/lilo.conf > /dev/null 2>&1 lilo configuration appears OK. Added linux Added linux-up Added cpq-2.4.7-10 Added cpq-2.4.7-10-0 * To use SCSI tape drives with CCISS Smart Array controller 1. Add the following into /etc/init.d/cciss_tape -----8<------8<------8<-----8<------ for x in /proc/driver/cciss/* do echo "engage scsi" > $x done -----8<------8<------8<-----8<------ 2. Create a symbolic link, e.g: chmod +x /etc/init.d/cciss_tape cd /etc/rc.d ln -s S90cciss_tape ../init.d/cciss_tape 3. The script will be run automatically at boot time, or you can run it manually for the first time. 4. The tape drive(s) should then be accessible in the usual manner, e.g.: through /dev/st0, /dev/st1, etc. Work-around for Controller Number Change Your controller number MAY change after upgrading from an older version of the CCISS driver to version 2.4.5 or higher. This re-numbering is caused because version 2.4.5 of the CCISS driver started using the new PCI API provided by the 2.4 kernel. The previous PCI API provided an interface that scanned for CISS controllers by matching the specified PCI vendor/device ID. As the controllers were found for that particular vendor/device ID pair, the controller numbers were assigned. The new API now scans for ALL CISS controller at the same time. As a result, all CISS controllers are now ordered in PCI bus scan order. This is only a problem if the server has Smart Array 5300 installed and either Smart Array 5i or Smart Array 532. For example, if the server had Smart Array 5300, Smart Array 5i, and Smart Array 532 installed in the server, using the older PCI API, the driver would search for the SA5300 by specifying its PCI Vendor/Device ID and assign controller number values based on PCI bus scan order. It would then search for Smart Array 5i and Smart Array 532, they have the same PCI Vendor/Device ID, and assign controller numbers values as it found the controllers. The PCI API routines provided With the 2.4 kernel search for all PCI CCISS controllers in PCI bus scan order and assign the controller number as the controllers are found. Another example, if the server had a Smart Array 5i and a Smart Array 5300 installed, the controller order would look like this using the previous version of the CCISS driver: Smart Array 5i would be /dev/cciss/c1xxxx Smart Array 5300 would be /dev/cciss/c0xxxx After upgrading to CCISS driver version 2.4.5 or higher: Smart Array 5i would be /dev/cciss/c0xxxx Smart Array 5300 would be /dev/cciss/c1xxxx This will cause your kernel to report that it is unable to mount root because it is looking for root attached to the Smart Array 5i on /dev/cciss/c1xxxx, but it is now /dev/cciss/c0xxxx. To get your system to correctly boot again, you must modify the filesystem table file /etc/fstab and the lilo config file /etc/lilo.conf and re-run the Linux install loader, /sbin/lilo. To get the system to boot: When you get the system panic "Unable to Mount root..." two lines above it you will see a message like: VFS: Cannot open root device 6913 In this example 69 means c1 68 = c0 # controller 0 69 = c1 # controller 1 6A = c2 # controller 2 6B = c3 # controller 3 6C = c4 # controller 4 ... the 13 means d1p3 01 = d0p1 # disk 0, partition 1 02 = d0p2 # disk 0, partition 2 ... 10 = d1p0 # disk 1, partition 0 11 = d1p1 # disk 1, partition 1 12 = d1p2 # disk 1, partition 2 13 = d1p3 # disk 1, partition 3 ... 1) when lilo boots do to get lilo text mode 2) hit to get a listing of the available kernels 3) type root= In this example we want to use c0 so the new-major number is 68, our minor is still 13 and the new-kernel is cpq-2.4.7-10 cpq-2.4.7-10 root=6813 4) Checking of the filesystems will fail (because the fstab entries are wrong), you will then be prompted to "Give root password for maintenance mode". Enter your root password and hit 5) The / filesystem is now mounted read-only, to change the mount flags to make the filesystem writeable type: # mount -o remount rw / 6) Edit /etc/fstab and change the mount points entries. Our example /etc/fstab file contains the following text: LABEL=/ / ext2 defaults 1 1 LABEL=/home /home ext2 defaults 1 2 /dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,owner 0 0 none /proc devpts gid=5,mode=620 0 0 /dev/cciss/c1d1p3 swap swap defaults 0 0 Using this example, change the /dev/cciss/c1d1p3 entry to /dev/cciss/c0d1p3. Make sure you search the whole list.. swap is usually at the bottom. 7) Mount all the other filesystems that are listed in your corrected /etc/fstab file with the mountall option to mount. # mount -a 8) Edit the lilo configuration file /etc/lilo.conf to specify the device that contains the master boot record and the device that should be mounted as root. The options are labled "boot=" and "root=" respectively. Our example lilo.conf file contains the following text: boot=/dev/cciss/c1d0 map=/boot/map prompt message=/boot/message default=linux image=/boot/vmlinuz-2.4.7-10 label=linux read-only root=/dev/cciss/c1d1p3 image=/boot/fdfs label=cpq-2.4.7-10 read-only root=/dev/cciss/c1d1p3 Specify the correct boot device by changing the boot=/dev/cciss/c1d0 entry to boot=/dev/cciss/c0d0. In this example the new kernel has the label "cpq-2.4.7-10". Locate the root= entry line in this section and change the root=/dev/cciss/c1d1p3 entry to root=/dev/cciss/c0d1p3. 9) run /sbin/lilo. You should not get any errors out of lilo. If you do, you have missed the new kernel entry. # lilo Added linux * Added cpq-2.4.7-10 10) Reboot and your system will now come up normally on the new kernel. Feedback -------- To provide kernel/driver development feedback send email to Cciss-discuss@lists.sourceforge.net For support for Compaq Smart Array controllers, please send email to support@compaq.com. Copyright 2002, Compaq Computer Corporation. All rights reserved. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies