Skip to main content
Start a Conversation

Unsolved

Bruce Ferrell

3 Posts

761

February 24th, 2020 17:00

MD3000i unable to boot after battery change

Controller 1 seems failed; Hangs at:

-=<###>=-
Attaching interface lo0... done

Adding 9767 symbols for standalone.

Controller 0 shows:

Error
02/25/20-00:31:32 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00

Send for Service Interface or baud rate change
02/25/20-00:31:51 (GMT) (tRAID): NOTE: Set Powerup State
02/25/20-00:31:51 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
02/25/20-00:31:51 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
02/25/20-00:31:51 (GMT) (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBase = 0x0
02/25/20-00:31:51 (GMT) (tRAID): NOTE: Turning on tray summary fault LED
02/25/20-00:31:53 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
02/25/20-00:31:53 (GMT) (tRAID): NOTE: lost persistent dq data because buffer was modified or size changed.
esmc0: LinkUp event

02/25/20-00:31:54 (GMT) (tNetCfgInit): NOTE: Network Ready
02/25/20-00:31:57 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
02/25/20-00:31:59 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-63-00
02/25/20-00:32:07 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:0 prevNumActivePhys:2 numActivePhys:2
02/25/20-00:32:07 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:1 prevNumActivePhys:2 numActivePhys:2
02/25/20-00:32:17 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
02/25/20-00:32:17 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
02/25/20-00:32:17 (GMT) (tRAID): WARN: No attempt made to open Inter-Controller Communication Channels
02/25/20-00:32:17 (GMT) (tRAID): NOTE: LockMgr Role is Master
02/25/20-00:32:17 (GMT) (tRAID): WARN: FBM:validateSubModel: Exception - Alt controller not ready
02/25/20-00:32:17 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
02/25/20-00:32:18 (GMT) (tRAID): NOTE: spmEarlyData: No data available
02/25/20-00:32:23 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
02/25/20-00:32:47 (GMT) (sasCheckExpanderSet): WARN: sasCheckExpanderSetup: No bus target for local expander available for 30 seconds after sasChannelInitia
lize
02/25/20-00:33:53 (GMT) (tRAID): NOTE: WWN baseName 000a842b-2b5899eb (valid==>NoPrevAlt)
02/25/20-00:33:53 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
02/25/20-00:33:53 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
02/25/20-00:33:54 (GMT) (tRAID): WARN: BID: initialize(): Power latched!
02/25/20-00:34:08 (GMT) (tRAID): WARN: dbm::RWFileSystem::initialize: Exception caught, ConstructorIOException: -16
02/25/20-00:34:08 (GMT) (tRAID): WARN: Exception caught in intentLogStartOfDay, DbmNoFileSystemException: recType: 11
02/25/20-00:34:10 (GMT) (tRAID): WARN: DbmNoFileSystemException: recType: 59 Line 1375 File cmgrControllerMgr.cc
02/25/20-00:34:10 (GMT) (tRAID): WARN: DbmNoFileSystemException: recType: 34 Line 605 File cmgrControllerMgr.cc
02/25/20-00:34:10 (GMT) (tRAID): NOTE: ACS: Icon ping to alternate failed: -2, resp: 0
02/25/20-00:34:10 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 0
02/25/20-00:34:10 (GMT) (tRAID): WARN: ACS: autoCodeSync(): Skipped since alt not communicating.
02/25/20-00:34:10 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
02/25/20-00:34:10 (GMT) (tRAID): NOTE: Caught IconSendInfeasibleException Error in iop::requestAltIopDelay
02/25/20-00:34:10 (GMT) (tRAID): NOTE: CheckInMonitor: Check-in failed (IconSendInfeasibleException Error)
02/25/20-00:34:10 (GMT) (tRAID): WARN: USM Exception caught in processUsmHeader - DbmNoFileSystemException: recType: 30
02/25/20-00:34:10 (GMT) (tRAID): WARN: USM Error allocating UsmStableStorageHeader in processUsmHeader() - DbmNoFileSystemException: recType: 30
02/25/20-00:34:10 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
02/25/20-00:34:10 (GMT) (tRAID): NOTE: SOD failure in evf::VolumeCfgManager::initialize
02/25/20-00:34:10 (GMT) (tRAID): NOTE: DbmNoFileSystemException in evf::VolExtentMgr::initialize
02/25/20-00:34:10 (GMT) (tRAID): WARN: Received IconSendInfeasibleException Error adding small edr records from alt controller
02/25/20-00:34:10 (GMT) (tRAID): WARN: edrSOD: No Config File System

02/25/20-00:34:10 (GMT) (tRAID): NOTE: DbmNoFileSystemException in safe::initialize
02/25/20-00:34:10 (GMT) (tRAID): WARN: snrProcessDatabase: No File System Found
02/25/20-00:34:10 (GMT) (tRAID): WARN: spm: unable to exchange features, assuming none
02/25/20-00:34:10 (GMT) (tRAID): WARN: spm::SPMManager::initialize NoFileSystem
02/25/20-00:34:10 (GMT) (tRAID): NOTE: sas: Peering Disabled (Alt Unavailable)
02/25/20-00:34:10 (GMT) (tRAID): ERROR: CopyTargetname: target name length = 0
02/25/20-00:34:10 (GMT) (tRAID): WARN: ConfigManager::processArrayDatabase, No Config File System
02/25/20-00:34:10 (GMT) (tRAID): WARN: ConfigManager::processPortDatabase, No Config File System
02/25/20-00:34:10 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0
02/25/20-00:34:11 (GMT) (NvpsPersistentSyncM): WARN: nvps Exception DbmNoFileSystemException: recType: 19 Line 354 File nvpsPersistentSyncMgr.cc
02/25/20-00:34:11 (GMT) (NvpsPersistentSyncM): WARN: nvps Exception DbmNoFileSystemException: recType: 19 Line 354 File nvpsPersistentSyncMgr.cc
02/25/20-00:34:11 (GMT) (NvpsPersistentSyncM): WARN: nvps Exception DbmNoFileSystemException: recType: 19 Line 354 File nvpsPersistentSyncMgr.cc
02/25/20-00:34:38 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
02/25/20-00:34:38 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
02/25/20-00:34:38 (GMT) (tRAID): NOTE: Qlogic coredump file written to 'host:/tmp/QLogic_Coredump_port_0_3L97WD1',rc 204E50, expected 204E50
02/25/20-00:34:38 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1

02/25/20-00:34:38 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
02/25/20-00:34:38 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
02/25/20-00:34:38 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State 4543
02/25/20-00:34:38 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
02/25/20-00:34:40 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c2e0 4c0c8 bytes , result 0
02/25/20-00:35:07 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
02/25/20-00:35:07 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
02/25/20-00:35:08 (GMT) (tRAID): NOTE: Qlogic coredump file written to 'host:/tmp/QLogic_Coredump_port_0_3L97WD1',rc 204E50, expected 204E50
02/25/20-00:35:08 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1

02/25/20-00:35:08 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
02/25/20-00:35:08 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
02/25/20-00:35:08 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State 4543
02/25/20-00:35:08 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed

Eventually the management IP comes available, but SMClient shows unresponsive

Suggestions?

 

 

Bruce Ferrell

3 Posts

February 25th, 2020 12:00

Based on my reading, I'd come to that conclusion.

I tried the "send break and log into sysuser to access the menu"  but I didn't get the four option menu.

My question re: syswipe is, will that allow me to recover the RAID?

DellEMCSupport

631 Posts

February 25th, 2020 12:00

Hello Bruce Ferrell,

Based on the output that you posted your controller is bad.  You can try to do a syswipe on the controller and it may boot afterwards.  A syswipe is normally done by a Dell technician, however due to the age of this system I am guessing that it is no longer has a support contract.  Also, by doing a syswipe on a controller if done incorrectly can harm your system. 

Please let us know if you have any other questions.

DellEMCSupport

631 Posts

February 25th, 2020 13:00

Hello Bruce Ferrell,

If you can’t access the sysuser on that controller then the controller is dead & needs to be replaced.  When you do a syswipe it erases the configuration on the controller & resets the controller back to factory settings.  When a controller can’t be reset or get into the sysuser account it is dead.

Please let us know if you have any other questions.

Was this post helpful?

View All

No Events found!

Top