disk 관련 log 문의 드립니다.

[최경민_1]

안녕하세요. 유닉스 초보 입니다.
disk 관련하여 아래와 같은 log가 나왔는데 정확히 어떤 조치를 취해야 할지 알고 싶습니다. 도움 부탁드립니다.
internal disk가 IR Volume 으로 구성 되어있는데 led상으로는 이상이 없습니다. IR Volume로 구성되어있는 disk중 하나가 이상이 있는것 같은데..두개중 어느쪽것인지 알수 없을까요?
==================================================
dmesg
==================================================
Syscall Monitor - ACTIVATED
SAS driver at 0/1/1/0 (/dev/sasd0) : RAID volume at SAS address 0x01c22f91815988a9 is in a degraded state.
SAS driver at 0/1/1/0 (/dev/sasd0) : RAID volume at SAS address 0x01c22f91815988a9 is in a degraded state.
SAS driver at 0/1/1/0 (/dev/sasd0) : RAID volume at SAS address 0x01c22f91815988a9 is in a degraded state.
==================================================
ioscan
==================================================
Class I H/W Path Driver S/W State H/W Type Description
==================================================================================
disk 1 0/1/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c3t0d0 /dev/dsk/c3t0d0s2 /dev/rdsk/c3t0d0 /dev/rdsk/c3t0d0s2
/dev/dsk/c3t0d0s1 /dev/dsk/c3t0d0s3 /dev/rdsk/c3t0d0s1 /dev/rdsk/c3t0d0s3
disk 7 0/4/1/0.2.10.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c12t0d1 /dev/rdsk/c12t0d1
disk 8 0/4/1/0.2.10.0.0.0.2 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c12t0d2 /dev/rdsk/c12t0d2
disk 6 0/4/1/0.2.11.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c14t0d1 /dev/rdsk/c14t0d1
disk 9 0/4/1/0.2.11.0.0.0.2 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c14t0d2 /dev/rdsk/c14t0d2
disk 4 0/4/1/1.1.10.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c8t0d1 /dev/rdsk/c8t0d1
disk 10 0/4/1/1.1.10.0.0.0.2 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c8t0d2 /dev/rdsk/c8t0d2
disk 5 0/4/1/1.1.11.0.0.0.1 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c10t0d1 /dev/rdsk/c10t0d1
disk 11 0/4/1/1.1.11.0.0.0.2 sdisk CLAIMED DEVICE HP HSV300
/dev/dsk/c10t0d2 /dev/rdsk/c10t0d2
disk 12 255/1/0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-V
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
==================================================
event.log
==================================================
>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Tue Jun 10 08:27:38 2008

baeckdu01 sent Event Monitor notification information:

/system/events/system_status/ui_host/baeckdu01
is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Tue Jun 10 08:27:38 2008
Severity............: INFORMATION
Monitor.............: sysstat_em
Event #.............: 100002
System..............: baeckdu01

Summary:
The system baeckdu01 is now responding to the monitor's query.


Description of Error:

This system will now be monitored.

Probable Cause / Recommended Action:

Previously this system was not responding to the monitor's query because
of one of the following reasons :

* system's name could not be resolved to IP address
* the network was down or the network response was poor
"/var/opt/resmon/log/event.log" 3353 lines, 101664 characters
/var/stm/config/tools/monitor/default_dm_sas_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4b1dc12500000000
Additional System Data:
System Model Number.............: ia64 hp server rx2660
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_sas_adapter.htm#33

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



I/O Log Event Data:

Driver Status Code..................: 0x00000021
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 169 bytes.

Manager-Specific Information:

Raw data from SAS MPT SCSI Adapter driver:
01000000 20E099F1 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 544D2028 30783030 30303030 30322920 746F2053 41532061 64647265
73732030 78303163 32326639 31383135 39383861 39202864 65765F74 20307831
66303330 30303229 20666169 6C656420 77697468 20434442 20737461 74757320
30783030 30303034 30





>---------- End Event Monitoring Service Event Notification ----------<

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Wed Dec 9 12:07:20 2009

baeckdu01 sent Event Monitor notification information:

/adapters/events/sas_adapter/0_1_1_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Wed Dec 9 12:07:20 2009
Severity............: CRITICAL
Monitor.............: dm_sas_adapter
Event #.............: 33
System..............: baeckdu01

Summary:
Adapter at hardware path 0/1/1/0 : Task Management function to SAS port
failed.



Description of Error:


lbolt value: 560265711
TM (0x00000002) to SAS address 0x01c22f91815988a9 (dev_t 0x1f030002) failed
with CDB status 0x00000400^M


Probable Cause / Recommended Action:

Task Management function to SAS port failed.
Please check the following:
1) Verify that the device is powered on and is accepting other commands.
2) If the device is accepting other commands, check device internal logs.


Additional Event Data:
System IP Address...: 10.223.20.20
Event Id............: 0x4b1f146800000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_sas_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4b1f140700000000
Additional System Data:
System Model Number.............: ia64 hp server rx2660
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_sas_adapter.htm#33

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



I/O Log Event Data:

Driver Status Code..................: 0x00000021
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 169 bytes.

Manager-Specific Information:

Raw data from SAS MPT SCSI Adapter driver:
01000000 2164F9EF 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 544D2028 30783030 30303030 30322920 746F2053 41532061 64647265
73732030 78303163 32326639 31383135 39383861 39202864 65765F74 20307831
66303330 30303229 20666169 6C656420 77697468 20434442 20737461 74757320
30783030 30303034 30





>---------- End Event Monitoring Service Event Notification ----------<

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Fri Dec 11 11:54:22 2009

baeckdu01 sent Event Monitor notification information:

