Solution if an error is reported if you install the multipathing software using a disk on a device running the Linux operating system

0

Solution if an error is reported if you install the multipathing software using a disk on a device running the Linux operating system:
Check whether the installation script of the multipathing software /home/linux/Packages contains an uppercase P. If it contains an uppercase P, an error is reported because the directory name of disks cannot contain uppercase letters. In this case, you need to copy the upgrade package from the disk to the local disk.

Other related questions:
Solution when the operation of installing the multipathing software is not activated
Solution when the operation of installing the multipathing software is not activated: FAQ-How Can I Handle the Problem that the Installed Multipathing Software Is not Activated

Solution if a message indicating unknown kernel is prompted during the installation of the multipathing software because the operating system version of the Linux host is different from the kernel version
Solution if a message indicating unknown kernel is prompted during the installation of the multipathing software because the operating system version of the Linux host is different from the kernel version: When you install the multipathing software, if the kernel version of the software package is different from the operating system version, a message indicating unknown kernel will be prompted. 1. Run cat cat /etc/xxx-release (xxx indicates the name of the Linux distribution, for example, Red Hat or SUSE) to check the operating system version. # cat /etc/redhat-release Red Hat Enterprise Linux AS release 4 (Nahant Update 7) 2. Run uname -a to query the kernel version of the Linux operating system. # uname -a Linux ctucipjrlx007 2.6.9-78.ELsmp #1 SMP Sat Nov 26 08:44:12 CST 2011 i686 i686 i386 GNU/Linux 3. Check whether the operating system version is different from the kernel version. 4. If the operating system version is different from the kernel version, change the operating system version in /etc/xxx-release to the version in table 1 and reinstall the multipathing software.

Method used to modify the timeout period for the Emulex HBA card on a device running the Linux operating system
Method used to modify the timeout period for the Emulex HBA card on a device running the Linux operating system: 1. How can I modify the timeout period for the Emulex HBA card on a device running the Linux operating system? Description: On a standard dual-switch network, Emulex HBA cards are used on the server. If one of the switchboards (switches) is faulty, the I/O suspension time before failover is about 30s. After fault locating, it can be determined that the I/O suspension is caused by the long timeout period of the HBA card. In some application scenarios, the I/O suspension time needs to be modified. 2. Solution Check the value of the lpfc_nodev_tmo parameter in the configuration file. In RHEL and Asianux, the configuration file is /etc/modprobe.conf. In SUSE, the configuration file is /etc/modprobe.conf.local. a. Check whether the UltraPath software has been installed on the server. If not, install the UltraPath software and proceed to the following steps: b. Modify the value of the lpfc_nodev_tmo parameter (add this parameter if it does not exist). For example, options lpfc lpfc_nodev_tmo=n (n is an integer and it is recommended that the value of n range from 10 to 60.) c. Run upUpdate to update the UltraPath image file. d. Restart the server to validate the modification.

Solution if an error is reported when the user unmounts the storage file system on the Linux host side
Solution if an error is reported when the user unmounts the storage file system on the Linux host side: a. A busy message is displayed when the user unmounts the storage file system from the Linux host side. If a busy message is displayed when the user unmounts the storage file system from the Linux host side, it indicates that a process is using this file. To view the process, perform the following operations: Enter the following command on the host: fuser -vm /dev/sdc (or /home/hms/data/c). Format: fuser -vm driver letters (or the file system path) After checking the process that occupies the file, check the process usage. After the process can be stopped, stop the process and then unmount the file system. To stop a process, run the following command: kill -9 process ID. If you do not need to check which process is using the file (consequences of stopping processes are not considered), run the following command to stop all processes that use the file: Enter the following command on the host: fuser -km /dev/sdc (or /home/hms/data/c) Format: fuser -km drive letters (or the file system path) Note: Before stopping the process, ensure that stopping the process does not affect the normal running of the host and services. If the preceding operations cannot stop the process, hard reset the host. Before resetting the host, remove the fiber from the host to the storage, or delete the mapping from the storage to the host. b. A timeout message is displayed when the user unmounts the storage file system from the Linux host side. A mtab~ file is generated from the default mounting file mtab each time the umount command is being executed. The mtab~ file is a flag file used for mutual exclusion and will be deleted after umount is executed. If the umount operation is not completed, the file will not be deleted. During the execution of umount, it is considered that the previous umount is still running. The mtab~ file will be deleted only after umount is executed. Therefore, the umount operation times out and exits. Manually delete the mtab~ file and then run umount. Note: The default mounting directory file of the host may vary with the operating system. Therefore, you need to confirm with the operating system administrator.

Using a one-click operating system installation disk as a standard installation disk
The following uses the IBM one-click operating system installation disk as an example to describe how to use a one-click operating system installation disk as a standard installation disk. The procedure is as follows: Ensure that the RAID configuration is complete. Insert the SUSE Linux 11 SP1 one-click installation CD-ROM and restart the server. Wait about 5 minutes. The system restarts, and the SUSE Linux Enterprise Server window is displayed. Use the arrow keys to select the installation mode (install linux for 7 hard disks for example). Press the Backspace key to delete the contents after Boot Options. Press Enter. The subsequent installation procedure is the same as that for installing the operating system using a standard operating system installation disk.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top