MD3600f Controller entering SODReboot lockdown state

Hello @JQWang,

 

What is the firmware version? Did you update it recently? Or there was any hardware change? If so, please describe what happened previous to the error.

 

Normally, a lock down is to prevent any data loss it locks down the controller to ensure that there is no further corruption. Can you share some screenshots of the error from the MDSM?

 

This error also happend after a few retries to boot and reboots. It just stop rebooting and shows “lockdown” with this kind of message in the serial shell. In that case is correct using lemClearLockdown command to clear the lockdown state. But this will not fix the initial problem that started the controller rebooting in the first place. 

 

There are a large number of conditions that can trigger a controller to begin rebooting.  But keep in mind that the original cause of those reboots will most likely NOT be seen because the lockdown is set PRIOR to SOD to avoid the reboot.  So you will need to determine what activities or symptoms were present BEFORE the lockdown went into place.  It may be necessary to clear the lockdown first so you can monitor the serial shell output and see what process was running at the time the reboot occurred.

 

After addressing the source of the reboots, you can then clear the lockdown state.

 

Regards.

 

Hi,@DiegoLopez 

I have changed the hard drive, but MSDM can not connect, so I want to try to restore the whole device to the original settings

My device status message

===============================================================

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 13891 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
65D0 Host Channel 1--Tachyon QE8
01 TachLite Register Test Passed
65D1 Host Channel 2--Tachyon QE8
01 TachLite Register Test Passed
65D2 Host Channel 3--Tachyon QE8
01 TachLite Register Test Passed
65D3 Host Channel 4--Tachyon QE8
01 TachLite Register Test Passed
3900 Real-Time Clock
01 RT Clock Tick Passed
Diagnostic Manager exited normally.

Current date: 05/19/20 time: 08:35:12

Send for Service Interface or baud rate change
05/19/20-00:27:52 (tRAID): NOTE: Set Powerup State
05/19/20-00:27:52 (tRAID): SOD Sequence is Normal, 0 on controller A
05/19/20-00:27:53 (tRAID): NOTE: Turning on tray summary fault LED
05/19/20-00:27:53 (tRAID): NOTE: SODRebootLoop- Limit:5 Cnt:255
05/19/20-00:27:53 (tRAID): NOTE: Flashing tray summary fault LED
05/19/20-00:27:53 (tRAID): WARN: Controller entering SODReboot lockdown state..

Hi @DiegoLopez 

Can you help me? I have described my device firmware version and other information..THX

Hello again @JQWang

Honestly, I cannot see where you described your device firmware version (03.0A is not the information we are looking for) and other information. All I can see is some serial log.

In the log I see this error: RTC Error: Real-time clock device is not working

This RTC Error is a sync error on the clocks. Normally this could be an issue with the RTC on the controllers (you can try to sync the clocks first on the controllers to see they just got out of sync). This also happens with an older version of firmware then it is good to upgrade that as well.

Do you have a dual controller MD3600f or a single controller MD3600f?  Are you getting the same error on both controllers?  If you connect the serial cable to your controller in slot0 and you remove and reseat the controller can you capture the boot of the controller so we can see what it is stopping on?

If the error is in a single controller and you can't update fw version or access it in any way. The memory DIMM in the controller or the whole controller can be faulty.

To reset the MD3600f to the factory defaults what you can do is to reset the password first on both controllers then you can go into MDSM and remove all virtual disks & host mappings.  To reset the passwords on the back of the controllers there is an orange latch & there is a button under the latch if you press that button it resets the password on the controller.  You will need to do this to both controllers to be sure that the password has been reset.  Once that is done then you can login to the management port default IP 192.168.128.101 & 102. If you have not installed MDSM then will need to do so you can access the management port. 

And if you cannot access MDSM you should be able to access the CLI (serial calbe) to reset the IP’s. Once into the controller you can follow the options to reset the IP address to IPv4.  You will need to do this to both controllers as well.

1. Startup a terminal emulation program like putty, teraterm, minicom or hyperterminal using these terminal settings (115200-8-n-1).

2. Send a from the terminal shell. This is accomplished by within HyperTerminal or Putty, use from within Minicom on Linux systems.

3. When prompted for input within 5 seconds, press for the service interface menu.

Only capital "S" works here, lowercase "s" will not be recognized for this command.

4. The user will then be prompted for a password. The Password is: supportDell

5. The menu options available are.

    1) Display IP Configuration

    2) Change IP Configuration

    3) Reset Storage Array (SYMbol) Password

    Q) Quit Menu

 

I hope this helps.

Regards.