No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The BMR Recovery for a Client Mounted with a Hard Disk Array Fails and Error Message FATAL: Module qla2300 not found Is Displayed

Publication Date:  2015-07-29 Views:  83 Downloads:  0
Issue Description
A BH23 client runs the SUSE operating system. The client is connected to the hard disk array S2300 through an HBA. The model of the HBA is QLogic ISP2312-based 2 GB Fibre Channel. During the BMR for the client, error message FATAL: Module qla2300 not found is displayed. The BMR fails.

Handling Process
1.  Download and install the proper HBA driver.

NOTE:
You can obtain the HBA driver from http://support.qlogic.com/support/drivers_software.aspx.

a. Log in to a SUSE server that works properly as the user root.
b. Download the HBA driver. The qla2xxx-v8.02.23_4-dist.tgz file stored in /home is used as an example in this topic.
c. In /home, run the tar -xvzf qla2xxx-v8.02.23_4-dist.tgz command to decompress the driver file.

SUSE10:~ # cd /home/
SUSE10:/home # tar -xvzf qla2xxx-v8.02.23_4-dist.tgz
qlogic/
qlogic/drvrsetup
qlogic/libinstall
qlogic/libremove
qlogic/qla2xxx-src-v8.02.23.tar.gz
qlogic/qlapi-v4.00build25-rel.tgz
qlogic/README.qla2xxx
qlogic/RELEASE.qla2xxx


d. Read the README.qla2xxx file and install the HBA driver based on the instructions in the file.

2.  Load the driver to the SRT.

a. Copy the qla2xxx.ko file in /lib/modules/2.6.16.46-0.12-default/kernel/drivers/scsi/qla2xxx/ on the SUSE server to the HDP3500E.

NOTE:
Use the file transfer tool such as SSH Secure File Transfer Client to copy the file. In this topic, assume that the file is copied to /home on the HDP3500E.

b. Log in to the HDP3500E operating system interface as the user root, and the port number is 2222.
c. In /usr/openv/netbackup/bin, run the ./bmrsrtadm command to modify the SRT.

hdp3500e:/usr/openv/netbackup/bin # ./bmrsrtadm
Select one of the following options:
    1.  Create a new Shared Resource Tree.
    2.  Create a new CD image based Shared Resource Tree.
    3.  Copy an existing Shared Resource Tree to a new location.
    4.  Import a Shared Resource Tree.
    5.  Modify an existing Shared Resource Tree.
    6.  Delete an existing Shared Resource Tree.
    7.  List Shared Resource Trees available on this server.
    8.  Quit.


d. Enter 5 to modify the existing SRT. Press Enter to continue.

Enter your selection (1-8) [1] : 5

e. Enter the name of the created SRT, for example, NB71_SRT_SUSE10_SP3. Press Enter to continue.

Enter the name of an existing SRT : NB71_SRT_SUSE10_SP3
------------------------------------------------------------------------------
SRT name:      NB71_SRT_SUSE10_SP3
Location:      /export/srt/NB71_SRT_SUSE10_SP3
Description:   NB71_SRT_SUSE10_SP3
Exclusive use: (none)
------------------------------------------------------------------------------
You may make modifications to this SRT.
Select one of the following options:
    1.  Install Symantec NetBackup Maintenance Pack.
    2.  Install Veritas Volume Manager and Veritas File System.
    3.  Update Veritas Volume Manager and Veritas File System.
    4.  Install Veritas Security Services.
    5.  Install additional patches/drivers.
    6.  Change SRT description.
    7.  Change client exclusive use of this SRT.
    8.  Quit.


f. Enter 5 to install a patch or driver file on the SRT. Press Enter to continue.

Enter your selection (1-8) [8] : 5
The following additional packages are available to install:
     1. Install/update kernel drivers.
     2. Install a Linux Update/Service Pack.
     3. None of the above, leave unchanged.


g. Enter 1 to install the driver on the SRT. Press Enter to continue.

Enter your selection [3] : 1
The following options are available to install or update kernel drivers
in the boot filesystem image:
1.  Install a Linux driver update disk. (.img file)
2.  Install a driver module. (.o or .ko file)
3.  None of the above, leave unchanged.


h. Enter 2 to install the driver module. Press Enter to continue.

Enter your selection [3] : 2

i. Enter the path that stores the driver file, for example, /home/qla2xxx.ko. Press Enter to continue.

Enter path to driver module file (or none to return to menu) :/home/qla2xxx.ko
Driver module "/home/qla2xxx.ko" has been added to the boot filesystem image.
You may now choose to install or update additional drivers.
The following options are available:
1.  Install a Linux driver update disk. (.img file)
2.  Install a driver module. (.o file)
3.  None of the above, no further changes.


j. Enter 3 to stop the operations on the SRT. Press Enter to continue.

Enter your selection [3] : 3
Updating boot filesystem image contents ... ok.
You may make modifications to this SRT.
Select one of the following options:
    1.  Install Symantec NetBackup Maintenance Pack.
    2.  Install Veritas Volume Manager and Veritas File System.
    3.  Update Veritas Volume Manager and Veritas File System.
    4.  Install Veritas Security Services.
    5.  Install additional patches/drivers.
    6.  Change SRT description.
    7.  Change client exclusive use of this SRT.
    8.  Quit.


k. Enter 8 and press Enter to exit. The SRT modification is complete.

l. Restart the BMR. For details, see "Restoring a SUSE-Based Client System" in the OceanStor HDP3500E BMR Backup and Recovery Guide.
Root Cause
By default, the SRT does not provide the HBA driver. After the client is started through the SRT, the system detects that the HBA driver is unavailable during system detection and HBA activation. Therefore, the system displays Module qla2300 not found. Because the HBA driver is unavailable, the client fails to identify the connected hard disk array. Error message about incorrect hard disk information is displayed, which results in the BMR failure.

Suggestions
For clients that are mounted with hard disk arrays or other devices, obtain proper driver files and manually load the driver files to the SRT if the corresponding driver files are not loaded to the SRT during the BMR.

END