VSM6-VSM7 - Microcode upgrade fails with message --TDX Driver was Not Installed

Asset ID:	1-72-2350968.1
Update Date:	2018-01-21
Keywords:

Solution Type Problem Resolution Sure

Solution 2350968.1 : VSM6-VSM7 - Microcode upgrade fails with message --TDX Driver was Not Installed

Applies to:

StorageTek Virtual Storage Manager System 6 (VSM6) - Version All Versions to All Versions [Release All Releases]
StorageTek Virtual Storage Manager System 7 (VSM7) - Version 7.0.0 to 7.1.2 [Release 7.0]
Information in this document applies to any platform.

Symptoms

Disruptive application microcode upgrade stops with a rc=256 Execution Stopped on Failure during the command installBuildLocal.pl.

The error message (below) indicates The TDX DRIVER WAS NOT INSTALLED.

!!!! WARNING: The TDX DRIVER WAS NOT INSTALLED. !!!!
The TDX Driver failed to unload because a process has the driver open.
Make sure ALL the processes opening the TDX Driver are stopped.
You will need to rerun this TDX Driver install script again!
ERROR executing sudo -u root /opt/vsm/bin/installtdx_release: rc = 256
VSM6 code installation FAILED!!!
***************************************************
Dec 13 08:42:12 installBuildLocal.pl EXECUTION STOPPED ON FAILURE!!!!

***************************************************
Dec 13 08:42:12 Error executing ./installBuildLocal.pl -b 7.0.0.12.000 : rc = 256

***************************************************
Dec 13 08:42:12 disruptiveCodeLoad.pl EXECUTION STOPPED ON FAILURE!!!!

Dec 13 08:42:12 Logging at /home/vsmadm/download/disruptiveCodeLoad.log.0
***************************************************

Changes

VSM microcode upgrade

Cause

A TDX driver process did not shut down properly during the code load process.

Solution

Rerun the disruptive code load command (dcl) again.

Example:
dcl -v 7.0.0.12.000

This will reinitiate the VSM shutdown, re-distribute the code to both nodes, and re-install the code on both nodes.

If for any reason that the code fails a second time, delete all of the code files from directories listed in both nodes (see below).

VSM6:
Node 1: /home/vsmadm/download
Node 2: /home/vsmadm/

VSM7:
Node 1: /export/home/vsmadm/download
Node 2: /export/home/vsmadm/

--Remove any of the following files listed below from both nodes.

--Upload the two code build* files again to the download directory in Node 1 and start the app code upgrade again, from the beginning.

(Note: The files listed below are an example from 7.0.0.12.000 code. The actual code will depend on what was being loaded at the time of the failure.)

     vsmadm@vsmpriv1:~/download$ ls -l
     total 2281814
     -rw-r--r-- 1   vsmadm staff 91075670   Nov 29 2016   A_7.0.0.12.000.tar.gz
     -rw-r--r-- 1   vsmadm staff 657367814 Nov 29 2016 B_7.0.0.12.000.tar.gz
     -rwxr-xr-x 1 vsmadm staff 748533760 Nov 29 2016    build7.0.0.12.000.tar
     -rw-r--r-- 1   vsmadm staff 56               Nov 29 2016 build7.0.0.12.000.tar.md5sum
     -rwxr-xr-x 1 vsmadm staff 21453 Nov 29 2016   disruptiveCodeLoad.pl
     -rwxr-xr-x 1 vsmadm staff 5642           Nov 29 2016   downloadBuildLocal.pl
     -rwxr-xr-x 1 vsmadm staff 3615           Nov 29 2016   downloadBuildRemote.pl
     -rwxr-xr-x 1 vsmadm staff 15091 Nov 29 2016   installBuildLocal.pl
     -rwxr-xr-x 1 vsmadm staff 4120           Nov 29 2016   installBuildRemote.pl
     -rw-r--r-- 1   vsmadm staff 6                 Nov 29 2016 ndclLevel.dat
     -rwxr-xr-x 1 vsmadm staff 23624 Nov 29 2016 nondisruptiveCodeLoad.pl
     -rwxr-xr-x 1 vsmadm staff 6552           Nov 29 2016   replaceBuild.pl

Attachments

This solution has no attachment