md3220i lock down problem - General - Forum - Storage - Dell Community

md3220i lock down problem

Storage

Storage
Gain insight and information on Dell EMC Storage products from engineers, peers and experts in the industry.

md3220i lock down problem

This question has been answered by JW

hi all,

We have a strange problem with the md3220i.

The system is brand new, we opened the packages and power up the system, but we have something strange with the logs. We can not communicate with the controller. This is what we see in the logs:

Do you have any ideas how to fix this ?

-=<###>=-
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 13884 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 Lines Test Passed
3900 Real-Time Clock
01 RT Clock Tick Passed
Diagnostic Manager exited normally.


Current date: 01/15/14 time: 01:43:59

Send <BREAK> for Service Interface or baud rate change
01/15/14-09:00:05 (tRAID): NOTE: Set Powerup State
01/15/14-09:00:05 (tRAID): SOD Sequence is Normal, 0 on controller A
01/15/14-09:00:05 (tRAID): NOTE: Turning on tray summary fault LED
01/15/14-09:00:06 (tRAID): NOTE: Installed Protocols: <MTPs: INIC SAS USB > <IT
Ps: RDMA ISER IPOIB > <STPs: FCP RmtDMA iSCSI SAS >
01/15/14-09:00:06 (tRAID): NOTE: Required Protocols: <MTPs: INIC SAS > <ITPs:
UNK > <STPs: iSCSI SAS >
01/15/14-09:00:06 (tRAID): NOTE: loading flash file: iSCSI
01/15/14-09:00:08 (tRAID): NOTE: DSM: Current revision 7
01/15/14-09:00:08 (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
01/15/14-09:00:08 (tRAID): NOTE: RCBBitmapManager total RPA size = 1778384896
01/15/14-09:00:09 (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBase = 0x
1
01/15/14-09:00:09 (tRAID): NOTE: loading flash file: MTLSEBET1G
*** Disabled FULL TRACE ***
01/15/14-09:00:09 (tRAID): WARN: MTLSE: before mtl_create_pool:IO task size: 0x
140
01/15/14-09:00:09 (tRAID): NOTE: init: ioc: 0, PLVersion: 11-075-03-00
01/15/14-09:00:10 (tRAID): WARN: MLM: Failed creating m_MelNvsramLock
01/15/14-09:00:10 (tRAID): WARN: MLM: Failed creating m_MelEventListLock
01/15/14-09:00:10 (tRAID): NOTE: CrushMemoryPoolMgr: platform and memory (CPU M
emSize:2048), adjusted allocating size to 65536 for CStripes
01/15/14-09:00:12 (tRAID): SOD: Instantiation Phase Complete
01/15/14-09:00:11 (IOSched): NOTE: SAS Expander Added: expDevHandle:x11 enclHan
dle:x2 numPhys:37 port:2 ioc:0 channel:0 numEntries:22
01/15/14-09:00:11 (tRAID): WARN: sodLockdownCheck: sodSequence update: CtlrLock
down
01/15/14-09:00:11 (tRAID): WARN: No attempt made to open Inter-Controller Commu
nication Channels 0-0
01/15/14-09:00:11 (tRAID): NOTE: LockMgr Role is Master
01/15/14-09:00:12 (tSasExpChk): NOTE: Local Expander Firmware Version: 00.00.80
.10
01/15/14-09:00:18 (tSasDiscCom): NOTE: SAS: Initial Discovery Complete Time: 36
seconds since last power on/reset, 10 seconds since sas instantiated
01/15/14-09:00:18 (tRAID): NOTE: WWN baseName 000290b1-1c1190ee (valid==>SigMat
ch)
01/15/14-09:00:18 (tRAID): NOTE: spmEarlyData: No data available
01/15/14-09:00:18 (tRAID): NOTE: ServerEngines BladeEngine 2 Firmware Update Ut
ility v2.901.242.0
Copyright 2009 ServerEngines Corpo
01/15/14-09:00:18 (tRAID): NOTE:
01/15/14-09:00:18 (tRAID): NOTE: Found BE card 0x0 at 2.0 bar1-base 0xf0200000
bar2-base 0xf0220000 dev 0x384292c
01/15/14-09:00:18 (tRAID): NOTE: flash_rbver = 2.0.3.768
01/15/14-09:00:18 (tRAID): NOTE: flash_armfwver = 2.901.319.0
01/15/14-09:00:20 (tRAID): NOTE: ufi_rbver = 2.0.3.768
01/15/14-09:00:20 (tRAID): NOTE: ufi_armfwver = 2.901.319.0
01/15/14-09:00:20 (tRAID): NOTE: Flash on BladeEngine at 02 : 00 matches UFI SE
BE2T1G
01/15/14-09:00:20 (tRAID): WARN: MTLSE: start: lowLevelInit Target bcmId: 0 ins
tId 0
01/15/14-09:00:20 (tRAID): NOTE: irq_ptr:0xd78850
01/15/14-09:00:20 (tRAID): NOTE: BcmId [4] PCI [2.0.4]
01/15/14-09:00:20 (tRAID): NOTE: DevId 0x0212 VendId 0x19a2
01/15/14-09:00:20 (tRAID): NOTE: BAR0 IO base 0xf0380000
01/15/14-09:00:20 (tRAID): NOTE: BAR1 MEM base 0xf03a0000
01/15/14-09:00:20 (tRAID): NOTE: BAR2 MEM base 0xf03c0000
01/15/14-09:00:20 (tRAID): WARN: MTLSE: done: with initiator initialization: mt
lInt:0x526fbc0 target bcmid:0 init bcmid: 4 rc 0, phba:0x5270020
01/15/14-09:00:20 (tRAID): NOTE: Target:irq_ptr:0x0xd780b0, func:0x0, bcmId:0x0

01/15/14-09:00:20 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 0 BDF 2.0
.0
01/15/14-09:00:20 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
01/15/14-09:00:20 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xd780b0, phba:0
x383fca0, func:0x0
01/15/14-09:00:20 (tRAID): NOTE: BcmId [0] PCI [2.0.0]
01/15/14-09:00:20 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
01/15/14-09:00:20 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
01/15/14-09:00:20 (tRAID): NOTE: BAR1 MEM base 0xf0200000 size 1
01/15/14-09:00:20 (tRAID): NOTE: BAR2 MEM base 0xf0220000 size 1
01/15/14-09:00:20 (tRAID): NOTE: BAR4 MEM base 0xf0240000 size 1
01/15/14-09:00:20 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Oct 25 2012, Time:15:03:42
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.319.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
01/15/14-09:00:21 (tRAID): NOTE: RPA memory region : start 0x47392fe00 size 167
77216 (ConIO-size 16777216) registered for pre-post data buffers on port 0
01/15/14-09:00:21 (tRAID): WARN: MTLSE: Default link local address on interface
1 is fe80:0000:0000:0000:92b1:1cff:fe37:7b41
01/15/14-09:00:21 (tRAID): WARN: MTLSE: Default link local address on interface
5 is fe80:0000:0000:0000:90b1:1c03:e837:7b41
01/15/14-09:00:22 (tRAID): WARN: MTLSE: Default link local address on interface
6 is fe80:0000:0000:0000:90b1:1c07:d037:7b41
01/15/14-09:00:22 (tRAID): WARN: MTLSE: done: with target initialization: 0 rc
0
01/15/14-09:00:22 (tRAID): WARN: MTLSE: done: lowLevelInit bcmId: 0 rc 0
01/15/14-09:00:22 (tRAID): WARN: MTLSE: start: lowLevelInit Target bcmId: 1 ins
tId 1
01/15/14-09:00:22 (tRAID): NOTE: irq_ptr:0xd78668
01/15/14-09:00:22 (tRAID): NOTE: BcmId [3] PCI [2.0.5]
01/15/14-09:00:22 (tRAID): NOTE: DevId 0x0212 VendId 0x19a2
01/15/14-09:00:22 (tRAID): NOTE: BAR0 IO base 0xf03e0000
01/15/14-09:00:22 (tRAID): NOTE: BAR1 MEM base 0xf0400000
01/15/14-09:00:22 (tRAID): NOTE: BAR2 MEM base 0xf0420000
01/15/14-09:00:22 (tRAID): WARN: MTLSE: done: with initiator initialization: mt
lInt:0x5d3a280 target bcmid:1 init bcmid: 3 rc 0, phba:0x5d40060
01/15/14-09:00:22 (tRAID): NOTE: Target:irq_ptr:0x0xd77ec8, func:0x1, bcmId:0x1

01/15/14-09:00:22 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 1 BDF 2.0
.1
01/15/14-09:00:22 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
01/15/14-09:00:22 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xd77ec8, phba:0
x38403b0, func:0x1
01/15/14-09:00:22 (tRAID): NOTE: BcmId [1] PCI [2.0.1]
01/15/14-09:00:22 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
01/15/14-09:00:22 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
01/15/14-09:00:22 (tRAID): NOTE: BAR1 MEM base 0xf0260000 size 1
01/15/14-09:00:22 (tRAID): NOTE: BAR2 MEM base 0xf0280000 size 1
01/15/14-09:00:22 (tRAID): NOTE: BAR4 MEM base 0xf02a0000 size 1
01/15/14-09:00:22 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Oct 25 2012, Time:15:03:42
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.319.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
01/15/14-09:00:23 (tRAID): NOTE: RPA memory region : start 0x47492fe00 size 167
77216 (ConIO-size 16777216) registered for pre-post data buffers on port 1
01/15/14-09:00:23 (tRAID): WARN: MTLSE: Default link local address on interface
2 is fe80:0000:0000:0000:92b1:1cff:fe37:7b42
01/15/14-09:00:23 (tRAID): WARN: MTLSE: Default link local address on interface
7 is fe80:0000:0000:0000:90b1:1c03:e837:7b42
01/15/14-09:00:23 (tRAID): WARN: MTLSE: Default link local address on interface
8 is fe80:0000:0000:0000:90b1:1c07:d037:7b42
01/15/14-09:00:23 (tRAID): WARN: MTLSE: done: with target initialization: 1 rc
0
01/15/14-09:00:23 (tRAID): WARN: MTLSE: done: lowLevelInit bcmId: 1 rc 0
01/15/14-09:00:23 (tRAID): WARN: MTLSE: start: lowLevelInit Target bcmId: 2 ins
tId 2
01/15/14-09:00:23 (tRAID): NOTE: irq_ptr:0xd78480
01/15/14-09:00:23 (tRAID): NOTE: BcmId [2] PCI [2.0.6]
01/15/14-09:00:23 (tRAID): NOTE: DevId 0x0212 VendId 0x19a2
01/15/14-09:00:23 (tRAID): NOTE: BAR0 IO base 0xf0440000
01/15/14-09:00:23 (tRAID): NOTE: BAR1 MEM base 0xf0460000
01/15/14-09:00:23 (tRAID): NOTE: BAR2 MEM base 0xf0480000
01/15/14-09:00:24 (tRAID): WARN: MTLSE: done: with initiator initialization: mt
lInt:0x8d1bb00 target bcmid:2 init bcmid: 2 rc 0, phba:0x8d1e060
01/15/14-09:00:24 (tRAID): NOTE: Target:irq_ptr:0x0xd77ce0, func:0x2, bcmId:0x2

01/15/14-09:00:24 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 2 BDF 2.0
.2
01/15/14-09:00:24 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
01/15/14-09:00:24 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xd77ce0, phba:0
x3840ac0, func:0x2
01/15/14-09:00:24 (tRAID): NOTE: BcmId [2] PCI [2.0.2]
01/15/14-09:00:24 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
01/15/14-09:00:24 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
01/15/14-09:00:24 (tRAID): NOTE: BAR1 MEM base 0xf02c0000 size 1
01/15/14-09:00:24 (tRAID): NOTE: BAR2 MEM base 0xf02e0000 size 1
01/15/14-09:00:24 (tRAID): NOTE: BAR4 MEM base 0xf0300000 size 1
01/15/14-09:00:24 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Oct 25 2012, Time:15:03:42
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.319.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
01/15/14-09:00:25 (tRAID): NOTE: RPA memory region : start 0x47592fe00 size 167
77216 (ConIO-size 16777216) registered for pre-post data buffers on port 2
01/15/14-09:00:25 (tRAID): WARN: MTLSE: Default link local address on interface
3 is fe80:0000:0000:0000:92b1:1cff:fe37:7b43
01/15/14-09:00:25 (tRAID): WARN: MTLSE: Default link local address on interface
9 is fe80:0000:0000:0000:90b1:1c03:e837:7b43
01/15/14-09:00:25 (tRAID): WARN: MTLSE: Default link local address on interface
10 is fe80:0000:0000:0000:90b1:1c07:d037:7b43
01/15/14-09:00:25 (tRAID): WARN: MTLSE: done: with target initialization: 2 rc
0
01/15/14-09:00:25 (tRAID): WARN: MTLSE: done: lowLevelInit bcmId: 2 rc 0
01/15/14-09:00:25 (tRAID): WARN: MTLSE: start: lowLevelInit Target bcmId: 3 ins
tId 3
01/15/14-09:00:25 (tRAID): NOTE: irq_ptr:0xd78298
01/15/14-09:00:25 (tRAID): NOTE: BcmId [1] PCI [2.0.7]
01/15/14-09:00:25 (tRAID): NOTE: DevId 0x0212 VendId 0x19a2
01/15/14-09:00:25 (tRAID): NOTE: BAR0 IO base 0xf04a0000
01/15/14-09:00:25 (tRAID): NOTE: BAR1 MEM base 0xf04c0000
01/15/14-09:00:25 (tRAID): NOTE: BAR2 MEM base 0xf04e0000
01/15/14-09:00:25 (tRAID): WARN: MTLSE: done: with initiator initialization: mt
lInt:0x8e829a0 target bcmid:3 init bcmid: 1 rc 0, phba:0x8e86060
01/15/14-09:00:25 (tRAID): NOTE: Target:irq_ptr:0x0xd77af8, func:0x3, bcmId:0x3

01/15/14-09:00:25 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 3 BDF 2.0
.3
01/15/14-09:00:25 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
01/15/14-09:00:25 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xd77af8, phba:0
x38411d0, func:0x3
01/15/14-09:00:25 (tRAID): NOTE: BcmId [3] PCI [2.0.3]
01/15/14-09:00:25 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
01/15/14-09:00:25 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
01/15/14-09:00:25 (tRAID): NOTE: BAR1 MEM base 0xf0320000 size 1
01/15/14-09:00:25 (tRAID): NOTE: BAR2 MEM base 0xf0340000 size 1
01/15/14-09:00:25 (tRAID): NOTE: BAR4 MEM base 0xf0360000 size 1
01/15/14-09:00:25 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Oct 25 2012, Time:15:03:42
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.319.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
01/15/14-09:00:26 (tRAID): NOTE: RPA memory region : start 0x47692fe00 size 167
77216 (ConIO-size 16777216) registered for pre-post data buffers on port 3
01/15/14-09:00:26 (tRAID): WARN: MTLSE: Default link local address on interface
4 is fe80:0000:0000:0000:92b1:1cff:fe37:7b44
01/15/14-09:00:27 (tRAID): WARN: MTLSE: Default link local address on interface
11 is fe80:0000:0000:0000:90b1:1c03:e837:7b44
01/15/14-09:00:27 (tRAID): WARN: MTLSE: Default link local address on interface
12 is fe80:0000:0000:0000:90b1:1c07:d037:7b44
01/15/14-09:00:27 (tRAID): WARN: MTLSE: done: with target initialization: 3 rc
0
01/15/14-09:00:27 (tRAID): WARN: MTLSE: done: lowLevelInit bcmId: 3 rc 0
01/15/14-09:00:27 (tRAID): SOD: Pre-Initialization Phase Complete
01/15/14-09:00:39 (tRAID): WARN: CmgrLockdownException: CORRUPT DBM DATABASE DE
TECTED - LOCKDOWN Type=6
01/15/14-09:00:39 (tRAID): NOTE: ACS: Acs Needed on Alt: No, StateCode: 6, Reas
onCode = 12
01/15/14-09:00:39 (tRAID): NOTE: ACS: Icon ping to alternate failed: -2, resp:
0
AcsCommunicator::getInstance() Mode undetermined, using DOMI
01/15/14-09:00:39 (tRAID): WARN: ACS: altValidateStagedFirmware(): Domi Excepti
on caught: IconSendInfeasibleException Error
01/15/14-09:00:40 (tRAID): SOD: Code Synchronization Initialization Phase Comple
te
01/15/14-09:00:39 (tRAID): WARN: Lockdown case-DB CORRUPT. NVPS did not update
from Sstor.
01/15/14-09:00:40 (tRAID): SOD: Initialization Phase Complete
==============================================
Title: Disk Array Controller
Copyright 2008-2012 NetApp, Inc. All Rights Reserved.

Name: RC
Version: 07.84.44.60
Date: 10/25/2012
Time: 14:41:57 CDT
Models: 2660
Manager: devmgr.v1084api04.Manager
==============================================

01/15/14-09:00:39 (tRAID): NOTE: SYMbol available
01/15/14-09:00:39 (tRAID): WARN: **********************************************
***********
01/15/14-09:00:39 (tRAID): WARN: **********************************************
***********
01/15/14-09:00:39 (tRAID): WARN: **
**
01/15/14-09:00:39 (tRAID): WARN: ** WARNING!!!!!!
**
01/15/14-09:00:39 (tRAID): WARN: **
**
01/15/14-09:00:39 (tRAID): WARN: ** This controller is locked down due to detec
ted **
01/15/14-09:00:39 (tRAID): WARN: ** corruption in the primary database.
**
01/15/14-09:00:39 (tRAID): WARN: ** In order to prevent any configuration loss,
the **
01/15/14-09:00:39 (tRAID): WARN: ** backed up database must be restored.
**
01/15/14-09:00:39 (tRAID): WARN: **
**
01/15/14-09:00:39 (tRAID): WARN: **
**
01/15/14-09:00:39 (tRAID): WARN: **********************************************
***********
01/15/14-09:00:39 (tRAID): WARN: **********************************************
***********
01/15/14-09:00:40 (tRAID): SOD: sodComplete Notification Complete
01/15/14-09:00:40 (tRAID): sodMain CtlrLockdown sequence finished, elapsed time
= 35 seconds
01/15/14-09:00:40 (tRAID): sodMain complete
01/15/14-09:00:39 (tRAID): WARN: SOD lockdown sequence complete - suspending..

Verified Answer
  • If you have the serial cable, or password reset cable as the manuals refer to it, you may be able to clear the lockdown state. I know this command works, but only if you are able to enter commands in the CLI through the serial port. If it will accept commands, you will see a -> when you press enter. The clear lockdown command is lemClearLockdown I believe. it may be lemClearlockdown though. 

    These controllers go into lockdown states way too easy if you ask me... I'm fighting 10+ MD32XX units right now. Although I cannot enter commands in the CLI, it just enters text and does not recognize it as any kind of command. Hopefully yours aren't as lost as mine, I have one under warranty though, so I am about to call Dell support. I will post an update when I'm done crying.

    Good luck

All Replies
  • Hello WebTosha,

    I see you say that the system is brand new. Did you happen to try updating the firmware when you received this error or no? Also are you getting the error from both controllers & are both controllers rebooting over & over or is it just coming from one controller? In addition to that seeing as the system is brand new I would contact support so that they can try to get the system out of lockdown & can pull logs to see what is causing this issue.

    Please let us know if you have any other questions.

    DELL-Sam L
    Dell | Social Outreach Services - Enterprise
    Download the Dell Quick Resource Locator app today to access PowerEdge support content on your mobile device! (iOS, Android, Windows)

  • Hi WebTosha,

    I just sent you a Private Message about this issue.  I have seen this issue before and would like to ask you a few questions before contacting support so we might be able to ascertain what is causing this issue before they clear the lockdown.

    Thanks,

    Ash

  • I am unable to send a PM through the community site.   Can you please send me an email, I'd like to help with the issue:  ash_mccarty AT dell.com

  • Thanks for your reply

    Was obtained MD3220i with two RAID controllers. After startup, both received IP address of the controller . Tools Modular Disk Storage managery to first connect the controller passed, but damage reported and database management tools were not available to connect the second controller did not pass . First controller was removed , and in its place , a second controller . After that, the system starts and we were able to connect to the system . The system proposed to update the firmware . It has been downloaded the latest firmware from the website and update product of a sequence . The operation completed successfully . Then you added earlier pulling the controller in the second slot . System reported no accordance firmware. Started a firmware update , but after 15 minutes encounter the error that the controller does not respond. After a while, restart the entire system , the result is already listed above . Moreover, if this failed to remove the controller , the system is working properly. But as soon as it is installed in the system , the work stops. If you install only one failed controller to the system and run , the connection means for Modular Disk Storage managery occurs , but the controls can not be opened and only informs the damaged database and re-quired the firmware upgrade. Firmware update does not start, reporting that the firmware file is not true , and reset the database does not happen because they do not correspond to the firmware.

    P.S.

    Sorry for my English. 

  • Thanks for the update.  When did you receive the array?  Were you able to contact Dell Tech Support and get the issue resolved?  If not, when you contact them can you please ask them to connect to the serial port and capture a dqprint output and save to the case.  This will help us analyze why you originally had issues.

  • If you have the serial cable, or password reset cable as the manuals refer to it, you may be able to clear the lockdown state. I know this command works, but only if you are able to enter commands in the CLI through the serial port. If it will accept commands, you will see a -> when you press enter. The clear lockdown command is lemClearLockdown I believe. it may be lemClearlockdown though. 

    These controllers go into lockdown states way too easy if you ask me... I'm fighting 10+ MD32XX units right now. Although I cannot enter commands in the CLI, it just enters text and does not recognize it as any kind of command. Hopefully yours aren't as lost as mine, I have one under warranty though, so I am about to call Dell support. I will post an update when I'm done crying.

    Good luck

  • Thank you. This is what you need. You saved me.

  • Hi, I am stuck at the same issue - I am able to login to cli over serial cable and run netCfgSet command change the mgmt. IP etc.  I can also login using telnet into VxWorks prompt -  I can ping the mgmt port also but other than that nothing more.  MSDM does not find the unit - How do i put the unit into a mode where i can upload a new firmware and Nvram ?

    Thanks

  • The management IP is best set using the on-screen options when you connect via serial.

    To do this.. enter a break, then shift+S. the password is supportDell from here you can modify a few settings- such as LAN parameters, array password, etc.

    -When a PV is in lockdown, MDSM will still detect it. this sounds like it could be something else, but not 100%.

    However, if you are getting the lockdown message in the serial output you will need to proceed in the VxWorks shell to clear the lockdown state.

    -What firmware version is on the array- what version of MDSM is in use-

  • I have tried to bring up the service option but using ctrl + break and then Shift S but it never appears .  i recently acquired, I am struggling through the setup process.  Probably have read all info availabel on forums etc !

    Firmware version: 07.75.14.61

    MSDM - latest

    Upon power up, I get following after mem, processor etc shows ok:

    -=<###>=-

    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 14630 symbols for standalone.

    eth0: LinkUp event

    06/14/16-00:24:49 (tNetCfgInit): NOTE:  Network Ready

     

    Bad File CRC after decompression

    ld(): error loading file (errno = 0x610001).

    shellLib: the current task is not a shell task and there is not any shell task running on the console.

     

     

    Kernel initialization complete

     

     

    Current date: 06/13/16  time: 17:03:00

     

    LSI Logic RAID Controller

    Copyright 2008-2011, LSI Logic Corporation.  All Rights Reserved.

    Copyright 1984-2006 Wind River Systems, Inc.

    VxWorks: VxWorks 6.5   Kernel: WIND version 2.10

    Model: 2660    Firmware version: 07.75.14.61

     

    ->

    Serial Port shell started.

    ----------------------------------------

    it just sits there - i and w give following info:

    -------------------------------------

     

    -> i

     

      NAME         ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY

    ----------  ------------ -------- --- ---------- -------- -------- ------- -----

    tJobTask    31cd9c         881020   0 PEND         405d58   880ef0       0     0

    tExcTask    31bed4         65c4c0   0 PEND         405d58   65eab0       0     0

    tLogTask    logTask        884078   0 PEND         403700   883f50       0     0

    tNbioLog    31e3b0         8877a0   0 PEND         405d58   887690       0     0

    tShell0     shellTask     1d63b50   1 READY        40e0a4  1d61e50  550002     0

    tVkiLog     vkiLogTask    1ff3eb8   4 PEND         405d58  1ff3d80       0     0

    tErfTask    2d93e8         8aad08  10 PEND         4064f0   8aac40       0     0

    ipcom_tick> 4224c4         a3e870  20 DELAY        40c328   a3e7d0       0     3

    tAioIoTask> aioIoTask      89f0d8  50 PEND         4064f0   89eff0       0     0

    tAioIoTask> aioIoTask      8a74e8  50 PEND         4064f0   8a7400       0     0

    tNetTask    netTask        8c2ce0  50 PEND         405d58   8c2b30       2     0

    ipcom_sysl> 4239d8         9cd3a8  50 PEND         4064f0   9cd1f0       0     0

    ipnetd      45ecf4         a36180  50 PEND+T       405d58   a360a0  3d0004 204538

    ipcom_teln> ipcom_telnet   a3b5a0  50 PEND         405d58   a3b380       2     0

    ipdhcpc     41b640         a41b30  50 PEND         405d58   a41940       2     0

    tAioWait    aioWaitTask    896bd0  51 PEND         405d58   896a90       0     0

    tSvc0       141f80         87b010  70 PEND         403700   87af10       0     0

    tCciTask    cciTask        8bdd80  75 PEND         405d58   8bdcc0       0     0

    tSubSys     subSysIntHan   ba15d0 100 PEND         405d58   ba1500       0     0

    tNetReset   1cbfc0        1d52868 100 PEND+T       403700  1d52720       2     1

    tVkiIdle    vkiIdle       1ff1a28 250 READY        15fad8  1ff1950       0     0

    value = 0 = 0x0

    -> w

      NAME       ENTRY       TID       STATUS   DELAY  OBJ_TYPE    OBJ_ID   OBJ_NAME

    ---------- ---------- ---------- ---------- ----- ---------- ---------- --------

    tJobTask     0x31cd9c   0x881020 PEND           0 SEM_B        0x621cbc N/A

    tExcTask     0x31bed4   0x65c4c0 PEND           0 SEM_B        0x621b50 N/A

    tLogTask   logTask      0x884078 PEND           0 MSG_Q(R)     0x8822e0 N/A

    tNbioLog     0x31e3b0   0x8877a0 PEND           0 SEM_B        0x779810 N/A

    tShell0    shellTask   0x1d63b50 READY          0                     0

    tVkiLog    vkiLogTask  0x1ff3eb8 PEND           0 SEM_B       0x1ff2e38 N/A

    tErfTask     0x2d93e8   0x8aad08 PEND           0 SEM_C        0x8a9c88 N/A

    ipcom_tick   0x4224c4   0xa3e870 DELAY          1                     0

    tAioIoTask aioIoTask    0x89f0d8 PEND           0 SEM_C        0x897fd8 N/A

    tAioIoTask aioIoTask    0x8a74e8 PEND           0 SEM_C        0x897fd8 N/A

    tNetTask   netTask      0x8c2ce0 PEND           0 SEM_B        0x65bec4 N/A

    ipcom_sysl   0x4239d8   0x9cd3a8 PEND           0 SEM_C        0x9cea38 N/A

    ipnetd       0x45ecf4   0xa36180 PEND+T     200661 SEM_B        0xa37ae0 N/A   

    ipcom_teln ipcom_teln   0xa3b5a0 PEND           0 SEM_B        0xa2b2d8 N/A

    ipdhcpc      0x41b640   0xa41b30 PEND           0 SEM_B        0xa43460 N/A

    tAioWait   aioWaitTas   0x896bd0 PEND           0 SEM_B        0x897ef0 N/A

    tSvc0        0x141f80   0x87b010 PEND           0 MSG_Q(R)     0x7662d0 N/A

    tCciTask   cciTask      0x8bdd80 PEND           0 SEM_B        0x8ae950 N/A

    tSubSys    subSysIntH   0xba15d0 PEND           0 SEM_B        0xb9e4d0 N/A

    tNetReset    0x1cbfc0  0x1d52868 PEND+T       623 MSG_Q(R)    0x1d4d598 N/A

    tVkiIdle   vkiIdle     0x1ff1a28 READY          0                     0

    value = 0 = 0x0

    ->

  • I've got an idea.. This does not appear to be in lockdown, just bad FW. Though the alternate may be locked.

    -Typically you will see some output referring to the alternate controller, there is none in your print from boot to halt- it doesn't complete due to corrupt FW. This could be thwarting the alternate controller, potentially locking it out.

    Remove the controller that gave the above cli output- connect the serial cable to the other controller and move it to slot 0.

    -There is a chance the standard setup process will work as far as adding the array, and thanks to the error bypass option in the latest MDSM SW, you'll be able to perform a firmware update with it in a degraded state. You may have to get into the VxWorks shell and run the lemClearLockdown command before bringing it up.

    Once you've got it in MDSM, update the controller to the latest FW, you will need to update to the bridge FW first! 7.75.28.60, then onto the latest 8.x FW.

    Once you've got the single controller running 8.20.16.60, install the "bad" controller in the secondary slot and connect the serial cable immediately.
    The firmware mismatch will trigger a forced update to the "bad" controller- You'll see the progress in real-time in the CLI.

    -if the controller has issues other than corrupt FW, the downloads may not even start.

    -This is not necessarily a permanent fix! the controller's FW corrupted for a good reason somewhere along the way. I strongly recommend having a replacement plan if the controller goes down again. With the array optimal in duplex mode, there isn't really a critical risk, but if that controller goes down again I strongly recommend replacing it as it will likely just get worse. Running some burn-ins may bring back confidence. At the least- run the onboard controller diagnostics. Can do in the hardware tab, right click the controller and the option is there somewhere...

    -If none of this works, try removing the drives when attempting to bring up the alternate controller- then add 1x drive before attempting the update (it is required). It is ideal to use a disk that was not previously configured in a PowerVault, but must be a Dell certified SAS drive. Certain errors can be transferred with drives- this does not appear to be one of them, but just in case... usually only cfg db errors will move with components that store the config.

    I hope this helps- this is somewhat of a last ditch move.

    ### But I could be completely wrong about my directions above, the CRC fail after decompression could point at a flash memory problem, there is a DDR2 DIMM and an SD card internal to each controller that can fail. Things that cause stuff to fail after decompression: bad fw, bad flash, bad sys board. The above will only work if it is bad fw.

  • JW - thank you for taking the time to write these instructional details - really good stuff !

    Here is the challenge, I only have one controller in the unit ! I just acquired this MD3200i and it came with a single controller.  The unit was working before it was decommissioned. 

    Looking at the LEDs - all are according to the user manual - only battery LED is amber so I ordered an OEM replacement battery.

    I am just trying to load a new FW so it can start to work.  I read in some forums that when a FW is missing, the unit can ask for xmodem upload of the FW.  Is there a way to put this controller into that mode so it will ask for a file upload without a MDSM station?

    I am able to connect with telnet also to this unit.

    Thanks again for all your help !  

  • Ok - so for anyone else having the same issues - i have figured out the following:

    xtraputty has xmodem option so you can upload download files

    hitting ctrl + x three consecutive times on console bring up the file upload option for firmware and nvsram upload

    ctrl + b during boot bring up a diagnostics menu

    ctrl + x does a soft reboot

    shellUsr login password is available at a Chinese language site - it is a 7 character password - D*****> 

    Challenges experienced:  

    xtraputty crashes during xmodem firmware upload and thus requires a lot of patience ! many tries for a simple task - 

    have not been able to fully upload a complete firmware file other than the "bridge firmware"

    MDSM still does not find the unit even though I can ping it :( 

    will keep you posted 

  • Hello zminhas,

    Here is a link to the Deployment guide for your MD3220i. I would double check your setup to ensure that your setup is correct. http://downloads.dell.com/manuals/common/powervault-md3200i_deployment%20guide_en-us.pdf

    It is strange that you can ping the Management IP of your MD3220i but you can’t connect to it via MDSM. Also have you tried to access MDSM via CLI? Here is a link to the CLI guide for MDSM just in case you need it. http://topics-cdn.dell.com/pdf/powervault-md3200_CLI%20Guide_en-us.pdf

    Please let us know if you have any other questions.

    DELL-Sam L
    Dell | Social Outreach Services - Enterprise
    Download the Dell Quick Resource Locator app today to access PowerEdge support content on your mobile device! (iOS, Android, Windows)

  • So here's where I am so far after loading the bridge firmware:  I issued lemClearLockdown but it ends up at this stage after reboot.... any ideas?

    ----------
    -=<###>=-
    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 14630 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
    06/17/16-18:31:34 (tNetCfgInit): NOTE:  Network Ready


    Current date: 06/17/16  time: 11:09:43

    Send <BREAK> for Service Interface or baud rate change
    06/17/16-18:31:41 (tRAID): NOTE:  Set Powerup State
    06/17/16-18:31:41 (tRAID): NOTE:  SOD Sequence is Normal, 0
    06/17/16-18:31:42 (tRAID): NOTE:  Turning on tray summary fault LED
    06/17/16-18:31:42 (tRAID): ERROR: SBB ICID value bad
    06/17/16-18:31:42 (tRAID): WARN:  Suspending Ctlr: "SBB_Ctlr_Validation_Failed"
    06/17/16-18:31:42 (tRAID): NOTE:  Flashing tray summary fault LED
    06/17/16-18:31:42 (tRAID): WARN:  Controller entering ClientErr lockdown state...