Unsolved
2 Posts
0
847
May 15th, 2020 11:00
MD3200i in SODReboot lockdown state
Hello,
I am having issue with MD3200i after it lost iscsi connection with a PowerEdge server. Currently all the iscsi interface are not responding to ping. Out-Of-Band port is pingable but the array is not detected by MDSM software. Physically there is a amber led blinking at the front. When I plugin the console cable and power cycle the unit I see the message said the array is in SODReboot lockdown state.
I did some reading over the forum, seems this means the controllers are not boot up successfully and lock itself as protection. I would like to ask in this state how could I determine the cause of the lockdown? Should I unlock the controller first and boot again?
Regards,
And below are the boot log capture from both controller.
#####Controller 0#####
-=<###>=-
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:" " ...
RTC Error: Real-time clock device is not working
OK.
Adding 14308 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.
eth0: LinkUp event
05/15/20-13:05:26 (tNetCfgInit): NOTE: Network Ready
Current date: 05/15/20 time: 02:53:22
Send for Service Interface or baud rate change
05/15/20-13:05:37 (tRAID): NOTE: Set Powerup State
05/15/20-13:05:37 (tRAID): NOTE: SOD Sequence is Normal, 0
05/15/20-13:05:37 (tRAID): NOTE: Turning on tray summary fault LED
05/15/20-13:05:37 (tRAID): NOTE: SODRebootLoop- Limit:5 Cnt:5
05/15/20-13:05:37 (tRAID): NOTE: Flashing tray summary fault LED
05/15/20-13:05:37 (tRAID): WARN: Controller entering SODReboot lockdown state...
#####Controller 1#####
-=<###>=-
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:" " ...
RTC Error: Real-time clock device is not working
OK.
Adding 14308 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.
eth0: LinkUp event
05/15/20-12:55:47 (tNetCfgInit): NOTE: Network Ready
Current date: 05/15/20 time: 01:52:16
Send for Service Interface or baud rate change
05/15/20-12:55:57 (tRAID): NOTE: Set Powerup State
05/15/20-12:55:57 (tRAID): NOTE: SOD Sequence is Normal, 0
05/15/20-12:55:57 (tRAID): NOTE: Turning on tray summary fault LED
05/15/20-12:55:57 (tRAID): NOTE: SODRebootLoop- Limit:5 Cnt:5
05/15/20-12:55:57 (tRAID): NOTE: Flashing tray summary fault LED
05/15/20-12:55:57 (tRAID): WARN: Controller entering SODReboot lockdown state...
DELL-Sam L
Moderator
•
7.7K Posts
0
May 15th, 2020 15:00
Hello citizen_B,
Your system is in a lockdown state. If your system is under warranty then you will want to call into support so that we can clear the lockdown. If you are not under warranty, then you will need to access the VXshellusr of your MD and clear the lockdown. The VXshellusr account has a password that can’t be provided to customers, and that is why we say to call support to clear this error.
Please let us know if you have any other questions.
citizen_B
2 Posts
0
May 15th, 2020 19:00
Hello Sam,
Thank you for your reply.
Would a faulty power support causing a lockdown? Because I do have one power supply flashing amber led, and I have populated all the bay with harddisk.
Could I generate a support bundle at this state? And say I have VXshellusr access to unlock the controller, Would this cause harm to have the controller try to boot so than I can capture the console output?
Regards,
DELL-Sam L
Moderator
•
7.7K Posts
0
May 18th, 2020 10:00
Hello citizen_B,
A lockdown can happen for many reasons. Losing a single power supply should not trigger a lockdown. You should be able to gather a support bundle with one working power supply. You can clear the lockdown on your own if your system is out of warranty, however if you do it wrong you can harm your data. if your system is still under warranty then I would call in so that we can clear the lockdown.
Please let us know if you have any other questions.