Skip to ContentSkip to Footer
시작 내용
- Community Home
- >
- HPE Community, Korea
- >
- HP-UX
- >
- event.log좀 봐주세요...추가질문있습니다....또 추가질문여.
HP-UX
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
-
정보
- 커뮤니티
- Welcome
- 시작하기
- 포럼 FAQ
- 랭킹 개요
- 참여규칙
- Tips and Tricks
- 접촉
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- 다른 HPE 사이트
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
포럼
-
블로그
-
정보
-
한국어
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 친구에게 이메일 보내기
- 부적절한 컨텐트 신고
날짜: 11-18-2004 11:00 PM
날짜: 11-18-2004 11:00 PM
event.log좀 봐주세요...추가질문있습니다....또 추가질문여.
OS : hp-ux 10.0
Model : K9000
아래에 event.log를 보여드립니다....
Event.log --------------------------------------------------
Event data from monitor:
Event Time : Sun Nov 11 01:01:24 2004
Hostname : zkr01h04 IP Address : xx.xx.xx.xx
Event Id : 0x00417a805400000000 Monitor : ha_disk_array
Event # : 66 Event Class : I/O
Severity : CRITICAL
Storage array controller at hardware path 10/8.1.1 : Peer Controller Removed
Associated OS error log entry id(s):
0x417a805200000002
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/ha_disk_array.htm#66
Description of Error:
This SP (storage-control processor)'s peer is no longer responding to queries
from this SP following a period of time where the peer was known present. (SP
Event Code 0xA11)
Probable Cause / Recommended Action:
The peer Storage-control Processor (SP) has been removed or has failed. Replace
the SP with the "Service LED" indicator on.
--------------------------------------------------------------
또한 dmesg 에 아래와 같은 message도 보여집니다..
dmesg --------------------------------------------------------
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f040100 (with priority: 0, and current flags: 0x40) t.
LVM: Restored PV 0 to VG 4.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f040100 (with priority: 0, and current flags: 0x40) t.
LVM: Restored PV 0 to VG 4.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f040100 (with priority: 0, and current flags: 0x40) t.
LVM: Restored PV 0 to VG 4.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path 10/8.0.1 (error = 5)
lv_readvgdats: Could not read VGDA 2 header & trailer from disk H/W path 10/8.0.1 (error = 5)
lv_readvgdats: Could not read VGSA 1 header & trailer from disk H/W path 10/8.0.1 (error = 5)
lv_readvgdats: Could not read VGSA 2 header & trailer from disk H/W path 10/8.0.1 (error = 5)
LVM: Failed to restore PV 0 to VG 4!
lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path 10/8.0.1 (error = 5)
LVM: Restored PV 0 to VG 4.
----------------------------------------------------------
Model : K9000
아래에 event.log를 보여드립니다....
Event.log --------------------------------------------------
Event data from monitor:
Event Time : Sun Nov 11 01:01:24 2004
Hostname : zkr01h04 IP Address : xx.xx.xx.xx
Event Id : 0x00417a805400000000 Monitor : ha_disk_array
Event # : 66 Event Class : I/O
Severity : CRITICAL
Storage array controller at hardware path 10/8.1.1 : Peer Controller Removed
Associated OS error log entry id(s):
0x417a805200000002
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/ha_disk_array.htm#66
Description of Error:
This SP (storage-control processor)'s peer is no longer responding to queries
from this SP following a period of time where the peer was known present. (SP
Event Code 0xA11)
Probable Cause / Recommended Action:
The peer Storage-control Processor (SP) has been removed or has failed. Replace
the SP with the "Service LED" indicator on.
--------------------------------------------------------------
또한 dmesg 에 아래와 같은 message도 보여집니다..
dmesg --------------------------------------------------------
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f040100 (with priority: 0, and current flags: 0x40) t.
LVM: Restored PV 0 to VG 4.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f040100 (with priority: 0, and current flags: 0x40) t.
LVM: Restored PV 0 to VG 4.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f040100 (with priority: 0, and current flags: 0x40) t.
LVM: Restored PV 0 to VG 4.
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
LVM: Performed a switch for Lun ID = 1 (pv = 0x37a7400), from raw device 0x1f041100 (with priority: 1, and current flags: 0x0) to.
LVM: VG 4 : PV 0 (device 0x1f040100) is POWERFAILED
LVM: Recovered Path (device 0x1f040100) to PV 0 in VG 4.
lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path 10/8.0.1 (error = 5)
lv_readvgdats: Could not read VGDA 2 header & trailer from disk H/W path 10/8.0.1 (error = 5)
lv_readvgdats: Could not read VGSA 1 header & trailer from disk H/W path 10/8.0.1 (error = 5)
lv_readvgdats: Could not read VGSA 2 header & trailer from disk H/W path 10/8.0.1 (error = 5)
LVM: Failed to restore PV 0 to VG 4!
lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path 10/8.0.1 (error = 5)
LVM: Restored PV 0 to VG 4.
----------------------------------------------------------
5 응답 5
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 친구에게 이메일 보내기
- 부적절한 컨텐트 신고
날짜: 11-18-2004 11:00 PM
날짜: 11-18-2004 11:00 PM
event.log좀 봐주세요...추가질문있습니다....또 추가질문여.
The peer Storage-control Processor (SP) has been removed or has failed. Replace the SP with the "Service LED" indicator on.
한쪽 controller에 무네가 있는듯 합니다..
10/8.1.1 에 붙은 것이 sp A 인지 sp B 인지 확인하시고 교체를.....
한쪽 controller에 무네가 있는듯 합니다..
10/8.1.1 에 붙은 것이 sp A 인지 sp B 인지 확인하시고 교체를.....
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 친구에게 이메일 보내기
- 부적절한 컨텐트 신고
날짜: 11-19-2004 11:00 PM
날짜: 11-19-2004 11:00 PM
event.log좀 봐주세요...추가질문있습니다....또 추가질문여.
안녕하세요~
이종민입니다.
메시지 내용으로 보아, K class에 nike어레이를 사용하시는 듯하네요.
어레이의 컨트롤러(SP)가 한개 고장난듯 합니다.
고장난 컨트롤러를 교체하세요~
제 기억에 나이키는 한쪽 컨트롤러 고장나면, 성능이 엄청 떨어지던것으로 기억합니다. 그러니 얼렁 연락하셔서 교체해 주세요
그럼..
이종민입니다.
메시지 내용으로 보아, K class에 nike어레이를 사용하시는 듯하네요.
어레이의 컨트롤러(SP)가 한개 고장난듯 합니다.
고장난 컨트롤러를 교체하세요~
제 기억에 나이키는 한쪽 컨트롤러 고장나면, 성능이 엄청 떨어지던것으로 기억합니다. 그러니 얼렁 연락하셔서 교체해 주세요
그럼..
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 친구에게 이메일 보내기
- 부적절한 컨텐트 신고
날짜: 11-19-2004 11:00 PM
날짜: 11-19-2004 11:00 PM
event.log좀 봐주세요...추가질문있습니다....또 추가질문여.
모든분들 답변 감사드립니다..
-----mstm 내용--------
10/8.0 C2300 Array (DGCC2300WDR5 Information Successful
10/8.1 C2300 Array (DGCC2300WDR5 Information Successful
-----expert내용-------
Thu Aug 1 13:44:19 2002
Thu Aug 1 13:44:19 2002: Expert tool (scsi_nike) starting on path (10/8.0).
Thu Aug 1 13:46:05 2002: Tool completed with exit_status SUCCESSFUL (0)
indicating tool completed without errors.
모두 정상으로 보여지는데..정상적인것인가요?
-----mstm 내용--------
10/8.0 C2300 Array (DGCC2300WDR5 Information Successful
10/8.1 C2300 Array (DGCC2300WDR5 Information Successful
-----expert내용-------
Thu Aug 1 13:44:19 2002
Thu Aug 1 13:44:19 2002: Expert tool (scsi_nike) starting on path (10/8.0).
Thu Aug 1 13:46:05 2002: Tool completed with exit_status SUCCESSFUL (0)
indicating tool completed without errors.
모두 정상으로 보여지는데..정상적인것인가요?
위에 명시된 의견은 Hewlett Packard Enterprise가 아닌 저자의 개인 의견입니다. 이 사이트를 사용하면 이용 약관에 동의하게되며 참여 규칙 .