Unsolved
This post is more than 5 years old
7 Posts
0
1217
August 15th, 2018 13:00
MD3000i controller troubles
Dear I'm getting this error on my controller when I connected the cable on the console what could it be?
-=<###>=-
Attaching interface lo0... done
Adding 9767 symbols for standalone.
08/15/18-18:04:29 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
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
5900 Ethernet 91c111 #1
01 Register read Passed
02 Register test Passed
3A00 NAND Flash
06 Bad Blocks Test Passed
2310 Application Accelerator Unit
01 AAU Register Test Passed
6D00 LSI SAS 1068 IOC--Base Board
01 IOC Register Read Test Passed
02 IOC Register Address Lines Test Passed
03 IOC Register Data Lines Test Passed
6F01 QLOGIC EP4032 CHIP 0
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.
^B
Current date: 08/15/18 time: 09:26:51
Send for Service Interface or baud rate change
08/15/18-18:04:53 (GMT) (tRAID): NOTE: Set Powerup State
08/15/18-18:04:53 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
08/15/18-18:04:53 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
08/15/18-18:04:53 (GMT) (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBase = 0x0
08/15/18-18:04:53 (GMT) (tRAID): NOTE: Turning on tray summary fault LED
08/15/18-18:04:55 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
08/15/18-18:04:55 (GMT) (tRAID): NOTE: lost persistent dq data because buffer was modified or size changed.
esmc0: LinkUp event
08/15/18-18:04:56 (GMT) (tNetCfgInit): NOTE: Network Ready
08/15/18-18:04:59 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
08/15/18-18:05:02 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-63-00
08/15/18-18:05:11 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
08/15/18-18:05:11 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
08/15/18-18:05:11 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
08/15/18-18:05:12 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
08/15/18-18:05:12 (GMT) (tSasCfg013): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
08/15/18-18:05:12 (GMT) (tSasCfg021): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
08/15/18-18:05:18 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 1,devHandle: x17, SAS Address: 5b8ac6f40f939101
08/15/18-18:05:18 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 0,devHandle: x25, SAS Address: 5b8ac6f40f939100
08/15/18-18:05:18 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
08/15/18-18:05:18 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
08/15/18-18:05:18 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
08/15/18-18:05:18 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
08/15/18-18:05:18 (GMT) (tRAID): NOTE: LockMgr Role is Slave
08/15/18-18:05:18 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
08/15/18-18:05:18 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x5842b2b4 Low = x4019f910
08/15/18-18:05:19 (GMT) (tRAID): NOTE: spmEarlyData: No data available
08/15/18-18:05:25 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
08/15/18-18:05:25 (GMT) (tRAID): NOTE: WWN baseName 0006b8ac-6f0f9391 (valid==>SigMatch)
08/15/18-18:05:25 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
08/15/18-18:05:25 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
08/15/18-18:05:26 (GMT) (tRAID): WARN: BID: initialize(): Power latched!
08/15/18-18:05:33 (GMT) (IOSched): WARN: SSM: Start Unit to Devnum 0x00010009 FAILED (error: 2)! Drive will not be available
08/15/18-18:05:33 (GMT) (IOSched): WARN: SSM: Start Unit to Devnum 0x0001000b FAILED (error: 2)! Drive will not be available
08/15/18-18:05:39 (GMT) (iacTask4): NOTE: ACS: Acs Needed on Alt: No, StateCode: 0, ReasonCode = 2
08/15/18-18:05:39 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
08/15/18-18:05:39 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
08/15/18-18:05:40 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
08/15/18-18:05:41 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
08/15/18-18:05:41 (GMT) (tRAID): NOTE: EDR - recieved 1 small records
08/15/18-18:05:41 (GMT) (tRAID): NOTE: EDR - recieved 0 large records
08/15/18-18:05:42 (GMT) (tRAID): NOTE: Acquire 0.016 secs
08/15/18-18:05:44 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c380 4c0c8 bytes , result 0
08/15/18-18:06:12 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
08/15/18-18:06:12 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
08/15/18-18:06:12 (GMT) (tRAID): NOTE: Qlogic coredump file written to '6Q29JN1:/tmp/QLogic_Coredump_port_0_6Q29JN1',rc 204E50, expected 204E50
08/15/18-18:06:12 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
08/15/18-18:06:12 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
08/15/18-18:06:12 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
08/15/18-18:06:12 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State 4543
08/15/18-18:06:12 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
08/15/18-18:06:14 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c380 4c0c8 bytes , result 0
08/15/18-18:06:41 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
08/15/18-18:06:41 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
08/15/18-18:06:42 (GMT) (tRAID): NOTE: Qlogic coredump file written to '6Q29JN1:/tmp/QLogic_Coredump_port_0_6Q29JN1',rc 204E50, expected 204E50
08/15/18-18:06:42 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
08/15/18-18:06:42 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
08/15/18-18:06:42 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
08/15/18-18:06:42 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State 4543
08/15/18-18:06:42 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
08/15/18-18:06:43 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c380 4c0c8 bytes , result 0
08/15/18-18:07:10 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
08/15/18-18:07:10 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
08/15/18-18:07:11 (GMT) (tRAID): NOTE: Qlogic coredump file written to '6Q29JN1:/tmp/QLogic_Coredump_port_0_6Q29JN1',rc 204E50, expected 204E50
08/15/18-18:07:11 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
08/15/18-18:07:11 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
08/15/18-18:07:11 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
08/15/18-18:07:11 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State 4543
08/15/18-18:07:11 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
08/15/18-18:07:12 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c380 4c0c8 bytes , result 0
08/15/18-18:07:39 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
08/15/18-18:07:39 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
08/15/18-18:07:40 (GMT) (tRAID): NOTE: Qlogic coredump file written to '6Q29JN1:/tmp/QLogic_Coredump_port_0_6Q29JN1',rc 204E50, expected 204E50
08/15/18-18:07:40 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
08/15/18-18:07:40 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
08/15/18-18:07:40 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
08/15/18-18:07:40 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State 4543
08/15/18-18:07:40 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
08/15/18-18:07:41 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c380 4c0c8 bytes , result 0
08/15/18-18:08:09 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
08/15/18-18:08:09 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
08/15/18-18:08:09 (GMT) (tRAID): NOTE: Qlogic coredump file written to '6Q29JN1:/tmp/QLogic_Coredump_port_0_6Q29JN1',rc 204E50, expected 204E50
08/15/18-18:08:09 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
08/15/18-18:08:09 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
08/15/18-18:08:09 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
08/15/18-18:08:09 (GMT) (tRAID): NOTE: QLRebootTimer: Status after Get FW State 4543
08/15/18-18:08:09 (GMT) (tRAID): NOTE: QLRebootTimer: QLGetFwState failed
08/15/18-18:08:10 (GMT) (tRAID): WARN: QLStartAdapter: ControllerErrorCount exceeds threshold.
08/15/18-18:08:10 (GMT) (tRAID): ERROR: QLInitializeDevice: QLStartAdapter failed
08/15/18-18:08:10 (GMT) (tRAID): ERROR: QLAddDevice: controller/device/chip initialization failed.
08/15/18-18:08:10 (GMT) (tRAID): ERROR: qlgEnableHostInterface: QLInitializeDevice failed.
08/15/18-18:08:55 (GMT) (tRAID): NOTE: Scsicon error status fe received.
08/15/18-18:08:55 (GMT) (tRAID): WARN: sendTaskLockMsg: Error or Infeasible message status=ffffffff
08/15/18-18:08:55 (GMT) (tRAID): NOTE: LockMgr Role is Master
08/15/18-18:08:55 (GMT) (tRAID): WARN: Alt Ctl Reboot:
Reboot CompID: 0x401
Reboot reason: 0x9
Reboot reason extra: 0x0
08/15/18-18:08:55 (GMT) (tRAID): NOTE: holding alt ctl in reset
08/15/18-18:08:56 (GMT) (tRAID): NOTE: releasing alt ctl from reset
08/15/18-18:08:56 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
08/15/18-18:08:56 (GMT) (tRAID): NOTE: sas: Peering Disabled (Health Check) Event: -1
08/15/18-18:08:57 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 0, devHandle: x25, I/O: 0, SAS Address: 5b8ac6f40f939100
08/15/18-18:08:57 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 00020025
08/15/18-18:08:57 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
08/15/18-18:08:57 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 1, devHandle: x17, I/O: 0, SAS Address: 5b8ac6f40f939101
08/15/18-18:08:57 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 00020017
08/15/18-18:08:57 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
08/15/18-18:08:57 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
08/15/18-18:08:57 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
08/15/18-18:08:57 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
08/15/18-18:08:57 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
08/15/18-18:08:57 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
08/15/18-18:08:57 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
08/15/18-18:08:57 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
08/15/18-18:08:57 (GMT) (tRAID): NOTE: ********************************************************************************
08/15/18-18:08:57 (GMT) (tRAID): NOTE: QLogic Target Application, Version 2.01.08 6-13-2005 (W2K)
08/15/18-18:08:57 (GMT) (tRAID): NOTE: iSCSI Target Application
08/15/18-18:08:57 (GMT) (tRAID): NOTE: ********************************************************************************
Exception: Data Abort
cpsr: 60000013 pc: 0x0020eb
0 events found


DELL-Chris H
Moderator
•
9.7K Posts
0
August 17th, 2018 06:00
Rhudy,
The issue/error you are seeing was previously addressed in the posting found here, it includes information and possible steps/causes. It does appear that normally this is due to an issue with the controller. Please review the posting and let us know what you see.