Storage MD3200i one controller not booting, can't access

Hi,

Have you tried to reseat the controller? You may also try removing the battery from the controller and resetting its configuration. 

Hi Joash,

Thank you so much for responding.

I removed the battery and called, see the logs below, it still continues the same way.
I've also tried switching between controller 1 and 2 (the position) but it did not work either.

Without the battery (I removed, plugged in and turned on)

Adding 13888 symbols for standalone.
Length: 0x13c Bytes
Version ver03.0A

Reset, Power-Up Diagnostics - Loop 1 of 1
3600 Processor DRAM
01 Data lines Passed
02 Address lines Passed
3300 NVSRAM
01 Data lines Passed
4410 Ethernet 82574 1
01 Register read Passed
02 Register address lines Passed
6D40 Bobcat
02 Flash Test Passed
3700 PLB SRAM
01 Data lines Passed
02 Address lines Passed
7000 SE iSCSI BE2 1
01 Register Read Test Passed
02 Register Address Lines Test Passed
03 Register Data Passed
Diagnostic Manager exited normally.

Current date: 12/01/17 time: 08:25:08

Send for Service Interface or baud rate change
12/01/17-16:29:32 (tRAID): NOTE: Set Powerup State
12/01/17-16:29:32 (tRAID): SOD Sequence is Normal, 0 on controller B
12/01/17-16:29:32 (tRAID): NOTE: Turning on tray summary fault LED
12/01/17-16:29:32 (tRAID): WARN: Error threshold exceeded: "Client_Corrupt_DB_D etected_On_Alt"
12/01/17-16:29:33 (tRAID): NOTE: Installed Protocols:
12/01/17-16:29:33 (tRAID): NOTE: Required Protocols:
12/01/17-16:29:33 (tRAID): NOTE: loading flash file: iSCSI
12/01/17-16:29:35 (tRAID): NOTE: DSM: Current revision 7
12/01/17-16:29:35 (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
12/01/17-16:29:35 (tRAID): NOTE: RCBBitmapManager total RPA size = 1778384896
12/01/17-16:29:35 (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBase = 0x 1
12/01/17-16:29:36 (tRAID): NOTE: loading flash file: MTLSEBET1G
*** Disabled FULL TRACE ***
12/01/17-16:29:36 (tRAID): WARN: MTLSE: before mtl_create_pool:IO task size: 0x 140
12/01/17-16:29:36 (tRAID): NOTE: init: ioc: 0, PLVersion: 11-075-20-00
12/01/17-16:29:37 (tRAID): WARN: MLM: Failed creating m_MelNvsramLock
12/01/17-16:29:37 (tRAID): WARN: MLM: Failed creating m_MelEventListLock
12/01/17-16:29:37 (tRAID): NOTE: CrushMemoryPoolMgr: platform and memory (CPU M emSize:2048), adjusted allocating size to 65536 for CStripes
12/01/17-16:29:39 (tRAID): SOD: Instantiation Phase Complete
12/01/17-16:29:38 (IOSched): NOTE: SAS Expander Added: expDevHandle:x11 enclHan dle:x2 numPhys:25 port:2 ioc:0 channel:1 numEntries:22
12/01/17-16:29:38 (tRAID): WARN: Error threshold exceeded: "Client_Corrupt_DB_D etected_On_Alt"
12/01/17-16:29:38 (tRAID): WARN: Client threshold Exceeded
12/01/17-16:29:38 (tRAID): WARN: sodLockdownCheck: sodSequence update: SuspLock down
12/01/17-16:29:38 (tRAID): WARN: No attempt made to open Inter-Controller Commu nication Channels 0-0
12/01/17-16:29:38 (tRAID): WARN: Error threshold exceeded: "Client_Corrupt_DB_D etected_On_Alt"
12/01/17-16:29:38 (tRAID): WARN: Client reported lockdown: "Client_Corrupt_DB_D etected_On_Alt"
12/01/17-16:29:38 (tRAID): NOTE: Flashing tray summary fault LED
12/01/17-16:29:38 (tRAID): WARN: Suspending Start-Of-Day Task
12/01/17-16:29:39 (tSasExpChk): NOTE: Local Expander Firmware Version: 00.00.80 .10
12/01/17-16:29:45 (tSasDiscCom): NOTE: SAS: Initial Discovery Complete Time: 36 seconds since last power on/reset, 10 seconds since sas instantiated

Press within 5 seconds: for Service Interface, for baud rate *** Expired

Try these steps:

1.       Insert controller which completes SodMain and allow start of day to complete, let’s call this controller-0 .

2.       Insert other controller and we should expect that controller to held in a reset state. We will call this controller-1.

3.       From controller 0 issued the shell command -> cmgrSetAltToOptimal and/or -> altResetRelease

4.       Establish a serial connection to controller-1 ASAP.

5.       Issue the command -> lemClearLockdown on controller-1

6.       Issue the command -> bdbmClearPrimaryDatabase on controller 1.

7.       This should complete SodMain on controller-1.

8.       From MDSM, go to “Find Reports” and then “Clear Recovery Mode” to make array optimal.

OK,

just a question,
The step:

I do this for MDS or Putty? because I only have Putty the option to enter and change the password.

For MDS I have the " Execute Script " option.

That's right ?
Sorry for all the doubts.

From MDSM

I did the procedure but returned no result.

Can you please look at the pictures and see if I'm actually doing it right?

On Controller1 (with problemass) the terminal still does not respond to commands.

See in the photo that even his network interface is disabled after about 2 minutes that has been connected.

similar issue here only both controllers give the same output - 

-=<###>=-
Instantiating /ram as rawFs, device = 0x1
Formatting /ram for DOSFS
Instantiating /ram as rawFs, device = 0x1
Formatting...Retrieved old volume params with %38 confidence:
Volume Parameters: FAT type: FAT32, sectors per cluster 0
0 FAT copies, 0 clusters, 0 sectors per FAT
Sectors reserved 0, hidden 0, FAT sectors 0
Root dir entries 0, sysId (null) , serial number 10000
Label:" " ...
Disk with 1024 sectors of 512 bytes will be formatted with:
Volume Parameters: FAT type: FAT12, sectors per cluster 1
2 FAT copies, 1010 clusters, 3 sectors per FAT
Sectors reserved 1, hidden 0, FAT sectors 6
Root dir entries 112, sysId VXDOS12 , serial number 10000
Label:" " ...
Instantiating /ram as rawFs, device = 0x1
OK.

RTC Error: Real-time clock device is not working

Adding 13888 symbols for standalone.

This is where it stops

similar issue here only both controllers give the same output - 

-=<###>=-
Instantiating /ram as rawFs, device = 0x1
Formatting /ram for DOSFS
Instantiating /ram as rawFs, device = 0x1
Formatting...Retrieved old volume params with %38 confidence:
Volume Parameters: FAT type: FAT32, sectors per cluster 0
0 FAT copies, 0 clusters, 0 sectors per FAT
Sectors reserved 0, hidden 0, FAT sectors 0
Root dir entries 0, sysId (null) , serial number 10000
Label:" " ...
Disk with 1024 sectors of 512 bytes will be formatted with:
Volume Parameters: FAT type: FAT12, sectors per cluster 1
2 FAT copies, 1010 clusters, 3 sectors per FAT
Sectors reserved 1, hidden 0, FAT sectors 6
Root dir entries 112, sysId VXDOS12 , serial number 10000
Label:" " ...
Instantiating /ram as rawFs, device = 0x1
OK.

RTC Error: Real-time clock device is not working

Adding 13888 symbols for standalone.

This is where it stops

Hello Urbanet,

Are you able to post the full output from your controller?  If we can see the full boot up of your controller, then we can see what is going on better.  To get the full boot up of the controller you will need to remove it from the system and wait about 1 minute then insert it.  Also, were you doing a firmware upgrade, or was a power loss that caused this issue?

Please let us know if you have any other questions.