/adapters/events/sas_adapter/0_1_1_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Fri Dec 11 11:54:22 2009
Severity............: CRITICAL
Monitor.............: dm_sas_adapter
Event #.............: 33
System..............: baeckdu01

Summary:
Adapter at hardware path 0/1/1/0 : Task Management function to SAS port
failed.



Description of Error:


lbolt value: 577466617
TM (0x00000002) to SAS address 0x01c22f91815988a9 (dev_t 0x1f030002) failed
with CDB status 0x00000400^M


Probable Cause / Recommended Action:

Task Management function to SAS port failed.
Please check the following:
1) Verify that the device is powered on and is accepting other commands.
2) If the device is accepting other commands, check device internal logs.


Additional Event Data:
System IP Address...: 10.223.20.20
Event Id............: 0x4b21b45e00000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_sas_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4b21b3f200000000
Additional System Data:
System Model Number.............: ia64 hp server rx2660
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_sas_adapter.htm#33

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



I/O Log Event Data:

Driver Status Code..................: 0x00000021
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 169 bytes.

Manager-Specific Information:

Raw data from SAS MPT SCSI Adapter driver:
01000000 226B70F9 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 544D2028 30783030 30303030 30322920 746F2053 41532061 64647265
73732030 78303163 32326639 31383135 39383861 39202864 65765F74 20307831
66303330 30303229 20666169 6C656420 77697468 20434442 20737461 74757320
30783030 30303034 30





>---------- End Event Monitoring Service Event Notification ----------<

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Sat Dec 12 17:43:25 2009

baeckdu01 sent Event Monitor notification information:

/system/events/system_status/ui_host/baeckdu01
is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Sat Dec 12 17:43:25 2009
Severity............: INFORMATION
Monitor.............: sysstat_em
Event #.............: 100002
System..............: baeckdu01

Summary:
The system baeckdu01 is now responding to the monitor's query.


Description of Error:

This system will now be monitored.

Probable Cause / Recommended Action:

Previously this system was not responding to the monitor's query because
of one of the following reasons :

* system's name could not be resolved to IP address
* the network was down or the network response was poor
* the Online Diagnostic software was not present or was not running on
it

Additional Event Data:
System IP Address...: 10.223.20.20
Event Id............: 0x4b2357ad00000000
Monitor Version.....: B.01.00
Event Class.........: System
Client Configuration File...........:
/var/stm/config/tools/monitor/default_sysstat_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: ia64 hp server rx2660
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/sysstat_em.htm#100002

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Host ID ................: baeckdu01
Host IP Address.........: 10.223.20.20
Host Group Name.........: ui_host


>---------- End Event Monitoring Service Event Notification ----------<

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Dec 14 17:29:11 2009

baeckdu01 sent Event Monitor notification information:

/adapters/events/sas_adapter/0_1_1_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Mon Dec 14 17:29:11 2009
Severity............: CRITICAL
Monitor.............: dm_sas_adapter
Event #.............: 12
System..............: baeckdu01

Summary:
Adapter at hardware path 0/1/1/0 : One or more physical disks in the RAID
volume has failed.



Description of Error:


lbolt value: 17225809
RAID volume at SAS address 0x01c22f91815988a9 is in a degraded state.^M


Probable Cause / Recommended Action:

One or more physical disks in the RAID volume has failed,
but the RAID volume is still operational.
Check all connectors, cables and physical disks.
Reconnect any loose connectors and cables.
Replace failed physical disks immediately.


Additional Event Data:
System IP Address...: 10.223.20.20
Event Id............: 0x4b25f75700000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_sas_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4b25f75200000000
Additional System Data:
System Model Number.............: ia64 hp server rx2660
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.56.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_sas_adapter.htm#12

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



I/O Log Event Data:

Driver Status Code..................: 0x0000000C
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 136 bytes.

Manager-Specific Information:

Raw data from SAS MPT SCSI Adapter driver:
01000000 0106D851 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 52414944 20766F6C 756D6520 61742053 41532061 64647265 73732030
78303163 32326639 31383135 39383861 39206973 20696E20 61206465 67726164
65642073 74617465





>---------- End Event Monitoring Service Event Notification ----------<

[고재진]

안녕하세요. sas 디스크 장애입니다.

디스크 상태를 보는 명령어는
/opt/sas/bin/sasmgr get_info -D /dev/sasd0 -q raid

하시면 디스크 상태보실수 있으실듯합니다.

장애 대처는 장애난 디스크를 온라인중에 빼고 꽂으시면 자동구성됩니다. 그럼..^^

[최경민_1]

답변 주셔서 감사합니다.
알려주신 명령어를 입력한 결과값은 아래와 같습니다. 이상이 없는것 같은데요.. 다른 확인 방법이 있는지요?
Tue Feb 23 18:11:15 2010

---------- LOGICAL DRIVE 1 ----------

Raid Level : RAID 1
Volume sas address : 0x1c22f91815988a9
Device Special File : /dev/rdsk/c3t0d0
Raid State : OPTIMAL
Raid Status Flag : ENABLED
Raid Size : 139236
Rebuild Rate : 0.00 %
Rebuild Progress : 100.00 %

Participating Physical Drive(s) :

SAS Address Enc Bay Size(MB) Type State

0x5000c5001759c25d 1 7 140014 SECONDARY ONLINE
0x5000cca00023d529 1 8 140014 PRIMARY ONLINE

[고재진]

안녕하세요.

우선 지금 disk는 정상이라고 보여집니다.

disk가 장애가 났다가 다시 정상으로 돌아온것 처럼 보여지네요.(종종 생깁니다.)
지금 event.log에서 2009년이후 2010년에는 더이상 로그가 발생하지 않은것 같은데요. 추후 같은 에러로그가 event.log에 발생하면 disk 교체를 진행해야 될것 같습니다.