md3200i controller WARN: Controller entering SODReboot lockdown state..

Hello Goddy_D,

This is a new feature to aid in the recovery of the controller.When a condition is present that prevents SOD (Start Of Day) from completing 5 times, the controller enters a SOD reboot lockdown state to prevent further continuous reboots.  What you need to do is to run the following command from serial shell: lemClearLockdown

Once that is done the error message will be cleared.  Once the lockdown state is triggered, the condition is persistent to that controller until the provided clear command is used - it will not clear with a manual reboot or power cycle and the sysWipe function is not available prior to SOD.  

Please let us know if you have any other questions.

Hi Sam L,

I used  putty to connect to  the md, please educate me on this:

1.When login and type S it does not initialize setup as dell manual said.At this point do I just  go ahead with the command line you gave?

2.Hope it would not affect my data.

Thanks for your support

I am going to send you an email on how to login to the shell.

I just sent you the message a few seconds ago

Hi Sam ,

Please can you send to this address: Email id removed per privacy policy>

Hi Sam,

My mail server is on the MD ,so please to this address please: Email id removed per privacy policy>

I replyed to  your Email message.

Thanks Sam,am good

Hello, Goddy_D, Sam.

I have similar issue (en.community.dell.com/.../20427849.aspx) and cannot log into the console shell (after pressing S nothing happens). Could you please help me?

Sam could you help me out with this same problem via email?

my email id is<ADMIN NOTE: Email id removed as per privacy policy>

Hello kshitij92,

I sent you an email using the email that is listed in your profile.  If you can get me one of the logs then I can review it & let you know what I find.  

Please let us know if you have any other questions.

I have the same problem, serial output below. Could you also email me the solution? I don't think I have shell access currently, as i tried to issue lemClearLockdown and it just printed the text.

-=<###>=-

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 f10000

 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 f10000

 Label:"           " ...

RTC Error:  Real-time clock device is not working

OK.

Adding 14577 symbols for standalone.

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 Lines Test                                    Passed

3900 Real-Time Clock

    01 RT Clock Tick                                               Passed

Diagnostic Manager exited normally.

02/26/15-14:30:50 (tSystem): ERROR: FPGA FW is out of date

"Rhone03 rev17" currently in use

"Rhone03 rev20" available for update using fpgaUpdate(" ");

       base address 0xf7f7fc00

02/26/15-14:30:54 (tNetCfgInit): NOTE:  eth0: LinkUp event

02/26/15-14:30:54 (tNetCfgInit): NOTE:  Network Ready

Current date: 02/26/15  time: 14:31:15

Send for Service Interface or baud rate change

02/26/15-14:31:14 (tRAID): NOTE:  Set Powerup State

02/26/15-14:31:15 (tRAID): SOD Sequence is Normal, 0 on controller A

02/26/15-14:31:15 (tRAID): NOTE:  loading flash file: ECTDell

02/26/15-14:31:15 (tRAID): NOTE:  unloading flash file: ECTDell

02/26/15-14:31:15 (tRAID): NOTE:  Turning on tray summary fault LED

02/26/15-14:31:15 (tRAID): NOTE:  SODRebootLoop- Limit:5 Cnt:5

02/26/15-14:31:15 (tRAID): NOTE:  Flashing tray summary fault LED

02/26/15-14:31:15 (tRAID): WARN:  Controller entering SODReboot lockdown state.

For clarity, this happened after a firmware upgrade using MDSM to the latest version 8 FW and NVSRAM. One controller survived, the other one is currently marked up as "Removed" on MDSM.

Hi. I have the same problem, please send me a mail too.

Hi Sam,

Would you also be able to offer me some assistance in clearing this issue.  I was able to observer these two issues.

03/10/15-19:00:41 (tRAID): SOD Sequence is Normal, 0 on controller B

03/10/15-19:00:41 (tRAID): NOTE:  Turning on tray summary fault LED

03/10/15-19:00:41 (tRAID): NOTE:  SODRebootLoop- Limit:5 Cnt:14

03/10/15-19:00:41 (tRAID): NOTE:  Flashing tray summary fault LED

03/10/15-19:00:41 (tRAID): WARN:  Controller entering SODReboot lockdown state...

06/06/14-20:29:02 (tRAID): WARN:  Error threshold exceeded: "Client_Corrupt_DB_Detected_On_Alt"

Not sure if both are related.