Unsolved
This post is more than 5 years old
7 Posts
0
69658
MD3000i - RAM Parity error
Hello,
Service tag# 14610001789
Red light on the front, iSCSI ports on one controller keep turning off, and when they're on, just the link light, no activity. Tried forcing it over to the primary by unplugging the secondary iSCSI cables (while it was off, then starting it up like that), but still no activity.
Connecting through telnet, it seems our primary controller is facing a RAM parity error, which is subsequently causing a port failure, and the secondary controller is resetting the primary. This is looping.
Curious to know if I can just purchase some new RAM (and what type of RAM it requires), or if the controller itself needs to be replaced?
Thanks,
--TacoBot
DELL-Sam L
Moderator
Moderator
•
7.1K Posts
0
December 1st, 2015 13:00
Hello TacoBot,
What we will need is to look at the boot up of the controller to see what is going on. To do that if you can do a serial capture we can look to see if it is an issue that requires the ram or the controller to be replaced. Here is how to do the serial capture:
1. Startup a terminal emulation program like putty, teraterm, minicom or hyperterminal using these terminal settings (115200-8-n-1).
2. Start the capture text in your Terminal emulation.
3. Pull the controller that you are connected to out for about 30 seconds and then insert it & you should start to see the text of the controller booting up
4. Wait for the message to start repeating & once it is repeating then you can stop the connection & text capture.
Please let us know if you have any other questions.
TacoBot
7 Posts
0
December 2nd, 2015 16:00
Hi, thanks for the reply. Please see below -- I let it do one complete loop after it was reset by the other controller again.
--------------------------------
-=<###>=-
Attaching interface lo0... done
Adding 9768 symbols for standalone.
Error
12/02/15-23:45:50 (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.
Current date: 12/02/15 time: 15:17:40
LSI Logic RAID Controller
Copyright 2005-2011, LSI Logic Corporation. All Rights Reserved.
Copyright 1984-2006 Wind River Systems, Inc.
VxWorks: VxWorks 6.4 Kernel: WIND version 2.10
Model: 1532 Firmware version: 07.35.39.64
12/02/15-23:46:09 (GMT) (tRAID): NOTE: Set Powerup State
12/02/15-23:46:09 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
12/02/15-23:46:09 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
Serial Port shell started.
-> 12/02/15-23:46:09 (GMT) (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBase = 0x0
12/02/15-23:46:09 (GMT) (tRAID): NOTE: Turning on tray summary fault LED
esmc0: Link change detected, LinkDown may take a long time to detect
12/02/15-23:46:11 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
0x36d600 (tNetTask): esmc0: LinkUp event
12/02/15-23:46:14 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
12/02/15-23:46:15 (GMT) (tNetCfgInit): NOTE: Network Ready
12/02/15-23:46:17 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-63-00
12/02/15-23:46:26 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:0 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:46:26 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:1 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:46:27 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:2 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:46:27 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:3 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:46:27 (GMT) (tSasCfg016): NOTE: Alt Controller path up - chan:0 phy:18 itn:1
12/02/15-23:46:27 (GMT) (tSasCfg021): NOTE: Alt Controller path up - chan:1 phy:16 itn:2
12/02/15-23:46:36 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
12/02/15-23:46:37 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
12/02/15-23:46:37 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
12/02/15-23:46:37 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
12/02/15-23:46:37 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 1,devHandle: x2b, SAS Address: 50022194b4a81800
12/02/15-23:46:37 (GMT) (tRAID): NOTE: LockMgr Role is Slave
12/02/15-23:46:37 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
12/02/15-23:46:37 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x50026b94 Low = x37541b10
12/02/15-23:46:37 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
12/02/15-23:46:41 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 29 seconds
12/02/15-23:46:41 (GMT) (tRAID): NOTE: WWN baseName 00040022-19b4a83b (valid==>SigMatch)
12/02/15-23:46:41 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
12/02/15-23:46:42 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
12/02/15-23:46:42 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
12/02/15-23:46:42 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
12/02/15-23:46:57 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
12/02/15-23:46:57 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
12/02/15-23:46:58 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
12/02/15-23:46:58 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
12/02/15-23:46:59 (GMT) (tRAID): NOTE: EDR - recieved 1 small records
12/02/15-23:46:59 (GMT) (tRAID): NOTE: EDR - recieved 0 large records
12/02/15-23:47:00 (GMT) (tRAID): NOTE: Acquire 0.020 secs
12/02/15-23:47:01 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 0058c3a0 4c0c8 bytes , result 0
12/02/15-23:47:03 (GMT) (tRAID): NOTE: ********************************************************************************
12/02/15-23:47:03 (GMT) (tRAID): NOTE: QLogic Target Application, Version 2.01.08 6-13-2005 (W2K)
12/02/15-23:47:03 (GMT) (tRAID): NOTE: iSCSI Target Application
12/02/15-23:47:03 (GMT) (tRAID): NOTE: ********************************************************************************
12/02/15-23:47:04 (GMT) (tRAID): NOTE: QLInitializeFW: iSNS Server 0.0.0.0:3205
12/02/15-23:47:04 (GMT) (tRAID): NOTE: QLInitializeFW: ISNSServerIPv6Addr 00:00:00:00:00:00:00:00 :3205
12/02/15-23:47:04 (GMT) (tRAID): NOTE: QLInitializeFW: iSCSI Name iqn.1984-05.com.dell:powervault.6002219000b4a83b00000000497acd71
12/02/15-23:47:04 (GMT) (tRAID): NOTE: QLInitializeFW: port = 0, IPv4 Enable = 1, IPv6 Enable = 0
12/02/15-23:47:04 (GMT) (tRAID): NOTE: QLInitializeFW: IP Address 192.168.130.101:3260
12/02/15-23:47:04 (GMT) (tRAID): NOTE: QLInitializeFW: Firmware waiting for DHCP lease. State 18
12/02/15-23:47:04 (GMT) (tRAID): NOTE: QLInitializeFW: Time 000/010 FwState 18
12/02/15-23:47:05 (GMT) (tRAID): NOTE: QLInitializeFW: Time 001/010 FwState 18
12/02/15-23:47:06 (GMT) (tRAID): NOTE: QLInitializeFW: Time 002/010 FwState 18
12/02/15-23:47:06 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Port 0 Link up.
12/02/15-23:47:07 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Async Event Code 8002 received
12/02/15-23:47:07 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: PortFatal interrupt. PortFatalErrorStatus 00002000 CSR 0000c508 AS 2 AF 800001
12/02/15-23:47:07 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: Local RAM Parity Fatal Error occured
12/02/15-23:47:07 (GMT) (IOSched): NOTE: QLProcessSystemError: Restart RISC
12/02/15-23:47:32 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
12/02/15-23:47:32 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
12/02/15-23:47:32 (GMT) (tRAID): NOTE: Qlogic coredump file written to 'host:/tmp/QLogic_Coredump_port_0_6PMF1J1',rc 204E50, expected 204E50
12/02/15-23:47:32 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
12/02/15-23:47:32 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
12/02/15-23:47:32 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
12/02/15-23:47:32 (GMT) (tRAID): WARN: QLInitializeFW: QLGetFwState failed.
12/02/15-23:47:32 (GMT) (tRAID): NOTE: QLInitializeAdapter: QLInitializeFW failed
12/02/15-23:47:32 (GMT) (tRAID): ERROR: QLEnable: Enable lun error
12/02/15-23:47:57 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0026, completion timeout
12/02/15-23:47:57 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x26
12/02/15-23:47:58 (GMT) (tRAID): NOTE: Qlogic coredump file written to 'host:/tmp/QLogic_Coredump_port_0_6PMF1J1',rc 204E50, expected 204E50
12/02/15-23:47:58 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
12/02/15-23:47:58 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
12/02/15-23:47:58 (GMT) (tRAID): NOTE: QLInitializeAdapter: MBOX_CMD_GET_FLASH f000. Unable to check MAC
12/02/15-23:47:58 (GMT) (tRAID): ERROR: QLEnable: Enable lun error
Exception: Reset
cpsr: 60000013 (Unknown Program Counter)
Registers:
r0 = 0 r1 = 34c52b8 r2 = 34c52b8 r3 = 0
r4 = 1d5b442 r5 = 1 r6 = 379f298 r7 = 0
12/02/15-23:47:58 (GMT) (t5): WARN: QLUtmEventNotify: pDevExt 31ce53c port 1 Event code 8002 pUtmTaGetTeb is null.
r8 = 400 r9 = 400 r10 = 33d7730 r11/fp = 1d90dc0
r12/ip = 1 r13/sp = 1d90d84 r14/lr = 6f8afc pc = 0
cpsr = 60000013
Stack Trace:
======== STACK SHOW ========
Showing for task id = 0x1d912a0 (tRAID), Running
FP=0x1d90dc0, SP=0x1d90d84, PC=0x0
Current executing task id = 0x1d912a0 (tRAID); not interrupted
Frame Ptr Ret Addr Return Name + Offset Called Name + Offset
========== ========== ================================ ========================
0x1d91270 0x0019f9c0 vxTaskEntry + 0x14 [fuzzy]
0x1d91268 0x0019f9c0 vxTaskEntry + 0x14 sodMain
0x1d911f4 0x0078bb88 sodMain + 0x1c8 _Z17sodInitializationv
0x1d911e4 0x0078abb8 _Z17sodInitializationv + 0x18 _Z32sodInitializeApplicationServicesv
0x1d911d4 0x0078a958 _Z32sodInitializeApplicationServicesv + 0xb8 _Z13sodLogStartupPFvvE
0x1d91078 0x0078a490 _Z13sodLogStartupPFvvE + 0xb0 _ZN3ion10initializeEv
0x1d91014 0x00c4d6bc _ZN3ion10initializeEv + 0x7c _ZN3ion10IonManager10initializeEv
0x1d90f94 0x00c1c1f8 _ZN3ion10IonManager10initializeEv + 0x438 _ZN5b_isn19IscsiNetworkManager10initializeEv
0x1d90e14 0x0068d3fc _ZN5b_isn19IscsiNetworkManager10initializeEv + 0x4fc QLTA_Main
0x1d90dc8 0x0066f638 QLTA_Main + 0x238 QLBM_RegisterImmDataBufs
0x1d90db4 0x006f8d90 QLBM_RegisterImmDataBufs + 0x30 QLBM_Register4032ImmDataBufs
Note: At least one "[fuzzy]" is indicated. A fuzzy frame entry is not a true
stack frame; rather, an address within VxWorks code space was found in the
stack, but it may not be a legitimate entry in the call list (or it may be).
Error in task 0x1d912a0: Bad stack pointer (sp=0x1d9216c)
********
Task Id: 0x1d912a0
Name: "tRAID"
Status: 0x00 (ready)
Options: 0x9001 (suprvsr)
Priority: 125
Stack base: 0x1d912a0
Stack end: 0x1d8c2a0
Stack size: 0x5000 (20480)
Stack margin: 0x3264 (12900)
Stack limit: 0x1d8c2a0
Pend queue: 0x2e5c70
Last errno: 0x860002
-=<###>=-
Attaching interface lo0... done
Adding 9768 symbols for standalone.
Error
12/02/15-23:48:03 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
WARNING: Reset by alternate controller
Current date: 12/02/15 time: 15:19:52
LSI Logic RAID Controller
Copyright 2005-2011, LSI Logic Corporation. All Rights Reserved.
Copyright 1984-2006 Wind River Systems, Inc.
VxWorks: VxWorks 6.4 Kernel: WIND version 2.10
Model: 1532 Firmware version: 07.35.39.64
12/02/15-23:48:20 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
12/02/15-23:48:20 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
Serial Port shell started.
-> 12/02/15-23:48:20 (GMT) (tRAID): NOTE: In iscsiIOQLIscsiInitDq. iscsiIoFstrBase = 0x0
12/02/15-23:48:20 (GMT) (tRAID): NOTE: Turning on tray summary fault LED
esmc0: Link change detected, LinkDown may take a long time to detect
12/02/15-23:48:22 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
0x36d600 (tNetTask): esmc0: LinkUp event
12/02/15-23:48:25 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
12/02/15-23:48:26 (GMT) (tNetCfgInit): NOTE: Network Ready
12/02/15-23:48:28 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-63-00
12/02/15-23:48:37 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:0 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:48:37 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:1 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:48:38 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:2 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:48:38 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:3 prevNumActivePhys:2 numActivePhys:2
12/02/15-23:48:38 (GMT) (tSasCfg016): NOTE: Alt Controller path up - chan:0 phy:18 itn:1
12/02/15-23:48:38 (GMT) (tSasCfg021): NOTE: Alt Controller path up - chan:1 phy:16 itn:2
12/02/15-23:48:47 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
12/02/15-23:48:48 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
12/02/15-23:48:48 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
12/02/15-23:48:48 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
12/02/15-23:48:48 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 1,devHandle: x2b, SAS Address: 50022194b4a81800
12/02/15-23:48:48 (GMT) (tRAID): NOTE: LockMgr Role is Slave
12/02/15-23:48:48 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
12/02/15-23:48:48 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x50026b94 Low = x37541b10
12/02/15-23:48:48 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
12/02/15-23:48:52 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
12/02/15-23:48:52 (GMT) (tRAID): NOTE: WWN baseName 00040022-19b4a83b (valid==>SoftRst)
12/02/15-23:48:52 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
12/02/15-23:48:53 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
12/02/15-23:48:53 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
12/02/15-23:48:53 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
12/02/15-23:49:05 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
12/02/15-23:49:06 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
12/02/15-23:49:07 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
12/02/15-23:49:07 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
12/02/15-23:49:07 (GMT) (tRAID): NOTE: EDR - recieved 1 small records
12/02/15-23:49:07 (GMT) (tRAID): NOTE: EDR - recieved 0 large records
12/02/15-23:49:08 (GMT) (tRAID): NOTE: Acquire 0.020 secs
12/02/15-23:49:10 (GMT) (tRAID): NOTE: QLStartFw: Downloading Driver's FW image 03.00.01.47 from 03220880 4c0c8 bytes , result 0
12/02/15-23:49:12 (GMT) (tRAID): NOTE: ********************************************************************************
12/02/15-23:49:12 (GMT) (tRAID): NOTE: QLogic Target Application, Version 2.01.08 6-13-2005 (W2K)
12/02/15-23:49:12 (GMT) (tRAID): NOTE: iSCSI Target Application
12/02/15-23:49:12 (GMT) (tRAID): NOTE: ********************************************************************************
12/02/15-23:49:12 (GMT) (tRAID): NOTE: QLInitializeFW: iSNS Server 0.0.0.0:3205
12/02/15-23:49:12 (GMT) (tRAID): NOTE: QLInitializeFW: ISNSServerIPv6Addr 00:00:00:00:00:00:00:00 :3205
12/02/15-23:49:12 (GMT) (tRAID): NOTE: QLInitializeFW: iSCSI Name iqn.1984-05.com.dell:powervault.6002219000b4a83b00000000497acd71
12/02/15-23:49:12 (GMT) (tRAID): NOTE: QLInitializeFW: port = 0, IPv4 Enable = 1, IPv6 Enable = 0
12/02/15-23:49:12 (GMT) (tRAID): NOTE: QLInitializeFW: IP Address 192.168.130.101:3260
12/02/15-23:49:13 (GMT) (tRAID): NOTE: QLInitializeFW: Firmware waiting for DHCP lease. State 18
12/02/15-23:49:13 (GMT) (tRAID): NOTE: QLInitializeFW: Time 000/010 FwState 18
12/02/15-23:49:14 (GMT) (tRAID): NOTE: QLInitializeFW: Time 001/010 FwState 18
12/02/15-23:49:15 (GMT) (tRAID): NOTE: QLInitializeFW: Time 002/010 FwState 18
12/02/15-23:49:15 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Port 0 Link up.
12/02/15-23:49:16 (GMT) (tRAID): NOTE: QLInitializeFW: Time 003/010 FwState 0
12/02/15-23:49:16 (GMT) (tRAID): NOTE: QLInitializeFW: port = 1, IPv4 Enable = 1, IPv6 Enable = 0
12/02/15-23:49:16 (GMT) (tRAID): NOTE: QLInitializeFW: IP Address 192.168.131.101:3260
12/02/15-23:49:16 (GMT) (tRAID): NOTE: QLInitializeFW: Firmware waiting for DHCP lease. State 18
12/02/15-23:49:16 (GMT) (tRAID): NOTE: QLInitializeFW: Time 000/010 FwState 18
12/02/15-23:49:17 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Async Event Code 8002 received
12/02/15-23:49:17 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: PortFatal interrupt. PortFatalErrorStatus 00002000 CSR 0000d508 AS 2 AF 800001
12/02/15-23:49:17 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: Local RAM Parity Fatal Error occured
12/02/15-23:49:17 (GMT) (IOSched): NOTE: QLProcessSystemError: Restart RISC
12/02/15-23:49:17 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Async Event Code 8002 received
12/02/15-23:49:17 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: PortFatal interrupt. PortFatalErrorStatus 00002000 CSR 0000d708 AS 2 AF 800009
12/02/15-23:49:17 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: Local RAM Parity Fatal Error occured
12/02/15-23:49:17 (GMT) (IOSched): NOTE: QLProcessSystemError: Restart RISC
12/02/15-23:49:42 (GMT) (tRAID): WARN: QLMailboxCommand: Cmd = 0069, completion timeout
12/02/15-23:49:42 (GMT) (tRAID): WARN: QLMailboxCommand: command completion timeout, cmd = 0x69
12/02/15-23:49:43 (GMT) (tRAID): NOTE: Qlogic coredump file written to 'host:/tmp/QLogic_Coredump_port_0_6PMF1J1',rc 204E50, expected 204E50
12/02/15-23:49:43 (GMT) (tRAID): WARN: Qlogic coredump file write failed.fclose returned -1
12/02/15-23:49:43 (GMT) (tRAID): NOTE: QLProcessSystemError: Restart RISC
12/02/15-23:49:43 (GMT) (tRAID): ERROR: QLGetFwState: MBOX_CMD_GET_FW_STATE failed. Stat f000
12/02/15-23:49:43 (GMT) (tRAID): WARN: QLInitializeFW: QLGetFwState failed.
12/02/15-23:49:43 (GMT) (tRAID): NOTE: QLInitializeAdapter: QLInitializeFW failed
12/02/15-23:49:43 (GMT) (tRAID): ERROR: QLEnable: Enable lun error
Exception: Reset
cpsr: 60000013 (Unknown Program Counter)
Registers:
r0 = 012/02/15-23:49:43 (GMT) (t5): WARN: QLUtmEventNotify: pDevExt 31cf780 port 1 Event code 8002 pUtmTaGetTeb is null.
r1 = 3519688 r2 = 3519688 r3 = 0
r4 = 1bedde2 r5 = 2 r6 = 3885828 r7 = 0
r8 = 400 r9 = 400 r10 = 343d7c4 r11/fp = 1c23ba0
r12/ip = 1 r13/sp = 1c23b64 r14/lr = 58b49c pc = 0
cpsr = 60000013
Stack Trace:
======== STACK SHOW ========
Showing for task id = 0x1c24080 (tRAID), Running
FP=0x1c23ba0, SP=0x1c23b64, PC=0x0
Current executing task id = 0x1c24080 (tRAID); not interrupted
Frame Ptr Ret Addr Return Name + Offset Called Name + Offset
========== ========== ================================ ========================
0x1c24050 0x0019f9c0 vxTaskEntry + 0x14 [fuzzy]
0x1c24048 0x0019f9c0 vxTaskEntry + 0x14 sodMain
0x1c23fd4 0x0061e528 sodMain + 0x1c8 _Z17sodInitializationv
0x1c23fc4 0x0061d558 _Z17sodInitializationv + 0x18 _Z32sodInitializeApplicationServicesv
0x1c23fb4 0x0061d2f8 _Z32sodInitializeApplicationServicesv + 0xb8 _Z13sodLogStartupPFvvE
0x1c23e58 0x0061ce30 _Z13sodLogStartupPFvvE + 0xb0 _ZN3ion10initializeEv
0x1c23df4 0x00ae005c _ZN3ion10initializeEv + 0x7c _ZN3ion10IonManager10initializeEv
0x1c23d74 0x00aaeb98 _ZN3ion10IonManager10initializeEv + 0x438 _ZN5b_isn19IscsiNetworkManager10initializeEv
0x1c23bf4 0x0051fd9c _ZN5b_isn19IscsiNetworkManager10initializeEv + 0x4fc QLTA_Main
0x1c23ba8 0x00501fd8 QLTA_Main + 0x238 QLBM_RegisterImmDataBufs
0x1c23b94 0x0058b730 QLBM_RegisterImmDataBufs + 0x30 QLBM_Register4032ImmDataBufs
Note: At least one "[fuzzy]" is indicated. A fuzzy frame entry is not a true
stack frame; rather, an address within VxWorks code space was found in the
stack, but it may not be a legitimate entry in the call list (or it may be).
Error in task 0x1c24080: Bad stack pointer (sp=0x1c24f4c)
********
Task Id: 0x1c24080
Name: "tRAID"
Status: 0x00 (ready)
Options: 0x9001 (suprvsr)
Priority: 125
Stack base: 0x1c24080
Stack end: 0x1c1f080
Stack size: 0x5000 (20480)
Stack margin: 0x3264 (12900)
Stack limit: 0x1c1f080
Pend queue: 0x2e5c70
Last errno: 0x860002
-=<###>=-
Attaching interface lo0... done
Adding 9768 symbols for standalone.
Error
12/02/15-23:49:48 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
WARNING: Reset by alternate controller
DELL-Sam L
Moderator
Moderator
•
7.1K Posts
0
December 8th, 2015 13:00
Hello TacoBot,
Thanks for the Serial capture. Based on the error listed below the controller needs to be replaced as it has failed.
12/02/15-23:49:17 (GMT) (IOSched): NOTE: QLProcessSystemError: Restart RISC
12/02/15-23:49:17 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Async Event Code 8002 received
12/02/15-23:49:17 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: PortFatal interrupt. PortFatalErrorStatus 00002000 CSR 0000d708 AS 2 AF 800009
12/02/15-23:49:17 (GMT) (IOSched): ERROR: QLDoInterruptServiceRoutine: Local RAM Parity Fatal Error occurred
Please let us know if you have any other questions.
TacoBot
7 Posts
0
December 8th, 2015 14:00
Hi Sam,
So the entire controller, not just the RAM then?
Does Dell still have any of these new, or are they all what I can find on ebay, etc?
Thanks again for your help!
--TacoBot
DELL-Sam L
Moderator
Moderator
•
7.1K Posts
0
December 9th, 2015 10:00
Hello TacoBot,
Yes it is the entire controller. As we don’t sell just the ram to replace on the controller. No we don’t have any new controllers left so you would need to look at Ebay or 3rd party resellers that are selling the controllers.
Please let us know if you have any other questions.
TacoBot
7 Posts
0
December 9th, 2015 11:00
Hi Sam, I appreciate the replies, however if Dell doesn't have the controller anyways, and I need to go to eBay in any case, wouldn't it make sense to just find the RAM on eBay?
Based on the log, does it seem that the controller is only failing due to the ram parity check failing, or is that just a symptom of the controller processor or main board or some other component failing?
Used RAM that seems to match what's in there is dirt cheap, used controllers will run us $600+, so if we can get away with just replacing the RAM, why buy someone's expensive used controller?
From what I've gathered, this RAM should be the exact replacement:
SAMSUNG PC2700R-25331-A3 512MB DDR PC2700 CL2.5 ECC
Can you confirm if this is true? I'd rather take a $20 gamble on this than buying the controller.
Thanks again,
--TacoBot
TacoBot
7 Posts
0
December 21st, 2015 15:00
^ Bump?