Unsolved
This post is more than 5 years old
5 Practitioner
•
274.2K Posts
0
28187
md3600f lock down problem
hi all,
We have a strange problem with the md3600f.
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 two controllers, one of them have some sort of problem.This is what we see in the logs:
Do you have any ideas how to fix this ?
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: 02/08/13 time: 08:48:29
Send for Service Interface or baud rate change
02/08/13-15:25:12 (tRAID): NOTE: Set Powerup State
02/08/13-15:25:13 (tRAID): SOD Sequence is Normal, 0 on controller A
02/08/13-15:25:13 (tRAID): NOTE: Turning on tray summary fault LED
02/08/13-15:25:13 (tRAID): NOTE: Installed Protocols:
02/08/13-15:25:13 (tRAID): NOTE: Required Protocols:
02/08/13-15:25:13 (tRAID): NOTE: loading flash file: Fibre
02/08/13-15:25:15 (tRAID): NOTE: DSM: Current revision 7
02/08/13-15:25:16 (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
02/08/13-15:25:16 (tRAID): NOTE: RCBBitmapManager total RPA size = 1778384896
02/08/13-15:25:16 (tRAID): NOTE: init: ioc: 0, PLVersion: 11-075-03-00
02/08/13-15:25:17 (tRAID): WARN: MLM: Failed creating m_MelNvsramLock
02/08/13-15:25:17 (tRAID): WARN: MLM: Failed creating m_MelEventListLock
02/08/13-15:25:17 (tRAID): NOTE: CrushMemoryPoolMgr: platform and memory (CPU MemSize:2048), adjusted allocating size to 262144 for CStripes
02/08/13-15:25:18 (tRAID): SOD: Instantiation Phase Complete
02/08/13-15:25:18 (tRAID): WARN: sodLockdownCheck: sodSequence update: CtlrLockdown
02/08/13-15:25:18 (tRAID): WARN: No attempt made to open Inter-Controller Communication Channels 0-0
02/08/13-15:25:18 (tRAID): NOTE: LockMgr Role is Master
02/08/13-15:25:18 (IOSched): NOTE: SAS Expander Added: expDevHandle:x11 enclHandle:x2 numPhys:25 port:2 ioc:0 channel:0 numEntries:22
02/08/13-15:25:19 (tSasExpChk): NOTE: Local Expander Firmware Version: 00.00.80.10
02/08/13-15:25:27 (tSasDiscCom): NOTE: SAS: Initial Discovery Complete Time: 39 seconds since last power on/reset, 10 seconds since sas instantiated
02/08/13-15:25:27 (tRAID): NOTE: WWN baseName 000690b1-1c201495 (valid==>SigMatch)
02/08/13-15:25:27 (tRAID): NOTE: spmEarlyData: No data available
02/08/13-15:25:27 (tRAID): SOD: Pre-Initialization Phase Complete
02/08/13-15:25:29 (utlTimer): NOTE: fcnChannelReport ==> -2 -3 -4 -5
02/08/13-15:25:34 (utlTimer): NOTE: fcnChannelReport ==> =2 =3 =4 =5
0xed4d18 (tNetCfgInit): miiPhyInit check cable connection
02/08/13-15:25:42 (tNetCfgInit): NOTE: eth0: LinkDown event
02/08/13-15:25:43 (tNetCfgInit): NOTE: Network Ready
02/08/13-15:25:50 (tRAID): NOTE: DB Adoption: DsmOK:1 MultDB:0 OneDbBadSqN:0 Allow:1 Adopted:1
02/08/13-15:25:52 (tRAID): WARN: CmgrLockdownException: CORRUPT DBM DATABASE DETECTED - LOCKDOWN Type=6
02/08/13-15:25:52 (tRAID): NOTE: ACS: Icon ping to alternate failed: -2, resp: 0
02/08/13-15:25:52 (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 0
02/08/13-15:25:52 (tRAID): WARN: ACS: autoCodeSync(): Skipped since alt not communicating.
02/08/13-15:25:52 (tRAID): SOD: Code Synchronization Initialization Phase Complete
02/08/13-15:25:52 (tRAID): WARN: Lockdown case-DB CORRUPT. NVPS did not update from Sstor.
02/08/13-15:25:53 (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
==============================================
02/08/13-15:25:53 (tRAID): NOTE: SYMbol available
02/08/13-15:25:53 (tRAID): WARN: *********************************************************
02/08/13-15:25:53 (tRAID): WARN: *********************************************************
02/08/13-15:25:53 (tRAID): WARN: ** **
02/08/13-15:25:53 (tRAID): WARN: ** WARNING!!!!!! **
02/08/13-15:25:53 (tRAID): WARN: ** **
02/08/13-15:25:53 (tRAID): WARN: ** This controller is locked down due to detected **
02/08/13-15:25:53 (tRAID): WARN: ** corruption in the primary database. **
02/08/13-15:25:53 (tRAID): WARN: ** In order to prevent any configuration loss, the **
02/08/13-15:25:53 (tRAID): WARN: ** backed up database must be restored. **
02/08/13-15:25:53 (tRAID): WARN: ** **
02/08/13-15:25:53 (tRAID): WARN: ** **
02/08/13-15:25:53 (tRAID): WARN: *********************************************************
02/08/13-15:25:53 (tRAID): WARN: *********************************************************
02/08/13-15:25:53 (tRAID): SOD: sodComplete Notification Complete
02/08/13-15:25:55 (tRAID): sodMain CtlrLockdown sequence finished, elapsed time = 42 seconds
02/08/13-15:25:55 (tRAID): sodMain complete
02/08/13-15:25:54 (tRAID): WARN: SOD lockdown sequence complete - suspending...
DELL-Sam L
Moderator
Moderator
•
6.9K Posts
0
February 8th, 2013 12:00
Hello rxtx256,
I suggest that you contact our support as they will need to reset the system. If support can’t get the system to reset then they will need to take a deeper look into the MD & see what is going on.
Please let us know if you have any other questions.
Kanat Taipakhov
1 Message
0
October 3rd, 2017 03:00
We have the same issue with MD3820i. We replaced all 600Gb 10k disks with 600Gb 15k disks.
We tried SMCli with "clear storageArray configuration all" and "clear storageArray recoveryMode" but we got "Error 1026 - The command issued to the storage array did not complete because the current RAID controller module firmware does not support this function."
Title: Disk Array Controller
Copyright 2013-2014 NetApp, Inc. All Rights Reserved.
Name: RC
Version: 08.10.08.60
Date: 05/23/2014
Time: 12:08:59 CDT
Models: 2701
Manager: devmgr.v1110api36.Manager
==============================================
10/03/17-09:06:13 (tRAID): NOTE: SYMbol available
10/03/17-09:06:13 (tRAID): WARN: *********************************************************
10/03/17-09:06:13 (tRAID): WARN: *********************************************************
10/03/17-09:06:13 (tRAID): WARN: ** **
10/03/17-09:06:13 (tRAID): WARN: ** WARNING!!!!!! **
10/03/17-09:06:13 (tRAID): WARN: ** **
10/03/17-09:06:13 (tRAID): WARN: ** This controller is locked down due to detected **
10/03/17-09:06:13 (tRAID): WARN: ** corruption in the primary database. **
10/03/17-09:06:13 (tRAID): WARN: ** In order to prevent any configuration loss, the **
10/03/17-09:06:13 (tRAID): WARN: ** backed up database must be restored. **
10/03/17-09:06:13 (tRAID): WARN: ** **
10/03/17-09:06:13 (tRAID): WARN: ** **
10/03/17-09:06:13 (tRAID): WARN: *********************************************************
10/03/17-09:06:13 (tRAID): WARN: *********************************************************
10/03/17-09:06:33 (tRAID): WARN: RPM: Timeout expired waiting for Response - msg 36 devnum 0x00f00011
10/03/17-09:06:33 (tRAID): ERROR: BackupDatabaseManager:getAltRecordBackup: Exception TimeoutForResponseException Error
10/03/17-09:06:53 (tRAID): WARN: RPM: Timeout expired waiting for Response - msg 37 devnum 0x00f00011
10/03/17-09:07:13 (tRAID): WARN: RPM: Timeout expired waiting for Response - msg 38 devnum 0x00f00011
10/03/17-09:07:13 (tRAID): SOD: sodComplete Notification Complete
10/03/17-09:07:13 (tRAID): sodMain CtlrLockdown sequence finished, elapsed time = 670 seconds
10/03/17-09:07:13 (tRAID): sodMain complete
10/03/17-09:07:13 (tRAID): WARN: SOD lockdown sequence complete - suspending...
What the solution for this issue?
DELL-Sam L
Moderator
Moderator
•
6.9K Posts
0
October 5th, 2017 11:00
Hello Kanat Taipakhov,
When you replaced all the drives did you remove all disk groups, virtual disks & host access before you removed the HDD from your MD3820i? If you didn’t then that is why you are getting this error. The error is due to your MD3820i looking for the virtual disk information, and not finding the matching information on your drives. So to prevent any data loss it locks down the controller to ensure that there is no further corruption.
If you still have the old drives you can insert them back into your MD3820i, and then remove the virtual disk, host access, & disk group information. Once that is done then you can swap the drives back to the 15K & recreate your setup again.
Please let us know if you have any other questions.