Highlighted
N/A

MD3220i slow read

Hello.

Our MD3220i is a very slow read performance. 40Mb/sec. I think this is not normal.

Host have a 3 gigabit connections (with MPIO) to storage. Jumbo frames is enabled.

Segment size 64K

Storage firmware version: 07.84.47.60

What could be the problem?

0 Kudos
8 Replies

RE: MD3220i slow read

Hello fxNil,

One thing that I would do is to upgrade the firmware on your MD3220i to a newer version. The current version that you are running was released in July of 2013. There have been a number of speed improvements since that release. Along with updating the firmware of your controllers in your MD3220i I would also upgrade the firmware of the HDD as well. Here are a couple of links to both the controller firmware & HDD firmware.

Controller Firmware

http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=4CP5X&fileId=1956170581&os...

HDD Firmware

http://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=GRH7X&fileId=1962189984&os...

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)

0 Kudos
DrTuy
Copper

RE: MD3220i slow read

Hello.

I was upgraded disks firmware successfully.

But upgrade RAID controller firmware was fail. Now I can't connect to MD3220i with MDSM and MDCU.

Ping to management ports a going well.

I don't know what to do. It's terrible.

0 Kudos
DrTuy
Copper

RE: MD3220i slow read

10/11/17-06:50:19 (tSystem): ERROR: FPGA FW is out of date
"Rhone03 rev17" currently in use
"Rhone03 rev20" available for update
10/11/17-06:50:23 (tNetCfgInit): NOTE: eth0: LinkUp event
10/11/17-06:50:24 (tNetCfgInit): NOTE: Network Ready
Current date: 10/11/17 time: 06:50:44

NetApp, Inc. RAID Controller
Copyright 2008-2017, NetApp, Inc. All Rights Reserved.
Copyright 1984-2006 Wind River Systems, Inc.
VxWorks: VxWorks 6.5 Kernel: WIND version 2.10
Model: 2660 Firmware version: 08.20.24.60
10/11/17-06:50:44 (tRAID): SOD Sequence is Normal, 0 on controller B

