• Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become A Partner
  • Partner Policy & Program
  • Global Learning
  • Partner Sales Resources
  • Partner Business Management
  • Service Business
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
Home Support Resource Center Software Download Servers

HBA-LSI-9300-8i(2024/8/22)

Category-Component Type:

Driver-Storage

Version:

40.00.00.00

OS:

linux-CAS-E0783

    Description

  • Description
  • Installation steps
  • Publish Description
  • Problems Solved
  • New Functions
  • Historical Versions
  • Description

    The software is the driver of broadcom IT-IR storage controller card in the Linux operating system (OS).

  • Installation steps

    rpm drive package

    1.Log in to the server system using an account with administrator privileges. Upload the driver file to the system (using the /root path as an example);

    2.If installing the driver, execute rpm -ivh /root/<name>.rpm (Here <name> is rpm installation package file name).

    If updating the driver, execute rpm -Uvh /root/<name>.rpm (Here <name> is rpm installation package file name).

    3.After successful installation, restart the machine for the changes to take effect.

    4.Restart the OS and open the terminal to execute the cat /sys/module/mpt3sas/version command. If the driver version on the storage card is already the target version, the new driver is successfully installed.

    (Note: Before installing the driver in Suse OS, check whether the third-party module support option is enabled: check the /etc/modprobe.d/unsupported-modules configuration file to ensure that allow_ unsupported_ modules option is set to 1.)

    deb drive package

    1.Log in to the server system using an account with administrator privileges. Upload the driver file to the system (using the /root path as an example).

    2.Make sure the build-essential and dkms packages are installed on the target server OS. You can query the packages installed on the current OS by executing the dpkg -l command. If the installation is not complete, execute the apt-get command for installation as shown below (3).

    3.(Take Ubuntu as an example) configure the apt source (local or network) and enter the following commands:

    # sudo apt-get update

    # sudo apt-get install build-essential

    # sudo apt-get install dkms

    4.Execute the driver package installation command: # sudo dpkg -i /root/<name>.deb (Here <name> is deb installation package file name).

    5.After successful installation, restart the machine for the changes to take effect.

    6.Restart the OS and open the terminal to execute the cat /sys/module/mpt3sas/version command. If the driver version on the storage card is already the target version, the new driver is successfully installed.

    src.rpm driver source code package

    1.Log in to the server system with an account that has administrator privileges and upload the driver source code package "src.zip" to the system.

    2.Before performing the compilation, please ensure that the following packages are installed in the current environment. If any dependencies are missing, please install them yourself:

    RHEL/CentOS systems: gcc, rpm-build, make, kernel-devel, linux-headers

    SLES systems: gcc, rpm-build, make, kernel-devel, kernel-source, kernel-syms

    3.Open the terminal and and use the command to unzip src.zip: unzip src.zip.

    (Note: The common commands for decompressing a compressed package are as follows:

    tar -xvf file.tar

    tar -zxvf file.tgz

    tar -jxvf file.bz2

    unrar e file.rar

    unzip file.zip)

    4.After extraction, enter the directory. Three types of src.rpm are provided. Choose the appropriate type of src.rpm depending on the actual situation;

    kmod_srpm (RHEL based)

    kmp_srpm (SLES based)

    generic_srpm (The generic src.pm for RHEL/CentOS/SLES systems, it is recommended to prioritize using kmod and kmp.)

    5.Execute the command to install the source RPM: rpm -ivvh xxx.src.rpm

    6.Enter the directory that contains the driver SPEC file:

    RHEL/CentOS systems: /root/rpmbuild/RPMS/x86_64/

    SLES systems: /usr/src/packages/RPMS/x86_64/

    7.Execute the following command to compile and generate the driver rpm package:

    rpmbuild -ba <name> (Here <name> is SPEC file name)

    8.After successful compilation, the rpm driver package will be generated in the following directory:

    RHEL/CentOS systems: /root/rpmbuild/RPMS/x86_64/

    SLES systems: /usr/src/packages/RPMS/x86_64/

    (Note: Please save and archive the compiled driver package for future use.)

    9.If installing the driver, execute rpm -ivh xxx.x86_64.rpm

    If updating the driver, execute rpm -Uvh xxx.x86_64.rpm

    10.After successful installation, restart the machine for the changes to take effect;

    11.Restart and enter the system, open the terminal and execute the cat /sys/module/mpt3sas /version command to check and confirm that the driver version of the storage card is the target driver version, which means that the new driver is installed successfully.

    dd drive package

    1.If the disk cannot be recognized during the operating system installation process, you need to install the storage card driver first. Please follow the instructions below.

    2.Mount the dd.iso driver file corresponding to the operating system in KVM.

    3.When starting OS boot and entering the selection menu, press "e" to enter grub.

    4.RHEL/CentOS/ORCL Linux systems: Add "inst.dd" at the end of the linuxefi... line and press Ctrl+x to start booting.

    SLES systems: Add "dud=1" at the end of the linuxefi... line, and press Ctrl+x to start booting.

    5.Based on the prompt information, select the driver files to load as needed and continue the operation.

    6.The driver has been loaded successfully. You can now proceed with the normal operating system installation process on the target disk.

  • Publish Description

    Products

    H3C UniServer B5700 G3

    H3C UniServer B5700 G5

    H3C UniServer B5800 G3

    H3C UniServer B7800 G3

    H3C UniServer E3200 G3

    H3C UniServer R2700 G3

    H3C UniServer R2900 G3

    H3C UniServer R4300 G3

    H3C UniServer R4300 G5

    H3C UniServer R4330 G5

    H3C UniServer R4330 G5 H3

    H3C UniServer R4500 G3

    H3C UniServer R4700 G3

    H3C UniServer R4700 G5

    H3C UniServer R4700 G6

    H3C UniServer R4900 G3

    H3C UniServer R4900 G5

    H3C UniServer R4900 G6

    H3C UniServer R4900 G6 Ultra

    H3C UniServer R4930 G5

    H3C UniServer R4930 G5 H3

    H3C UniServer R4950 G5

    H3C UniServer R4950 G5 Milan

    H3C UniServer R4950 G5 Rome

    H3C UniServer R4950 G6

    H3C UniServer R5300 G3

    H3C UniServer R5300 G5

    H3C UniServer R5500 G5 AMD

    H3C UniServer R5500 G5 Intel

    H3C UniServer R6700 G3

    H3C UniServer R6900 G3

    H3C UniServer R8900 G3

    H3C UniServer R5350 G6

    H3C UniServer R6900 G5

    H3C UniServer R5500 G6 AMD

    H3C UniServer R5500 G6 Intel

    H3C UniServer R5300 G6

    H3C UniServer R5500LC G5 Intel

    H3C UniServer R5500 G5 HYGON

    H3C UniServer B5700 G6

    H3C UniServer R4900LE G6 Ultra

    H3C UniServer R4700LE G6

    H3C UniServer R4900LC G5

    H3C UniServer R4700LC G5

    H3C UniServer R4930LC G5 H3

    H3C UniServer R4300 G6

    H3C UniServer R4500 G6

    H3C UniServer R6700 G6

    H3C UniServer R6900 G6

    H3C UniServer R5330 G7

    H3C UniServer R5500 G7 Hygon

  • Problems Solved

    1.Increase the device scanning scsi command timeout event to 30 seconds to address the issue where certain SATA drives require more time to process the device scanning scsi command after adding PUIS (Power Up in Standby) functionality via HBA firmware, resulting in initialization and detection failures in the operating system.

    2.Fixed compilation errors occurring on kernel versions 5.12 to 5.15.

    3.Fixed the issue causing system crashes due to use-after-free triggered by executing rmmod and related operations. Refer to the following log information for more details:

    图片 1

  • New Functions

    1.None.

  • Version:40.00.00.00(2024/8/22)

    Upgrade recommendations

    Upgrade the driver,as a best practice.

    Problems Solved

    1.Increase the device scanning scsi command timeout event to 30 seconds to address the issue where certain SATA drives require more time to process the device scanning scsi command after adding PUIS (Power Up in Standby) functionality via HBA firmware, resulting in initialization and detection failures in the operating system.

    2.Fixed compilation errors occurring on kernel versions 5.12 to 5.15.

    3.Fixed the issue causing system crashes due to use-after-free triggered by executing rmmod and related operations. Refer to the following log information for more details:

    图片 1

    New Functions

    1.None.

新华三官网