DDSS55KK CCoonnttrroolllleerr sshhoowwss SSuubbMMooddMMiiss LLoocckkddoowwnn eerrrroorr

SSuubbmmooddeell IIDD nnoott vvaalliidd,, ccooddee LL77

This is for DS5K with Firmware 07.84.xx. Should also work for other IBM DS Types

Prerequisites: Knownledge of how to connect and login to DS serial console. One working controller module in

the machine, or if both are showing the error then another working machine.

Login into serial console of faulty controller.

Type sysNvsramEdit

write down Board serial number

Example Output!

-> sysNvsramEdit ======== Kernel NVSRAM Configuration ======== 01) Serial Number SP01069057 02) World Wide Name 00 04) System Name LSI Logic 05) System Title LSI Logic RAID Controller 03) Password ******** 10) Console Baud Rate 9600 11) System Memory Size 0 12) Shared Memory Limit 0 13) Nvsram Log Size 0 14) Nvsram Script Size 0 1A) Nvsram H/W Log Size 0 41) Console Enabled 1 42) Caching Enabled 1 50) Memory Faults Enable 0 43) Diags Enabled 1 45) AutoLoad Enabled 1 46) PCI Scan Enabled 1 49) Ignore Alt Reset 0 66) Shell Enabled 0 60) Development Mode 0 61) Verbose Enabled 0 62) Debug Enabled 0 65) Ext Diags Enabled 0 67) Boot Menu Enabled 0 68) Continuous Diags 0 69) Mfg Diags 0 6A) All Monitor Options 0 6B) Monitor On Reboot 0 6C) Monitor On Exc 0 6D) Monitor On Watchdog 0 6F) Monitor On Break 0 18) Board Id Override 0 19) Host Id Override 0 63) VxW Debug Enabled 0 64) VxW Windview Enabled 0 15) VxW WindView BufSize 0 Enter selector code (Q to quit):

Login into shell of good controller.

Type sysNvsramEdit.

Copy output and paste into textfile for later use.

Type the following commands to get the output and copy it and paste into textfile for later use.

sysCfgShow 1

sysCfgShow 3

sysCfgShow 5

Example Output!

-> sysCfgShow 1 # Automatically generated MfgSec + 0 = 0x5d,0x00,0x00,0x00 MfgSec + 4 = 0x34,0x39,0x59,0x34,0x31,0x33,0x34,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00 value = 0 = 0x0 -> -> sysCfgShow 3 # ---==<< Board Identification >>==--- # # Installed: FEBRUARY 06, 2106 06:28 # # Automatically generated Board + 0 = 0x4c,0x53,0x49,0x20,0x4c,0x6f,0x67,0x69,0x63,0x20,0x52,0x41,0x49,0x44,0x20,0x43 Board + 16 = 0x6f,0x6e,0x74,0x72,0x6f,0x6c,0x6c,0x65,0x72,0x00,0x00,0x00,0x00,0x00,0x00,0x00 Board + 32 = 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00 Board + 48 = 0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00 Board + 80 = 0x53,0x50,0x30,0x31,0x30,0x36,0x39,0x30,0x35,0x37,0x20,0x20,0x20,0x20,0x20,0x20 Board + 64 = 0x4c,0x53,0x49,0x20,0x4c,0x6f,0x67,0x69,0x63,0x20,0x20,0x20,0x20,0x20,0x20,0x20 Board + 96 = 0x34,0x33,0x31,0x36,0x37,0x2d,0x30,0x30,0x20,0x20,0x20,0x20,0x20,0x20,0x20,0x20 Board + 112 = 0x31,0x35,0x33,0x38,0x33,0x2d,0x30,0x33,0x20,0x20,0x20,0x20,0x20,0x20,0x20,0x20 Board + 128 = 0x56,0x31,0x30,0x37,0x34,0x39,0x33,0x20,0x33,0x4c,0x54,0x48,0x30,0x31,0x20,0x20 Board + 144 = 0x30,0x33,0x2f,0x32,0x32,0x2f,0x31,0x30 Platform + 3 = 0x14 Platform + 4 = 0xffffffd2,0x26,0xffffffd6,0x59 Platform + 16 = 0xffffffd2,0x26,0xffffffd6,0x59 Platform + 41 = 0x14 value = 0 = 0x0 -> sysCfgShow 5 # ---==<< System Configuration >>==--- # # Installed: FEBRUARY 06, 2106 06:28 # # Automatically generated NonCfg + 0 = 0x49,0x42,0x4d,0x20,0x20,0x20,0x20,0x20 NonCfg + 8 = 0x31,0x38,0x31,0x38,0x20,0x20,0x20,0x20,0x20,0x20,0x46,0x41,0x53,0x74,0x54,0x20 NonCfg + 51 = 0x08,0x34 Operatn + 30 = 0x00 value = 5 = 0x5

Login into faulty controller.

Type the following:

sysNvsramUnlock

sysCfgInstallStream 1

<copy output of sysNvsramShow 1 into it> and hit <control>+<D> wait some seconds, it leaves

automatically.

sysCfgInstallStream 3

<copy output of sysNvsramShow 3 into it> and hit <control>+<D> wait some seconds, it leaves

automatically.

sysCfgInstallStream 5

<copy output of sysNvsramShow 5 into it> and hit <control>+<D> wait some seconds, it leaves

automatically.

Example:

Just select values from the output of sysCfgShow like this:

Paste after typing sysCfgInstallStream <number><enter>

Like this:

Type sysNvsramEdit

Correct the serialnumber with that one you have written down and compare and maybe correct

settings which should correspond with the setting of working controller.

Type the following:

sysNvsramLock

psvClearSodRebootLoopCounter

clearHardwareLockdown

lemClearLockdown

Now, after automatic reboot, the controller that showed the submodel mismatch error should work

again.

If both controllers show this error, the serialnumbers must be collected and written down and the

output of sysCfgShow (1, 3, 5) of another working machine should be collected for install with

sysCfgInstallStream.

Note:

This is a tricky procedure and therefore no guarantee of success is given here. I have done this

several times to repair our testequipment and it worked. Also some values then can be different as

original, like component partnumbers. Haven´t found out what exactly is stored into these

datafields.

Maybe the powercap has lost sufficient capacity to hold NVSRAM data and must be replaced before

entering the data values. It looks like below and must be ordered from various sellers.

Model is DALLAS DS9034PCX PowerCap™ with Crystal

PowerCap can be different or be a CMOS Coin Cell in other IBM DS

Types.

Experimental research by Marco Vernaglione. Rev2. 10-2017. marco.vernaglione@de.ibm.com