->
Serial Port shell started.
10/11/17-06:50:44 (tRAID): NOTE: loading flash file: ECTDell
10/11/17-06:50:45 (tRAID): NOTE: unloading flash file: ECTDell
10/11/17-06:50:45 (tRAID): NOTE: Turning on tray summary fault LED
10/11/17-06:50:45 (tRAID): NOTE: SODRebootLoop- Limit:5 Cnt:4
10/11/17-06:50:45 (tRAID): NOTE: Installed Protocols: <MTPs: INIC SAS USB > <ITPs: RDMA ISER IPOIB > <STPs: FCP RmtDMA iSCSI SAS >
10/11/17-06:50:45 (tRAID): NOTE: Required Protocols: <MTPs: INIC SAS > <ITPs: UNK > <STPs: iSCSI SAS >
10/11/17-06:50:45 (tRAID): NOTE: loading flash file: iSCSI
10/11/17-06:50:46 (tRAID): NOTE: loading flash file: MTLSEBET1G
*** Disabled FULL TRACE ***
10/11/17-06:50:47 (tRAID): WARN: MTLSE: before mtl_create_pool:IO task size: 0x140
10/11/17-06:50:48 (tRAID): NOTE: DSM: Current revision 7
10/11/17-06:50:48 (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
10/11/17-06:50:48 (tRAID): NOTE: cmgrCtlr: Board Manager HostBoardData Model Name for slot 0: 0501
10/11/17-06:50:48 (tRAID): NOTE: RCBBitmapManager total RPA size = 1761607680
10/11/17-06:50:49 (tRAID): NOTE: init: ioc: 0, PLVersion: 13-075-70-00
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=0
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=1
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=2
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=3
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=4
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=5
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=6
10/11/17-06:50:49 (tRAID): ERROR: findChannelFromIocPhy: channel not found, ioc=0, phy=7
10/11/17-06:50:49 (IOSched): NOTE: SAS Expander Added: expDevHandle:x11 enclHandle:x2 numPhys:37 port:2 ioc:0 channel:1 numEntries:22
10/11/17-06:50:50 (tSasExpChk): NOTE: Local Expander Firmware Version: 00.00.80.16
10/11/17-06:50:50 (tSasExpChk): NOTE: Enabling this controller's expander phys, channel=1
10/11/17-06:50:50 (sasEnPhys): NOTE: sasEnableDrivePhysTask: 24 phys enabled on channel 1
10/11/17-06:50:56 (tSasDiscCom): NOTE: SAS: Initial Discovery Complete Time: 42 seconds since last power on/reset, 10 seconds since sas instantiated
10/11/17-06:50:57 (tRAID): NOTE: CrushMemoryPoolMgr: platform and memory (CPU MemSize:2048), adjusted allocating size to 65536 for CStripes
10/11/17-06:50:58 (tRAID): SOD: Instantiation Phase Complete
10/11/17-06:50:58 (tRAID): WARN: No attempt made to open Inter-Controller Communication Channels 0-0
10/11/17-06:50:58 (tRAID): NOTE: Failing The Alternate Controller
10/11/17-06:50:58 (tRAID): WARN: Alt Ctl Reboot:
Reboot CompID: 0x401
Reboot reason: 0x6
Reboot reason extra: 0x0
10/11/17-06:50:58 (tRAID): NOTE: holding alt ctl in reset
10/11/17-06:50:58 (tRAID): NOTE: Alt firmware running deasserted: 0 ms
10/11/17-06:50:58 (tRAID): NOTE: HealthCheck: Alt Ctl: 1 Reset_Failure, state: 0 Start
10/11/17-06:50:58 (tRAID): NOTE: LockMgr Role is Master
10/11/17-06:50:59 (tRAID): NOTE: WWN baseName 0008d4ae-52b3b05f (valid==>SoftRst)
10/11/17-06:50:59 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
10/11/17-06:50:59 (tRAID): NOTE: ServerEngines BladeEngine 2 Firmware Update Utility v2.901.242.0
Copyright 2009 ServerEngines Corpo
10/11/17-06:50:59 (tRAID): NOTE:
10/11/17-06:50:59 (tRAID): NOTE: Found BE card 0x0 at 2.0 bar1-base 0xf0200000 bar2-base 0xf0220000 dev 0x323164c
10/11/17-06:50:59 (tRAID): NOTE: flash_rbver = 2.0.3.768
10/11/17-06:50:59 (tRAID): NOTE: flash_armfwver = 2.901.326.0
10/11/17-06:51:00 (tRAID): NOTE: ufi_rbver = 2.0.3.768
10/11/17-06:51:00 (tRAID): NOTE: ufi_armfwver = 2.901.326.0
10/11/17-06:51:00 (tRAID): NOTE: Flash on BladeEngine at 02 : 00 matches UFI SEBE2T1G
10/11/17-06:51:01 (tRAID): NOTE: Target:irq_ptr:0x0xe3aeb0, func:0x0, bcmId:0x0
10/11/17-06:51:01 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 0 BDF 2.0.0
10/11/17-06:51:01 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
10/11/17-06:51:01 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3aeb0, phba:0x322eb80, func:0x0
10/11/17-06:51:01 (tRAID): NOTE: BcmId [0] PCI [2.0.0]
10/11/17-06:51:01 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
10/11/17-06:51:01 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
10/11/17-06:51:01 (tRAID): NOTE: BAR1 MEM base 0xf0200000 size 1
10/11/17-06:51:01 (tRAID): NOTE: BAR2 MEM base 0xf0220000 size 1
10/11/17-06:51:01 (tRAID): NOTE: BAR4 MEM base 0xf0240000 size 1
10/11/17-06:51:01 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
10/11/17-06:51:02 (tRAID): NOTE: RPA memory region : start 0x471977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 0
10/11/17-06:51:02 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
10/11/17-06:51:03 (tRAID): NOTE: Target:irq_ptr:0x0xe3ad68, func:0x1, bcmId:0x1
10/11/17-06:51:03 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 1 BDF 2.0.1
10/11/17-06:51:03 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
10/11/17-06:51:03 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3ad68, phba:0x322f2a0, func:0x1
10/11/17-06:51:03 (tRAID): NOTE: BcmId [1] PCI [2.0.1]
10/11/17-06:51:03 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
10/11/17-06:51:03 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
10/11/17-06:51:03 (tRAID): NOTE: BAR1 MEM base 0xf0260000 size 1
10/11/17-06:51:03 (tRAID): NOTE: BAR2 MEM base 0xf0280000 size 1
10/11/17-06:51:03 (tRAID): NOTE: BAR4 MEM base 0xf02a0000 size 1
10/11/17-06:51:03 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
10/11/17-06:51:04 (tRAID): NOTE: RPA memory region : start 0x472977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 1
10/11/17-06:51:04 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
10/11/17-06:51:04 (tRAID): NOTE: Target:irq_ptr:0x0xe3ac20, func:0x2, bcmId:0x2
10/11/17-06:51:04 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 2 BDF 2.0.2
10/11/17-06:51:04 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
10/11/17-06:51:04 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3ac20, phba:0x322f9c0, func:0x2
10/11/17-06:51:04 (tRAID): NOTE: BcmId [2] PCI [2.0.2]
10/11/17-06:51:04 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
10/11/17-06:51:04 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
10/11/17-06:51:04 (tRAID): NOTE: BAR1 MEM base 0xf02c0000 size 1
10/11/17-06:51:04 (tRAID): NOTE: BAR2 MEM base 0xf02e0000 size 1
10/11/17-06:51:04 (tRAID): NOTE: BAR4 MEM base 0xf0300000 size 1
10/11/17-06:51:04 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
10/11/17-06:51:05 (tRAID): NOTE: RPA memory region : start 0x473977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 2
10/11/17-06:51:05 (tRAID): NOTE: sebeReadEEPROMChecksum: EEPROM checksum match: 0x81986278
10/11/17-06:51:06 (tRAID): NOTE: Target:irq_ptr:0x0xe3aad8, func:0x3, bcmId:0x3
10/11/17-06:51:06 (tRAID): NOTE: VendorID 0x19a2 DeviceId 0x210 bcmId 3 BDF 2.0.3
10/11/17-06:51:06 (tRAID): NOTE: Target:VKI_INT_CONNECT success:status:0x0
10/11/17-06:51:06 (tRAID): ERROR: Target:ISR registered:irq_ptr:0xe3aad8, phba:0x32300e0, func:0x3
10/11/17-06:51:06 (tRAID): NOTE: BcmId [3] PCI [2.0.3]
10/11/17-06:51:06 (tRAID): NOTE: DevId 0x0210 VendId 0x19a2
10/11/17-06:51:06 (tRAID): NOTE: BAR0 IO base 0x00000000 size 0
10/11/17-06:51:06 (tRAID): NOTE: BAR1 MEM base 0xf0320000 size 1
10/11/17-06:51:06 (tRAID): NOTE: BAR2 MEM base 0xf0340000 size 1
10/11/17-06:51:06 (tRAID): NOTE: BAR4 MEM base 0xf0360000 size 1
10/11/17-06:51:06 (tRAID): NOTE: MPU_EP_SEMAPHORE 0x0000c000
Driver Build Date:Apr 13 2017, Time:18:13:48
ServerEngines iSCSI Target Driver loaded
iSCSI Firmware Version:2.901.326.0
iSCSI Driver Version:2.901.242.0
Found BladeEngine2 in Gen2 x8 PCIe slot
10/11/17-06:51:07 (tRAID): NOTE: RPA memory region : start 0x474977e00 size 16777216 (ConIO-size 16777216) registered for pre-post data buffers on port 3
10/11/17-06:51:08 (tRAID): SOD: Pre-Initialization Phase Complete
10/11/17-06:51:20 (tRAID): WARN: ACS: testCommunication: Domi Exception caught: IconSendInfeasibleException Error
10/11/17-06:51:20 (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Status: 0
10/11/17-06:51:20 (tRAID): WARN: ACS: autoCodeSync(): Skipped since alt not communicating.
10/11/17-06:51:20 (tRAID): NOTE: iocfi: Peering Disabled (Alt Unavailable)
10/11/17-06:51:21 (tRAID): SOD: Code Synchronization Initialization Phase Complete
10/11/17-06:51:21 (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/11/17-06:51:21 (tRAID): NOTE: adjustLogicalCBSizeToBlks: vol(0)'s CBS was persisted in bytes(4096), convert to blks
10/11/17-06:51:22 (tRAID): NOTE: adjustLogicalCBSizeToBlks: vol(1)'s CBS was persisted in bytes(4096), convert to blks
10/11/17-06:51:22 (tRAID): NOTE: adjustLogicalCBSizeToBlks: vol(6)'s CBS was persisted in bytes(4096), convert to blks
10/11/17-06:51:22 (tRAID): NOTE: adjustLogicalCBSizeToBlks: vol(7)'s CBS was persisted in bytes(4096), convert to blks
10/11/17-06:51:22 (tRAID): NOTE: SAFE: Process new features
10/11/17-06:51:22 (tRAID): NOTE: SAFE: Process legacy features
10/11/17-06:51:22 (tRAID): NOTE: IOManager::restoreData - dataSize:0x2800000, startAddress:0x4779f7e00
10/11/17-06:51:24 (tRAID): NOTE: ncb::IOManager::restoreData - Successful
10/11/17-06:51:24 (tRAID): NOTE: OBB Restore From Flash Completed
10/11/17-06:51:24 (bdbmBGTask): ERROR: sendFreezeStateToAlternate: Exception IconSendInfeasibleException Error
10/11/17-06:51:25 (tRAID): NOTE: SPM acquireObjects exception: IconSendInfeasibleException Error
10/11/17-06:51:26 (tRAID): NOTE: sas: Peering Disabled (Alt unavailable)
10/11/17-06:51:26 (tRAID): NOTE: b_isn: Peering Disabled (Alt Unavailable)
10/11/17-06:51:26 (tRAID): NOTE: ion: Peering Disabled (Alt Unavailable)
10/11/17-06:51:27 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:28 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:29 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:31 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:32 (mtlseMgmtTask): WARN: Port[0] MTLSE Link event: link DOWN
10/11/17-06:51:32 (mtlseMgmtTask): WARN: Port[1] MTLSE Link event: link DOWN
10/11/17-06:51:32 (mtlseMgmtTask): WARN: Port[2] MTLSE Link event: link DOWN
10/11/17-06:51:32 (mtlseMgmtTask): WARN: Port[3] MTLSE Link event: link DOWN
10/11/17-06:51:32 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:32 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:32 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:32 (tRAID): WARN: mtlsebe::MtlInterface:Smiley TonguearameterValidation
10/11/17-06:51:32 (tRAID): WARN: MTLSE: group iSCSI Mtl:Smiley TonguearameterCommitCompleted without any other parameter events.
10/11/17-06:51:32 (tRAID): WARN: MTLSE: group iSNS Mtl:Smiley TonguearameterCommitCompleted without any other parameter events.
10/11/17-06:51:32 (tRAID): NOTE: iSCSI Queue Depth is(QLTA_MAX_TRBS) = 2560
10/11/17-06:51:32 (tRAID): NOTE: The sizeof TRBext =104 TpbExt =54
10/11/17-06:51:33 (tRAID): WARN: Unable to intialize mirror device
10/11/17-06:51:33 (tRAID): NOTE: CacheMgr::cacheOpenMirrorDevice:: mirror device 0xfffffff
10/11/17-06:51:33 (tRAID): WARN: CCM Failed to notify the alternate to update Cache Store in pstor, writeCacheStoreToPstor() caught IconSendInfeasibleException Error
10/11/17-06:51:33 (tRAID): WARN: CCM: mirrorInit() alternate did not check in
10/11/17-06:51:34 (tRAID): WARN: CCM Failed to notify the alternate to update Cache Store in pstor, writeCacheStoreToPstor() caught IconSendInfeasibleException Error
10/11/17-06:51:34 (tRAID): NOTE: CCM: sodClearMOSIntentsAlt(), failure clearing MOS intents on alt
10/11/17-06:51:35 (tRAID): NOTE: doRecovery: myMemory:1, IORCB:0, NEW:0, OLD:0
10/11/17-06:51:35 (tRAID): WARN: CCM Failed to notify the alternate to update Cache Store in pstor, writeCacheStoreToPstor() caught IconSendInfeasibleException Error
10/11/17-06:51:35 (tRAID): WARN: PSTOR: PstorRecordMgr: removeRecord failed
10/11/17-06:51:35 (tRAID): WARN: deleteBackupStatus: caught pstorRecordNotFoundException Line 1893 File ncbIOManager.cc
10/11/17-06:51:37 (tRAID): NOTE: UWMgr findIWLogs: Found IW log drive. Devnum 0x10000 tray=0 slot=1 ssd=0 qos=3 controller=0
10/11/17-06:51:37 (tRAID): NOTE: UWMgr findIWLogs: Found IW log drive. Devnum 0x10001 tray=0 slot=2 ssd=0 qos=3 controller=0
10/11/17-06:51:37 (tRAID): WARN: Null Pointer Exception-PieceManager::initialize
10/11/17-06:51:37 (tRAID): WARN: To *view* records:
resume IOSched [tr "IOSched"]
invoke vdmPrunerPanic(0x0ad057a0)
or invoke evfPrunerMenu(0x0ad057a0)
10/11/17-06:51:37 (tRAID): PANIC: SOD failure in vdm::initialize
volume records but you can view/analyze them through the vdmPruner tool
10/11/17-06:51:37 (tRAID): PANIC: SOD failure in vdm::initialize

Stack Trace for tRAID:
0x0027cc4c vxTaskEntry +0x5c : 0x0160c2c4 (0, 0)
0x0160c5d4 sodMain +0x314: sodInitialization() ()
0x0160e3b0 sodInitialization()+0x30 : sodInitializeApplication() ()
0x0160ecc8 sodInitializeApplication()+0xa8 : sodLogStartup(void (*)()) ()
0x0160f21c sodLogStartup(void (*)())+0xbc : 0x0706ee64 ()
0x0706ee74 vdm::initialize()+0x14 : vdm::beginInitialize(bool) ()
0x070707a4 vdm::beginInitialize(bool)+0x18c4: _vkiCmnErr__link ()
0x001778c4 _vkiCmnErr +0x104: 0x00177b00 (0x5b1144, 0x8405b38, 0x1ca1760)
0x00177f08 vkiLogShow +0x5c8: _vkiReboot (0x78002, 0)
0x00176194 _vkiReboot +0x54 : reboot ()
0x0033f084 reboot +0x5c : _vkiRebootHook (0)
0x00176330 _vkiRebootHook+0x50 : sasResetHook ()
0x0625b0f0 sasResetHook +0xf0 : sas::sasResetCtrlExp(int) ()
0x062b2c20 sas::sasResetCtrlExp(int)+0x40 : delayMilliseconds__link ()

-=<###>=-
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 14607 symbols for standalone.
10/11/17-06:51:45 (tSystem): ERROR: FPGA FW is out of date
"Rhone03 rev17" currently in use
"Rhone03 rev20" available for update
10/11/17-06:51:49 (tNetCfgInit): NOTE: eth0: LinkUp event
10/11/17-06:51:49 (tNetCfgInit): NOTE: Network Ready
Current date: 10/11/17 time: 06:52:10

NetApp, Inc. RAID Controller
Copyright 2008-2017, NetApp, Inc. All Rights Reserved.
Copyright 1984-2006 Wind River Systems, Inc.
VxWorks: VxWorks 6.5 Kernel: WIND version 2.10
Model: 2660 Firmware version: 08.20.24.60
10/11/17-06:52:10 (tRAID): SOD Sequence is Normal, 0 on controller B

->
Serial Port shell started.
10/11/17-06:52:10 (tRAID): NOTE: loading flash file: ECTDell
10/11/17-06:52:10 (tRAID): NOTE: unloading flash file: ECTDell
10/11/17-06:52:11 (tRAID): NOTE: Turning on tray summary fault LED
10/11/17-06:52:11 (tRAID): NOTE: SODRebootLoop- Limit:5 Cnt:5
10/11/17-06:52:11 (tRAID): NOTE: Flashing tray summary fault LED
10/11/17-06:52:11 (tRAID): WARN: Controller entering SODReboot lockdown state...
10/11/17-06:52:11 (tRAID): WARN: Controller entering SODReboot lockdown state...

0 Kudos
DrTuy
Copper

RE: MD3220i slow read

Can someone help me in solving this issue?

0 Kudos

RE: MD3220i slow read

Hello DrTuy,

Looking at your output that you have posted it looks like the second controller was not detected so that the firmware could be installed on it. The master controller then tried to reboot to connect to the alt controller but was still not able to do so, and therefore kept rebooting to try to regain connection to the alt controller. It looks like the controller had entered a lockdown state as it is not able to boot to Start of Day message. When we see this error we would clear the lock down by accessing the shell of the controller, and running the lemClearLockdown command. That will clear the error and allow the controller to boot. Now we would still need to make sure that the master controller can see your alt controller so that you can finish the firmware upgrade.

To run the lemClearLockdown command you will need to login to the secure shell on the controller. Now the username and password is only provided to support. Now if you do a web search there are some articles that can assist you in running the command & getting your system back up & running if your MD3220i is not still under warranty.

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)

0 Kudos
DrTuy
Copper

RE: MD3220i slow read

I entered the lemClearLockdown command  but it did not produce the effect. The log that I showed appeared the same on both controllers.
Perhaps some special sequence of actions may be necessary before performing lemClearLockdown?

0 Kudos

RE: MD3220i slow read

Hello DrTuy,

If you are running the command as the shell user & it is not able to clear then most likely the controllers will need to be replaced.

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)

0 Kudos

RE: MD3220i slow read

Hello DrTuy,

If you are running the command as the shell user & it is not able to clear then most likely the controllers will need to be replaced.

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)

0 Kudos