Storage 2540
hello
we met an abnormal problem (continuously reboot) when inserting a SAS disk 300G 15.7K in a Storage 2540
have you seen this kind of problem?
thank you
Attached logs
10/01/14-01:25:02 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:25:02 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:25:02 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:25:02 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:25:02 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:25:02 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:25:03 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:25:03 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:25:04 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:25:04 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:25:04 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:25:06 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:25:06 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:25:09 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
10/01/14-01:25:10 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:25:10 (GMT) (tRAID): WARN: key already exists
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:25:14 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:00:19
hello NIK
thank you for your quick response
i haven't support contract actually
the problem appear only when inserting a SAS disk 300G 15.7K
I tried these disks in another storage 2540, but the same problem still appears
Note: with disk SAS 300G 15.5K, all is good
here, all logs
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.10.01 11:06:14 =~=~=~=~=~=~=~=~=~=~=~=
Current date: 10/01/14 time: 08:59:11
10/01/14-01:24:22 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:24:22 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:24:22 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:24:25 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:24:26 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:24:28 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:24:38 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:24:38 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:24:38 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:24:39 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:24:39 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:24:39 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:24:48 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:24:48 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:24:48 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:24:48 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:24:48 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:24:48 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:24:48 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:24:49 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:24:49 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:24:49 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:24:52 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
10/01/14-01:24:52 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:24:53 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:24:54 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
10/01/14-01:24:54 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:24:54 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:24:54 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:24:59 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:25:00 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:25:00 (GMT) (iacTask3): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:25:00 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:25:01 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:25:02 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:25:02 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:25:02 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:25:02 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:25:02 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:25:02 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:25:02 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:25:02 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:25:02 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:25:02 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:25:02 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:25:02 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:25:03 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:25:03 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:25:04 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:25:04 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:25:04 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:25:06 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:25:06 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:25:09 (GMT) (HealthCheck): NOTE: Scsicon error status fe received.
10/01/14-01:25:10 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:25:10 (GMT) (tRAID): WARN: key already exists
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:25:14 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:00:19
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:25:30 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:25:30 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:25:30 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:25:33 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:25:34 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:25:36 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:25:46 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:25:46 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:25:46 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:25:47 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:25:47 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:25:47 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:25:56 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:25:56 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:25:56 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:25:56 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:25:56 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:25:56 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:25:56 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:25:57 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:25:57 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:25:57 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:26:00 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
10/01/14-01:26:00 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:26:01 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:26:02 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
10/01/14-01:26:02 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:26:02 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:26:02 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:26:07 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:26:09 (GMT) (iacTask4): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:26:09 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:26:09 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:26:10 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:26:11 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:26:11 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:26:11 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:26:11 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:26:11 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:26:11 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:26:11 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:26:11 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:26:11 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:26:11 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:26:11 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:26:11 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:26:12 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:26:12 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:26:13 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:26:13 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:26:13 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:26:15 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:26:15 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:26:19 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:26:19 (GMT) (tRAID): WARN: key already exists in mapInse
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:26:23 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:01:28
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:26:39 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:26:39 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:26:39 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:26:42 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:26:43 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:26:45 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:26:55 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:26:55 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:26:55 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:26:56 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:26:56 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:26:56 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:27:05 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:27:05 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:27:05 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:27:05 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:27:05 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:27:05 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:27:05 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:27:06 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:27:06 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:27:06 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:27:10 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
10/01/14-01:27:10 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:27:11 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:27:11 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 700ms for a channel to become ready
10/01/14-01:27:11 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:27:11 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:27:12 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:27:17 (GMT) (iacTask4): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:27:17 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:27:17 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:27:17 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:27:18 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:27:18 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:27:18 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:27:19 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:27:19 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:27:19 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:27:19 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:27:19 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:27:19 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:27:19 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:27:19 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:27:19 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:27:19 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:27:19 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:27:19 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:27:19 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:27:23 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:27:24 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:27:25 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:27:25 (GMT) (tRAID): WARN: key already exists in map
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:27:29 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:02:34
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:27:45 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:27:45 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:27:45 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:27:48 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:27:49 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:27:51 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:28:01 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:28:01 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:28:01 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:28:02 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:28:02 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:28:02 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:28:11 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:28:11 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:28:11 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:28:11 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:28:11 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:28:11 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:28:11 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:28:12 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:28:12 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:28:12 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:28:15 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 29 seconds
10/01/14-01:28:15 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:28:16 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:28:17 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
10/01/14-01:28:17 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:28:17 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:28:17 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:28:22 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:28:23 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:28:23 (GMT) (iacTask4): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:28:23 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:28:24 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:28:25 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:28:25 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:28:25 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:28:25 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:28:25 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:28:25 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:28:25 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:28:25 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:28:25 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:28:25 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:28:25 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:28:25 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:28:26 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:28:26 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:28:27 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:28:27 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:28:27 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:28:29 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:28:29 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:28:33 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:28:33 (GMT) (tRAID): WARN: key already exists in
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:28:37 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:03:42
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:28:53 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:28:53 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:28:53 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:28:56 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:28:57 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:28:59 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:29:09 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:29:09 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:29:09 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:29:10 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:29:10 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:29:10 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:29:19 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:29:19 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:29:19 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:29:19 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:29:19 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:29:19 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:29:19 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:29:20 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:29:20 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:29:20 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:29:23 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
10/01/14-01:29:23 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:29:24 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:29:25 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
10/01/14-01:29:25 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:29:25 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:29:25 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:29:30 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:29:32 (GMT) (iacTask4): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:29:32 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:29:32 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:29:33 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:29:34 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:29:34 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:29:34 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:29:34 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:29:34 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:29:34 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:29:34 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:29:34 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:29:34 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:29:34 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:29:34 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:29:34 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:29:35 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:29:35 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:29:36 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:29:36 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:29:36 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:29:38 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:29:38 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:29:42 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:29:42 (GMT) (tRAID): WARN: key already exists
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:29:46 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:04:50
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:30:02 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:30:02 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:30:02 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:30:05 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:30:06 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:30:08 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:30:18 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:30:18 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:30:18 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:30:19 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:30:19 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:30:19 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:30:28 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:30:28 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:30:28 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:30:28 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:30:28 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:30:28 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:30:28 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:30:29 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:30:29 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:30:29 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:30:32 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
10/01/14-01:30:32 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:30:33 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:30:34 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
10/01/14-01:30:34 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:30:34 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:30:34 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:30:39 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:30:40 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:30:40 (GMT) (iacTask4): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:30:40 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:30:41 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:30:42 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:30:42 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:30:42 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:30:42 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:xa - WidePort: #0 - Alt Controller, chan:0 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:30:42 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:30:42 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:30:42 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:30:42 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:30:42 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:30:42 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:30:42 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:30:42 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:30:43 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:30:43 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:30:44 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:30:44 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:30:44 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
Press within 5 seconds: <S> for Service Interface, <BREAK> for baud rate 10/01/14-01:30:46 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:30:46 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:30:50 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:30:50 (GMT) (tRAID): WARN: key already exists in mapInse
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:30:55 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
S
Current date: 10/01/14 time: 09:05:59
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:31:11 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:31:11 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:31:12 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:31:14 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:31:15 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
S
10/01/14-01:31:18 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
Press within 5 seconds: <S> for Service Interface, <BREAK> for baud rate
10/01/14-01:31:27 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:31:28 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:31:28 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:31:28 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:31:28 (GMT) (tSasCfg001): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:31:28 (GMT) (tSasCfg003): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:31:37 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:31:38 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:31:38 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:31:38 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:31:38 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0d, SAS Address: 500a0b8743b04000
10/01/14-01:31:38 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0b, SAS Address: 500a0b8743b04001
10/01/14-01:31:38 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:31:38 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:31:38 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:31:38 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:31:42 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
^A
lemClearLockdown
Press within 5 seconds: <S> for Service Interface, <BREAK> for baud rate
^AS
Press within 5 seconds: <S> for Service Interface, <BREAK> for baud rate
lemClearLockdown
10/01/14-01:33:12 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:33:12 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:33:12 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:33:14 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:33:19 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:33:23 (GMT) (tRAID): WARN: dbm::RWFileSystem::initialize: Exception caught, ConstructorIOException: -16
10/01/14-01:33:23 (GMT) (tRAID): WARN: Exception caught in intentLogStartOfDay, DbmNoFileSystemException: recType: 11
10/01/14-01:33:24 (GMT) (tRAID): WARN: DbmNoFileSystemException: recType: 59 Line 1375 File cmgrControllerMgr.cc
10/01/14-01:33:24 (GMT) (tRAID): WARN: DbmNoFileSystemException: recType: 34 Line 605 File cmgrControllerMgr.cc
10/01/14-01:33:24 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:33:24 (GMT) (iacTask5): NOTE: ACS: Acs Needed on Alt: No, StateCode: 4, ReasonCode = 8
10/01/14-01:33:24 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:33:24 (GMT) (NvpsPersistentSyncM): WARN: nvps Exception DbmNoFileSystemException: recType: 20 Line 354 File nvpsPersistentSyncMgr.cc
10/01/14-01:33:24 (GMT) (tRAID): WARN: USM Exception caught in processUsmHeader - DbmNoFileSystemException: recType: 30
10/01/14-01:33:24 (GMT) (tRAID): WARN: USM Error allocating UsmStableStorageHeader in processUsmHeader() - DbmNoFileSystemException: recType: 30
10/01/14-01:33:24 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:33:24 (GMT) (tRAID): NOTE: SOD failure in evf::VolumeCfgManager::initialize
10/01/14-01:33:24 (GMT) (tRAID): NOTE: DbmNoFileSystemException in evf::VolExtentMgr::initialize
10/01/14-01:33:24 (GMT) (tRAID): NOTE: DbmNoFileSystemException in safe::initialize
10/01/14-01:33:24 (GMT) (tRAID): WARN: spm::SPMManager::initialize NoFileSystem
10/01/14-01:33:26 (GMT) (tRAID): WARN: Error in updating in memory dq cfg!
10/01/14-01:33:26 (GMT) (tRAID): WARN: Caught DbmNoFileSystemException: recType: 65 in fbm::initialize
10/01/14-01:33:26 (GMT) (tRAID): WARN: readDatabaseMelHeader: Caught Exception DbmNoFileSystemException: recType: 25 Line 4141 File mlmMelMgr.cc
10/01/14-01:33:26 (GMT) (tRAID): WARN: MelMgr::initialize FAILED: Exception Line 1768 File mlmMelMgr.cc
10/01/14-01:33:26 (GMT) (tRAID): WARN: readDatabaseSyslogConfig: Caught Exception DbmNoFileSystemException: recType: 74 Line 361 File mlmSyslogMgr.cc
10/01/14-01:33:26 (GMT) (tRAID): WARN: Syslog database access failed: Exception at Line 266 File mlmSyslogMgr.cc
10/01/14-01:33:26 (GMT) (tRAID): WARN: CacheStore::read(,): Exception DbmNoFileSystemException: recType: 24
10/01/14-01:33:26 (GMT) (tRAID): WARN: CCM: readAndValidateCacheStore() caught CacheStoreDataException
10/01/14-01:33:26 (GMT) (tRAID): NOTE: CCM: readAndValidateCacheStore() recovering
10/01/14-01:33:26 (GMT) (tRAID): NOTE: CCM: readAndValidateCacheStore() partitioning for no mirroring
10/01/14-01:33:26 (GMT) (tRAID): NOTE: CacheStore::write(): Exception DbmNoFileSystemException: recType: 24
10/01/14-01:33:26 (GMT) (tRAID): WARN: CCM: initialize() caught exception(2) CacheStoreDataException
10/01/14-01:33:26 (GMT) (tRAID): NOTE: CCM: initialize(): Configuring cache
10/01/14-01:33:27 (GMT) (tRAID): WARN: Exception caught in presMgrInit - DbmNoFileSystemException: recType: 12
10/01/14-01:33:27 (GMT) (tRAID): NOTE: DbmNoFileSystemException in vdm::DriveManager::initialize
10/01/14-01:33:27 (GMT) (tRAID): NOTE: Starting UWManager::initialize, entries 510, invalid index -1
10/01/14-01:33:27 (GMT) (tRAID): NOTE: Size of NVSRAM IW Queue is 0
10/01/14-01:33:27 (GMT) (tRAID): NOTE: DbmNoFileSystemException in vdm::VolumeGroupManager::initialize
10/01/14-01:33:27 (GMT) (tRAID): NOTE: DbmNoFileSystemException in vdm::DacstoreVolManager::initialize
10/01/14-01:33:27 (GMT) (tRAID): NOTE: DbmNoFileSystemException in vdm::PieceManager::initialize
10/01/14-01:33:27 (GMT) (tRAID): NOTE: DbmNoFileSystemException in vdm::exop::ExclOpManager::initialize
10/01/14-01:33:27 (GMT) (tRAID): WARN: Exception while recoveringIntents: DbmNoFileSystemException: recType: 11
10/01/14-01:33:27 (GMT) (tRAID): WARN: Exception while recoveringIntents: DbmNoFileSystemException: recType: 11
10/01/14-01:33:27 (GMT) (tRAID): NOTE: CacheStore::write(): Exception DbmNoFileSystemException: recType: 24
10/01/14-01:33:27 (GMT) (tRAID): WARN: CCM: initComplete() caught(2) CacheStoreDataException
10/01/14-01:33:27 (GMT) (tRAID): NOTE: RTR: IO Released
10/01/14-01:33:27 (GMT) (tRAID): ERROR: Caught DbmNoFileSystemException: recType: 58 SubRecInterface::save
10/01/14-01:33:27 (GMT) (tRAID): WARN: Caught DbmNoFileSystemException: recType: 57 in sam::StorageArrayManager::initialize
10/01/14-01:33:27 (GMT) (ProcessHandlers): WARN: Exception caught in WWNStorage iosReleased: DbmNoFileSystemException: recType: 9
10/01/14-01:33:27 (GMT) (ProcessHandlers): WARN: dbm::WWNStorage::iosReleased() FAILED.
10/01/14-01:33:27 (GMT) (tRAID): NOTE: SOD: Initialization Phase Complete
==============================================
Title: Disk Array Controller
Copyright 2005-2011 LSI Logic Corporation, All Rights Reserved.
Name: RC
Version: 07.35.67.10
Date: 07/06/2011
Time: 13:33:59 CDT
Models: 1932
Manager: devmgr.v1035api01.Manager
==============================================
10/01/14-01:33:27 (GMT) (tRAID): NOTE: sodMain Normal sequence finished, elapsed time = 137 seconds
10/01/14-01:33:27 (GMT) (tRAID): NOTE: sodMain complete
10/01/14-01:33:28 (GMT) (ProcessHandlers): WARN: DbmNoFileSystemException: recType: 35 Line 5701 File cmgrControllerMgr.cc
10/01/14-01:33:28 (GMT) (ProcessHandlers): WARN: DbmNoFileSystemException: recType: 35 Line 4774 File cmgrControllerMgr.cc
10/01/14-01:33:28 (GMT) (ProcessHandlers): NOTE: SYMbol available
10/01/14-01:34:12 (GMT) (utlTimer): WARN: Extended Link Down Timeout on channel 2
10/01/14-01:34:12 (GMT) (utlTimer): WARN: Extended Link Down Timeout on channel 3
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:41:20 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:16:24
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:41:36 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:41:36 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:41:36 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:41:39 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:41:40 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:41:42 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:41:52 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:41:52 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:41:52 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:41:53 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:41:53 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:41:53 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:42:02 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:42:02 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:42:02 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:42:02 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:42:02 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:42:02 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:42:02 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:42:03 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:42:03 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:42:03 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:42:06 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
10/01/14-01:42:06 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:42:07 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:42:08 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
10/01/14-01:42:08 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:42:08 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:42:08 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:42:13 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:42:14 (GMT) (iacTask4): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:42:14 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:42:14 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:42:15 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:42:15 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:42:15 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:42:16 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:42:16 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:42:16 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:42:16 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:42:16 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:42:16 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:42:16 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:42:16 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:42:16 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:42:16 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:42:16 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:42:16 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:42:16 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:42:20 (GMT) (ssmEvent): WARN: sendTaskLockMsg: Error or Infeasible message status=fffffffe
10/01/14-01:42:20 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:42:21 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:42:22 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:42:22 (GMT) (tRAID): WARN: key already exists in
-=<###>=-
Attaching interface lo0... done
Adding 9769 symbols for standalone.
Error
10/01/14-01:42:26 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00
Current date: 10/01/14 time: 09:17:31
Send <BREAK> for Service Interface or baud rate change
10/01/14-01:42:42 (GMT) (tRAID): NOTE: SOD Sequence is Normal, 0
10/01/14-01:42:42 (GMT) (tRAID): NOTE: SOD: removed SAS host from index 0
10/01/14-01:42:42 (GMT) (tRAID): NOTE: SYMBOL: SYMbolAPI registered.
esmc0: LinkUp event
10/01/14-01:42:45 (GMT) (tNetCfgInit): NOTE: Network Ready
10/01/14-01:42:46 (GMT) (tRAID): NOTE: Initiating Drive channel: ioc:0 bringup
10/01/14-01:42:48 (GMT) (tRAID): NOTE: IOC Firmware Version: 00-24-65-00
10/01/14-01:42:58 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:0 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:42:58 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:1 phy:1 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:42:58 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:42:59 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan:0 phy:3 prevNumActivePhys:2 numActivePhys:2
10/01/14-01:42:59 (GMT) (tSasCfg002): NOTE: Alt Controller path up - chan:1 phy:18 itn:1
10/01/14-01:42:59 (GMT) (tSasCfg005): NOTE: Alt Controller path up - chan:0 phy:16 itn:2
10/01/14-01:43:08 (GMT) (tRAID): NOTE: IonMgr: Drive Interface Enabled
10/01/14-01:43:08 (GMT) (tRAID): NOTE: SOD: Instantiation Phase Complete
10/01/14-01:43:08 (GMT) (tRAID): NOTE: Inter-Controller Communication Channels Opened
10/01/14-01:43:08 (GMT) (tSasDiscCom): NOTE: SAS Discovery complete task spawned
10/01/14-01:43:08 (GMT) (IOSched): NOTE: New Initiator: 1 - channel: 0,devHandle: x0f, SAS Address: 500a0b8743b04000
10/01/14-01:43:08 (GMT) (IOSched): NOTE: New Initiator: 2 - channel: 1,devHandle: x0c, SAS Address: 500a0b8743b04001
10/01/14-01:43:08 (GMT) (tRAID): NOTE: LockMgr Role is Slave
10/01/14-01:43:09 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
10/01/14-01:43:09 (GMT) (sasCheckExpanderSet): NOTE: Expander SAS address: Hi = x500a0b85 Low = xbbf4a010
10/01/14-01:43:09 (GMT) (tRAID): NOTE: spmEarlyData: Using cached data
10/01/14-01:43:12 (GMT) (tSasDiscCom): WARN: SAS: Initial Discovery Complete Time: 30 seconds
10/01/14-01:43:12 (GMT) (tRAID): NOTE: WWN baseName 000700a0-b8743b04 (valid==>SoftRst)
10/01/14-01:43:13 (GMT) (tRAID): NOTE: ionEnableHostInterfaces is waiting for a channel to become ready
10/01/14-01:43:14 (GMT) (tRAID): NOTE: ionEnableHostInterfaces waited 1800ms for a channel to become ready
10/01/14-01:43:14 (GMT) (tRAID): NOTE: IonMgr: Host Interface Enabled
10/01/14-01:43:14 (GMT) (tRAID): NOTE: SOD: Pre-Initialization Phase Complete
10/01/14-01:43:14 (GMT) (utlTimer): NOTE: fcnChannelReport ==> -2 -3
10/01/14-01:43:19 (GMT) (utlTimer): NOTE: fcnChannelReport ==> =2 =3
10/01/14-01:43:21 (GMT) (tRAID): NOTE: ACS: autoCodeSync(): Process start. Comm Mode: 0, Status: 1
10/01/14-01:43:21 (GMT) (iacTask2): NOTE: ACS: Acs Needed on Alt: No, StateCode: 3, ReasonCode = 2
10/01/14-01:43:21 (GMT) (tRAID): NOTE: SOD: Code Synchronization Initialization Phase Complete
10/01/14-01:43:22 (GMT) (NvpsPersistentSyncM): NOTE: NVSRAM Persistent Storage updated successfully
10/01/14-01:43:22 (GMT) (tHckReset): WARN: Alt Ctl Reboot:
Reboot CompID: 0x408
Reboot reason: 0x6
Reboot reason extra: 0x0
10/01/14-01:43:22 (GMT) (tHckReset): NOTE: holding alt ctl in reset
10/01/14-01:43:23 (GMT) (IOSched): NOTE: Disconnect Initiator 1 - channel: 0, devHandle: x0f, I/O: 0, SAS Address: 500a0b8743b04000
10/01/14-01:43:23 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000f
10/01/14-01:43:23 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 1
10/01/14-01:43:23 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:2 prevNumActivePhys:2 numActivePhys:1
10/01/14-01:43:23 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, OPTIMAL to DEGRADED
10/01/14-01:43:23 (GMT) (IOSched): NOTE: Disconnect Initiator 2 - channel: 1, devHandle: x0c, I/O: 0, SAS Address: 500a0b8743b04001
10/01/14-01:43:23 (GMT) (IOSched): WARN: sasRemoveInitiator - No I/O's - send EventAck: event: 00000018, eventContext: 0002000c
10/01/14-01:43:23 (GMT) (sasTgtSendEventAck): WARN: sasTgtSendEventAckTask - SendEventAck for host: 2
10/01/14-01:43:23 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: chan:0 phy:3 prevNumActivePhys:1 numActivePhys:0
10/01/14-01:43:23 (GMT) (tSasEvtWkr): NOTE: sasIocPhyDown: IOCPort: chan:0, DEGRADED to FAILED
10/01/14-01:43:23 (GMT) (tSasEvtWkr): NOTE: sasRemoveExpanders: removing expanders on chan:0 level:0 and below
10/01/14-01:43:23 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, OPTIMAL to DEGRADED
10/01/14-01:43:23 (GMT) (tSasEvtWkr): NOTE: sasLinkDown: expDevHandle:x9 - WidePort: #1 - Alt Controller, chan:1 encl:0, subExp:255, DEGRADED to FAILED
10/01/14-01:43:27 (GMT) (tHckReset): NOTE: releasing alt ctl from reset
10/01/14-01:43:27 (GMT) (tHckReset): NOTE: LockMgr Role is Master
10/01/14-01:43:29 (GMT) (tRAID): NOTE: USM Mgr initialization complete with 0 records.
10/01/14-01:43:29 (GMT) (tRAID): WARN: key already exists in mapInsertT
-=<###>=-
Attaching interface lo0... done
Similar Messages
-
Oracle VM: Sun server x3-2 with Sun Storage 2540 M2
Hello Everyone!
Currently, we are planning to implement a project about Visualization using Oracle VM.
As the Sun Storage 2540 M2 uses FC channel to share its luns from storage, we are not sure on how to discover those share storage luns to be use in Oracle VM manager and Oracle VM Server.
So, could you please help guide us, give us some recommendations, or instruction documents to the issue above?
Thank so much in advance!
Regard,
DaraHmm, server is not (auto?)discovered
though machines can see each other via network, all ports are opened, but agent still reports
[2011-07-28 21:07:32 6001] DEBUG (OVSNotificationServer:233) NOTIFICATION SERVER STARTED
[2011-07-28 21:07:32 6005] INFO (OVSRemaster:101) REMASTER SERVER STARTED
[2011-07-28 21:07:32 6009] INFO (OVSMonitor:29) MONITOR SERVER STARTED
[2011-07-28 21:07:32 6013] INFO (OVSHA:103) HA SERVER STARTED
[2011-07-28 21:07:33 6017] INFO (OVSStat:234) STAT SERVER STARTED
[2011-07-28 21:07:33 6021] INFO (OVSAgentServer:274) OVSAgentServer start serving!
[2011-07-28 21:07:33 6021] INFO (OVSAgentServer:275) Oracle VM Server version: {'release': '3.0.2', 'date': '201109270901', 'build': '75'}
[2011-07-28 21:07:37 6009] DEBUG (OVSMonitor:46) Cluster state changed from [Unknown] to [Offline]
[2011-07-28 21:07:37 6009] DEBUG (OVSMonitor:50) Error sending notification: Cannot get manager URL from agent db.
[2011-08-14 23:30:58 13993] DEBUG (agtctl:95) master flag: None
A slight off-subject question, do I need to run anything on OVM (apart from setting on all servers the same password)? -
Sun Storage 2540 transfer volume from one controller to another
How we can manually transfer volume from controller to another controller ?
http://download.oracle.com/docs/cd/E19578-01/819-7038-10/819-7038-10.pdf
http://download.oracle.com/docs/cd/E19377-01/821-0968-10/821-0968-10.pdf
/opt/SUNWstkcam/binsscs list -a <array-name> volume
For every volume:
/opt/SUNWstkcam/bin/sscs modify -a <array-name> -c B volume <volume-name>
Regards. -
Hi all,
have 2 server Sparc T4 1 Storage 2540,is it necessary to install solaris cluster software for oracle database in each VM?
Thanks,
jari.Hi,
it depends what you would like to achieve. A good starting point is
SPARC: Oracle Solaris Cluster Topologies - Oracle Solaris Cluster Concepts Guide
regards
Walter -
Hello
I have CAM 6.5 and two Sun storages 2540
when i register them if finds them normally, with their names
But after this CAM sees both storages with the same name and i can manage only one of themHi,
How many controllers do you have on each ST2540.?
Each St2540 can have 2 controllers with seperate IP each.
You can cross verify that the IP's given during registration are from seperate storages (eg. controller A from both storages).
We are using same configuration here and found no such issues. -
Is Sun Storage 7000 Storage replication adapter compatible with 2540 series
We are evaluating VMWare Site Recovery Manager 4.0. Is Sun Storage 7000 Storage replication adapter compatible with 2540 Sun Storage series?
I would say the short answer would be no. The 2540 is a LSI based device, the SRM adapter for that is written by LSI. The 7000
series array is based on OpenSolaris and ZFS, quite a different beast. -
My CAM cannot see 2540 storage
Hello
I Installed CAM 6.0 on my windows XP, I powered on my 2540 storage for the first time. and connect it to the same LAN that my laptop is connected to.
when I try to register the array , the CAM cannot find it. I can ping to the storage using the default IP as in the Installation guide.
what can I do to troubleshoot this and solve it?
ThanksAssuming your 2540 is factory fresh, i.e., it hasn't been reconfigured IP wise since leaving the factory...
Reference Sun doc 820-0015-12.pdf...
The factory default IP address for controller A is: 192.168.128.101
The factory default IP address for controller B is: 192.168.128.102
Set your primary Ethernet port on your WinXP box temporarily to, for example, 192.168.128.1
Using either a cross-over cable, or you can do what I did, I used an old 10/100 Cisco switch in between the machine hosting the CAM software and the controllers. Once you have this properly setup, re-run the CAM registration process. You'll see your controller, auto-magically in CAM.
IF YOUR 2540 IS NOT FACTORY FRESH... You do have the special serial cable that came with the 2540? The reason I bring this up is because I built a project around 12 of these 2540's and I had to first create the private network to support the CAM function, and then I had to re-IP each of the controllers so that 24 controllers didn't step over themselves IP wise. Once you have the initial registration of the controller, you can change the IP address of the controller within CAM. So, if your 2540 is NOT new to you, the IP address of the controller may have changed. If so, then it will be easier to just "tip" into the controller (as oppose to the time searching the IP spectrum) and change the IP back to default, or to something else. To "tip" into a serial port is the equivalent of creating a null modem connection. If you need to "tip" into the serial port, then this is a different subject for another post.
Hope this help,
rrtays -
Need docs that explain Fibre Channel setup, getting I/O error on 2540 SAN
Sun T5220 Host running Solaris 10 5/09 as management host.
Qlogic 5602 FC Switch
Sun Storagetek 2540 - one controller tray with 9 300G SAS Hitachi drives. Firmware 7.35.x.
Sun branded Qlogic QLE2462 HBAs - PCI express, dual port. 3 in the T5220. qlcxxxx drivers for the HBAs.
Sun Common Array Manager software version 6.5.
I am a long-time Oracle DBA who has the task of setting up a Fibre Channel SAN. I am not a Solaris sysadmin, but have installed and maintained large databases on Solaris boxes where I had access to a competent sysadmin. I am at a classified site and cannot bring out electronic files with logs, configuration info, etc. to upload. Connecting the T5220 is the 1st box of many. This is my first exposure to HBA's, Fibre Channel, and SAN, so everything I know about it I have read in a manual or from a post somewhere. I understand the big picture and I have the SAN configured with 2 storage pools each with 1 volume in them on RAID5 virtual disks. I can see the LUN 0 on the T5220 server when I do a luxadm probe and when I do a format. I formatted one of the volumes successfully. Now I attempt to issue:
newfs /dev/rdsk/device_name_from_output_of_luxadm_probe
I get an immediate I/O error. I could be doing something totally naive or have a larger problem - this is where I get lost and the documentation becomes less detailed.
What would be great is if anyone knows of a detailed writeup that would match what I'm doing or a good off-the-shelf textbook that covers all of this or anything close. I continue to search for something to bridge my lack of knowledge in this area. I am unclear about the initiators and targets beyond the fundamental definitions. I have used the CAM 6.5 software to define the initiators that it discovered. I have mapped the Sun host into a host group also. I do not know what role the Qlogic 5602 Fibre Channel switch plays with respect to initiators and targets or if it has any role at all. Is it just a "pass through" and the ports on the 5602 do not have to be included? Maybe I don't have the SAN volume available in read/write. I find bits and pieces in blogs and forums, but nothing that puts it all together. I also find that many of the notes on the web are not accurate.
This all may appear simplistic to someone who works with it a lot and if you know of an obvious reference I should be using, a link or reply would be greatly appreciated as I continue to Google for information.Thanks for the reply. I had previously read the CAM 6.5 manual and have all the SAN configuration and mappings. Yesterday I was back at the site and was able to place a UFS filesystem on the exposed SAN LUN which was 0. I've not seen any reference to LUN 0 being a placeholder for the 2540 setup and when I assigned it, I allowed the CAM 6.5 software to choose "Next Available" LUN and it chose 0. LUN 31 on the 2540 is the "Access" LUN that is assigned automatically - perhaps it is taking the place of what you describe as the LUN 0 placeholder.
I was able to put a new UFS filesystem on LUN 0 (newfs), mount it, and copy data to it. The disk naming convention that Solaris shows for the SAN disks is pretty wild and I usually have to reference a Solaris book on the standard scsi disk name formats. My question/confusion at the moment is that I have 3 Sun branded Qlogic HBA's in the Sun T5220 server - QLE2462 (dual port) with one port on two of the HBAs cabled to the Qlogic 5602 FC switch which is cabled to the A and B controller of the SAN 2540 - there are only 2 cables coming out of the 5220; the 3rd HBA (for future use) has no cables to it. Both ports show up as active and connected on the server down to the SAN and the CAM 6.5 software automatically identified both initiators (ports) on the Sun 5220 when I mapped them. I had previously mapped them to the Sun host, mapped the host to a host_group, virtual disks to volumes, volumes to....etc.; and was able to put data on the exposed volume named dev_vol1 which is a RAID5 virtual disk on the SAN.
When I use the format command on Solaris, it shows two disks and I assumed this represented the two ports from the same host 5220. I was able to put a label on one of these disks (dev_vol1), format it, and put data on it as noted above. When I select the other disk in the format menu, it is not formatted, won't allow me to put a label on it (I/O error) and I can go no further from there. The CAM 6.5 docs stop after they get you through the mapping and getting a LUN exposed. I continue on the in a Solaris-centric mindset and try to do the normal label, format, newfs, mount routine and it works for the one "disk" that format finds but not for the other. The information from the format info on both the disks shows them as 1.09 TB and that is the only volume mapped right now from the SAN so I know it is the same SAN volume. It does not make sense that I would label it and format it again anyway, but is this what I am supposed to see - two disks (because of 2 ports?) and the ability to access it through one. I found out by trial an error that I could label, format, and access the one. I did not do it from knowledge or looking at the information presented....I just guessed through it.
I have not "bound" the 2 or HBAs in any way and that is on my list as next because I want to do multipathing and failover - just starting to read that so I may be using the wrong language. But I am wondering before I go on to that, if I am leaving something undone in the configuration that is going to hamper my success in the multipathing - since I cannot do anything with the 2nd "disk" that has been exposed to Solaris from the SAN. I thought, after I labeled, formatted and put a filesystem on the one "disk" I can write to that the other "disk" that shows up would just be another path to the same data via a 2nd initiator. Just writing that does not sound right, but I am trying to convey my thoughts as to what I logically expected to see. Maybe the question should be why am I seeing that 2nd "disk" in a Solaris format listing at all? I have not rebooted any time during this process also and can easily do that and will today. -
Hi experts,
I'm tring to configure OVM 3.1.1with a Storagetek 2540/2540-M2 array, is this supported? Do I have to install RDAC drivers in Oracle VM server?
I have this platform:
OVM Manager 3.1.1 on Sunfire X2270-M2 up and running
OVM Server 3.1.1 on sunfire X4470-M2 up and running
Storagetek 2540
The case is that I have 2 luns mapped in CAM for OVM Server, but it only sees the local luns, when I issue the commands: multipath -l, multipath -ll, rescan_for_disks, or rescan-scsi-bus.sh, from the ovm server it does not see the luns from the storage. I modify the multipath.conf file with the info of this doc:
http://docs.oracle.com/cd/E20734_01/pdf/E24025.pdf
device {
vendor "SUN"
product "LCSM100_F"
path_grouping_policy group_by_prio
prio rdac
getuid_callout "/lib/udev/scsi_id -g -u -d /dev/%n"
polling_interval 5
path_checker rdac
path_selector "round-robin 0"
hardware_handler "1 rdac"
failback immediate
features "2 pg_init_retries 50"
no_path_retry 30
rr_min_io 100
Am I doing something wrong?
RegardsMaybe a zoning issue. I run some 4470 M2 and don't have an issue with the multipath. I run a ZFS storage product which shouldn't that much different in what you're running with the 2540 MT2. What fiber switch are you running?
-
Any experience/suggestions with Oracle on Sun Storagetek 2540 SAN via NFS?
Hi,
Currently Oracle 11g is up and running on local drives. And we intend to move it off to Sun Storagetek 2540 SAN with Sun server 4140 (as NFS server) via NFS. So as far as the database server is concerned, it'd be NFS mount to the NFS server.
There's a new feature in Oracle 11g, Direct NFS Client, which is supposed to be more effective and more efficient than relying on O/S handling of NFS protocol. But in the white paper, it ONLY mentioned about NFS NAS scenario, not SAN. But I think it'd work with SAN as well, because as far as the database server is concerned, it's communicating to NFS server via NFS protocol. What do you think? Any experience/suggestions?
In terms of Storagetek 2540 SAN support, the Oracle's official answer would be "it's not supported unless the storage vendor and the storage device are listed in the Oracle Storage Compatibility Program list..." However, OSCP has been discommissioned in 1/2007, and Storagetek 2540 was introduced AFTER the date.
I think it MIGHT work given it's Sun/Oracle alliance.
What do you think?
Input/suggestion is appreciated,
HelenMy 3 year old linux installtion on my laptop, which is my NFS client most of the time uses udp as default (kernel 2.4.19).
Anyway the key is that the NFS client, or better, the RPC implementation on the client is intelligent enough to detect a failed TCP connection and tries to reestablish it with the same IP address. Now once the cluster has failed over the logical IP the reconnect will be successful and NFS traffic continues as if nothing bad had happened. This only(!) works if the NFS mount was done with the "hard" option. Only this makes the client retry the connection.
Other "dumb" TCP based applications might not retry and thus would need manual intervention.
Regarding UFS or PxFS, it does not make a difference. NFS does not know the difference. It shares a mount point.
Hope that helped. -
2540-M2 configuration on SG-XPCIE2FC-QF4 port 1
Hello..
One of my M5000 is running with two of SG-XPCIE2FC-QF4 card. Port 0 is directly connected (without SAN switches) to a 2008 model 2540 storage and now I need to attach my newly bought 2540-M2 to port 1 of these FC HBAs. I mapped the LUNs to the correct storage domains using CAM. In Solaris, even if I do devfsadm any number times nothing comes up in format! Any idea? Does the port 1 support 2540-M2? Need some patches? Please help...Thanks for your reply...
After many map-umapps to the default storage domain finally I could get the LUNS visible to Solaris. Now the issues is that port 1 on HBA (on the slot 2 PCI-E) is showing NOT CONNECTED! I have replaced fiber cables and powered off-on the array but no use. I did not reboot the server, only did a devfsadm -v. Old LUNs are Active/Standby mode as it has two paths, but the new ones are having only one path and threfore no redundancy. Any clues? see below outputs..
#cfgadm -al -o show_FCP_dev
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
c1 connected configured unknown
unavailable fc-private n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0:fc
c1::202400a0b839c57a,0 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0:fc::202400a0b839c57a,0
c1::202400a0b839c57a,1 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0:fc::202400a0b839c57a,1
c1::202400a0b839c57a,5 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0:fc::202400a0b839c57a,5
c1::202400a0b839c57a,31 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0:fc::202400a0b839c57a,31
c2 connected configured unknown
unavailable fc-private n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:fc
c2::20360080e523efc2,0 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:fc::20360080e523efc2,0
c2::20360080e523efc2,1 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:fc::20360080e523efc2,1
c2::20360080e523efc2,2 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:fc::20360080e523efc2,2
c2::20360080e523efc2,31 connected configured unknown
unavailable disk n /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:fc::20360080e523efc2,31
c3 connected configured unknown
unavailable fc-private n /devices/pci@1,700000/SUNW,qlc@0/fp@0,0:fc
c3::202500a0b839c57a,0 connected configured unknown
unavailable disk n /devices/pci@1,700000/SUNW,qlc@0/fp@0,0:fc::202500a0b839c57a,0
c3::202500a0b839c57a,1 connected configured unknown
unavailable disk n /devices/pci@1,700000/SUNW,qlc@0/fp@0,0:fc::202500a0b839c57a,1
c3::202500a0b839c57a,5 connected configured unknown
unavailable disk n /devices/pci@1,700000/SUNW,qlc@0/fp@0,0:fc::202500a0b839c57a,5
c3::202500a0b839c57a,31 connected configured unknown
unavailable disk n /devices/pci@1,700000/SUNW,qlc@0/fp@0,0:fc::202500a0b839c57a,31
c4 connected unconfigured unknown
unavailable fc n /devices/pci@1,700000/SUNW,qlc@0,1/fp@0,0:fc
#luxadm -e port
/devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0:devctl CONNECTED
/devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0:devctl CONNECTED
/devices/pci@1,700000/SUNW,qlc@0/fp@0,0:devctl CONNECTED
*/devices/pci@1,700000/SUNW,qlc@0,1/fp@0,0:devctl NOT CONNECTED*
luxadm_-e_dump_map_-devices-pci@0,600000-pci@0-pci@9-SUNW,qlc@0,1-fp@0,0:devctl.out
Pos AL_PA ID Hard_Addr Port WWN Node WWN Type
0 e4 2 e4 20360080e523efc2 20060080e523efc2 0x0 (Disk device)
1 1 7d 0 2101001b3230e8c2 2001001b3230e8c2 0x1f (Unknown Type,Host Bus Adapter)
luxadm_-e_dump_map_-devices-pci@0,600000-pci@0-pci@9-SUNW,qlc@0-fp@0,0:devctl
Pos AL_PA ID Hard_Addr Port WWN Node WWN Type
0 ef 0 ef 202400a0b839c57a 200400a0b839c57a 0x0 (Disk device)
1 1 7d 0 2100001b3210e8c2 2000001b3210e8c2 0x1f (Unknown Type,Host Bus Adapter)
luxadm_-e_dump_map_-devices-pci@1,700000-SUNW,qlc@0-fp@0,0:devctl
Pos AL_PA ID Hard_Addr Port WWN Node WWN Type
0 e4 2 e4 202500a0b839c57a 200400a0b839c57a 0x0 (Disk device)
1 1 7d 0 2100001b3210cbc3 2000001b3210cbc3 0x1f (Unknown Type,Host Bus Adapter)
luxadm_probe.out
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node WWN:200400a0b839c57a Device Type:Disk device
Logical Path:/dev/rdsk/c7t600A0B800039C57A0000030348798E6Ad0s2
Node WWN:200400a0b839c57a Device Type:Disk device
Logical Path:/dev/rdsk/c7t600A0B800039C57A0000030748798F30d0s2
Node WWN:200400a0b839c57a Device Type:Disk device
Logical Path:/dev/rdsk/c7t600A0B800039CA0E000002F948798F93d0s2
Node WWN:20060080e523efc2 Device Type:Disk device
Logical Path:/dev/rdsk/c7t60080E500023EFC2000004C84E857119d0s2
Node WWN:20060080e523efc2 Device Type:Disk device
Logical Path:/dev/rdsk/c7t60080E500023EFC2000004CB4E857181d0s2
Node WWN:20060080e523efc2 Device Type:Disk device
Logical Path:/dev/rdsk/c7t60080E500023EFC2000004CD4E8571BEd0s2
(highlited are the new LUNs added)
#format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> 72g
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@0,0
1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@0,600000/pci@0/pci@8/pci@0/scsi@1/sd@1,0
2. c7t600A0B800039C57A0000030348798E6Ad0 <SUN-LCSM100_F-0670 cyl 38398 alt 2 hd 512 sec 64>
/scsi_vhci/ssd@g600a0b800039c57a0000030348798e6a
3. c7t600A0B800039C57A0000030748798F30d0 <SUN-LCSM100_F-0670 cyl 51198 alt 2 hd 128 sec 64>
/scsi_vhci/ssd@g600a0b800039c57a0000030748798f30
4. c7t600A0B800039CA0E000002F948798F93d0 <SUN-LCSM100_F-0670 cyl 51198 alt 2 hd 128 sec 64>
/scsi_vhci/ssd@g600a0b800039ca0e000002f948798f93
5. c7t60080E500023EFC2000004C84E857119d0 <SUN-LCSM100_F-0777-2.00TB> appsnew
/scsi_vhci/ssd@g60080e500023efc2000004c84e857119
6. c7t60080E500023EFC2000004CB4E857181d0 <SUN-LCSM100_F-0777 cyl 63998 alt 2 hd 256 sec 64> temp1new
/scsi_vhci/ssd@g60080e500023efc2000004cb4e857181
7. c7t60080E500023EFC2000004CD4E8571BEd0 <SUN-LCSM100_F-0777 cyl 63998 alt 2 hd 256 sec 64> temp2new
/scsi_vhci/ssd@g60080e500023efc2000004cd4e8571be
#luxadm display /dev/rdsk/c7t600A0B800039C57A0000030348798E6Ad0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c7t600A0B800039C57A0000030348798E6Ad0s2
Vendor: SUN
Product ID: LCSM100_F
Revision: 0670
Serial Num: SX73502942
Unformatted capacity: 614400.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x3
Maximum prefetch: 0x3
Device Type: Disk device
Path(s):
/dev/rdsk/c7t600A0B800039C57A0000030348798E6Ad0s2
/devices/scsi_vhci/ssd@g600a0b800039c57a0000030348798e6a:c,raw
Controller /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0
Device Address 202400a0b839c57a,5
Host controller port WWN 2100001b3210e8c2
Class primary
State ONLINE
Controller /devices/pci@1,700000/SUNW,qlc@0/fp@0,0
Device Address 202500a0b839c57a,5
Host controller port WWN 2100001b3210cbc3
Class secondary
State STANDBY
Whereas the new volumes have only one path;
#luxadm display /dev/rdsk/c7t60080E500023EFC2000004CD4E8571BEd0s2
DEVICE PROPERTIES for disk: /dev/rdsk/c7t60080E500023EFC2000004CD4E8571BEd0s2
Vendor: SUN
Product ID: LCSM100_F
Revision: 0777
Serial Num: SV12601017
Unformatted capacity: 512000.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x3
Maximum prefetch: 0x0
Device Type: Disk device
Path(s):
/dev/rdsk/c7t60080E500023EFC2000004CD4E8571BEd0s2
/devices/scsi_vhci/ssd@g60080e500023efc2000004cd4e8571be:c,raw
Controller /devices/pci@0,600000/pci@0/pci@9/SUNW,qlc@0,1/fp@0,0
Device Address 20360080e523efc2,0
Host controller port WWN 2101001b3230e8c2
Class primary
State ONLINE -
Hi All,
I want to replace a battery on a 2540 storage.
Using CAM The state of the battery is Enabled and status error.
There is a maintenance led on the front of the storage.
At rear there is no maintenance led.
I cant' replace the battery because the state is not "Enabled but offline"
when I start the procedure for replacement.
Please help it is urgent .
Thanks,
EKRA ThierryIt is first important to know why the battery needs to be replaced, because all the 2500/2500-M2 have SMART batteries and if the battery is only expired, it should not be replaced.
There are different situations for which the batteries do not need to be replaced, they are explained in our KB article "Troubleshooting Sun Storage[TM] Array SMART Battery Faults (Doc ID 1021054.1)".
Nicolas -
Hi there,
I have a very strange issue with a 2540 storage array. I have cam 6.9 running on Solaris and the array is running firmware 7.35. When I register the array it sees it ok however as soon as I finish the registration I lose communication with the array. However I can ping the array and I can also see the controllers and disk's etc within cam. I am also managing a 6540 on the same cam host which I have no issue with.
Can anybody assist?Hi there,
I have a very strange issue with a 2540 storage array. I have cam 6.9 running on Solaris and the array is running firmware 7.35. When I register the array it sees it ok however as soon as I finish the registration I lose communication with the array. However I can ping the array and I can also see the controllers and disk's etc within cam. I am also managing a 6540 on the same cam host which I have no issue with.
Can anybody assist? -
Hi,
I'm in the process of configuring a 2540 storage array and have followed the instructions here
http://docs.sun.com/source/820-0015-11/hwig15xx_ipaddress.html#50458655_pgfId-1023204
to connect a serial terminal using the supplied 6-pin mini-DIN to RJ45 but despite using a selection of different adaptors I don't get any output on the terminal.
I've tried Break and CTRL Break but still nothing.
I'm fairly sure that the ethernet interface hasn't picked up a DHCP address.
Have even tried connecting to a serial port on a laptop without any success.
Any suggestions?
Thanks!Now you have to download CAM 6.0.1 from https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=SSTKCAM-6.0.1.11-OTH-G-F@CDS-CDS_SMI, install it, upgrade the array f/w to the latest version (06.70.54.10) and here you go, you can create your pool, profiles and volumes.
Enjoy ;-) -
2540 - more then 32 mappings to the host ?
Hello,
we decided to chunk the whole 2540 array space into 100 GB chunks. We got about 40 LUNs.
But we cannot map all to the host - only first 32 LUNs.
Does anybody know why ?HI,
It is the limitation of the storage and you cant map more than 32 luns from the storage.
you wont get the option of lun number greater than 31 and 31 will be a phantom.
Maybe you are looking for
-
File to idoc scenario error - not working yet :(
Hello! I'm trying to make changes in business partner record in CRM using idoc CRMXIF_PARTNER_SAVE_M01 I have an error 56 EDI: Partner profile not available. In Control record in we02 transaction, I have right Partner number for Recipient information
-
Simple question on /jsp:useBean
Hi, I have a bean within my jsp page. My page doesnt have the </jsp:useBean> code. When users go to my site everything is good. If they hold down F5 for a while, the page hangs and it hangs the whole site until its finished. Its like hold down F5 for
-
Does any one have the path to install Adobe 11 on OS 10.7 system?
I´ve just installed the Adobe Reader 11.0 on my macbook (OS 10.7). But when I tryed to open it appears a message ¨an internal error ocurred¨. Someone reported a similar problem installing the Adobe Reader version 10.0 on a macbook (OS 10.5), and wer
-
Bundling a vi for backwards compatibility
I am running 2 versions of Labview on different windows machines, 8.2.1 and 7.1. My problem is this: I am talking to a custom bit of hardware over USB, I only have code to do this in LV 8.2.1. I want to get the same functionality in 7.1. Is there any
-
Keynote recordings into Podcasts?
I tried searching for an answer to this with no luck. I'm using the new Keynote "Record Presentation" feature with great success. I'd love to use this approach to help create a video podcast, but everything that I'm seeing is based off of earlier Key