Environment
Novell ZENworks 7.2 Linux Management - ZLM7.2
Novell ZENworks 7.3 Linux Management - ZLM7.3
Devices are connected with QLogic fiber channel adapter to a SAN
Novell ZENworks 7.3 Linux Management - ZLM7.3
Devices are connected with QLogic fiber channel adapter to a SAN
Situation
Not possible to image SAN hosted drives
The imaging Linux boot process shows error:
"...
qla2xxx 0000:07:05.0: Firmware image unavailable.
..."
The imaging Linux boot process shows error:
"...
qla2xxx 0000:07:05.0: Firmware image unavailable.
..."
Resolution
Please look at download.novell.com for "ZENworks Imaging Driver
Update". Updates since June 2009 do contain a SUSE Linux
Enterprise 11 or newer based Linux kernel.
It might be necessary to set the option "Prompt=YES" in the settings.txt configuration file to get the bash shell working during kernel initialization. More information about the settings.txt file is available in online documentation .
It might be necessary to set the option "Prompt=YES" in the settings.txt configuration file to get the bash shell working during kernel initialization. More information about the settings.txt file is available in online documentation .
Additional Information
The initial ZENworks Linux Management 7.3 release boots a SUSE
Linux Enterprise Server 10 SP2 based kernel for the imaging process
and it does not start a bash shell during the boot process from
initrd.
A bash shell is needed to be able to execute the script loading the required QLogic adapter firmware.
Future versions of ZENworks Linux Management 7.3 are moving to a SUSE Linux Enterprise Server 11 or newer based kernel version. A newer imaging kernel should load again a bash shell during the boot process, fixing this issue.
A bash shell is needed to be able to execute the script loading the required QLogic adapter firmware.
Future versions of ZENworks Linux Management 7.3 are moving to a SUSE Linux Enterprise Server 11 or newer based kernel version. A newer imaging kernel should load again a bash shell during the boot process, fixing this issue.