LoveUnix » 其他UNIX & Linux » HP rp5470 ds2405 疑问
让LU留住您的每

一天 让LU博客留住您的每一天
2007-7-23 17:59 michaelchen
HP rp5470 ds2405 疑问

dmesg.log and event.log  referral attachments!
THK!

2007-7-23 18:41 Nothing
有没有搞错。还是个RAR?

2007-7-23 19:24 michaelchen
回复 #2 Nothing 的帖子

Jul 22 14:58
...
tlan3: Reset looper timeout: DMA timeout occurred at 0/0/0/0
btlan3: reset state is 550 at 0/0/0/0....
btlan3: WARNING: AUI Loopback Failed at 0/0/0/0....
btlan3: NOTE: MII Link Status Not OK - Switch Connection to AUI at 0/0/0/0....
btlan3: Reset looper timeout: DMA timeout occurred at 0/0/0/0
btlan3: reset state is 550 at 0/0/0/0....
btlan3: WARNING: AUI Loopback Failed at 0/0/0/0....
btlan: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/3/0/0/5/0....
btlan: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 0/1/0/0/7/0....
LVM: Path (device 0x1f0b4000) to PV 0 in VG 7 Failed!

SCSI: Async write error -- dev: b 31 0x0a4000, errno: 5, resid: 2048,
        blkno: 16388944, sectno: 32777888, offset: -397590528, bcount: 2048.

SCSI: Async write error -- dev: b 31 0x0a4000, errno: 5, resid: 2048,
        blkno: 4944, sectno: 9888, offset: 5062656, bcount: 2048.
LVM: vg[7]: pvnum=0 (dev_t=0x1f0a4000) is POWERFAILED
LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000491fd000), from raw device 0x1f0a4000 (with priority: 0, and current flags: 0x10) to raw device 0x1f0b4000 (with priority: 1, and current flags: 0x10).
0/8/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/8/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/9/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/9/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/8/0/0: 'World-wide name' (unique identifier) for device at nport ID 0xe1 has
changed. If the device has been replaced intentionally, please use the
fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
0/8/0/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
returned by nport ID 0xe1. FLOGI/PLOGI Fail Code = 0x6.

0/8/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/8/0/0: 'World-wide name' (unique identifier) for device at nport ID 0xe1 has
changed. If the device has been replaced intentionally, please use the
fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
0/8/0/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
returned by nport ID 0xe1. FLOGI/PLOGI Fail Code = 0x6.

0/8/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/8/0/0: 'World-wide name' (unique identifier) for device at nport ID 0xe1 has
changed. If the device has been replaced intentionally, please use the
fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
0/8/0/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
returned by nport ID 0xe1. FLOGI/PLOGI Fail Code = 0x6.

0/8/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/8/0/0: 'World-wide name' (unique identifier) for device at nport ID 0xe1 has
changed. If the device has been replaced intentionally, please use the
fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
0/8/0/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
returned by nport ID 0xe1. FLOGI/PLOGI Fail Code = 0x6.

0/8/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/9/0/0: 'World-wide name' (unique identifier) for device at nport ID 0xe1 has
changed. If the device has been replaced intentionally, please use the
fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
0/9/0/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
returned by nport ID 0xe1. FLOGI/PLOGI Fail Code = 0x6.

0/9/0/0: Unable to access previously accessed device at nport ID 0xe1.
0/9/0/0: 'World-wide name' (unique identifier) for device at nport ID 0xe1 has
changed. If the device has been replaced intentionally, please use the
fcmsutil(1M) command's replace_dsk option to allow the new device to be used.
0/9/0/0: Fibre Channel Driver detected a parse error in the FLOGI/PLOGI response
returned by nport ID 0xe1. FLOGI/PLOGI Fail Code = 0x6.

0/9/0/0: Unable to access previously accessed device at nport ID 0xe1.

2007-7-23 19:29 michaelchen
回复 #3 michaelchen 的帖子

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

Notification Time: Thu Jan 29 09:33:31 2004

wzp002 sent Event Monitor Restart information:

Title: dm_memory
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_memory
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  6570

Resources currently monitored:
/system/events/memory/192

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

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

Notification Time: Thu Jan 29 09:33:33 2004

wzp002 sent Event Monitor Restart information:

Title: lpmc_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/lpmc_em
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  6670

Resources currently monitored:
/system/events/cpu/lpmc/cache_errors

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

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

Notification Time: Thu Jan 29 09:33:34 2004

wzp002 sent Event Monitor Restart information:

Title: sysstat_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
Vendor: Hewlett-Packard Company
Version: A.01.00
Monitor PID:  6868

Resources currently monitored:
/system/events/system_status/ui_host/wzp002

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

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

Notification Time: Thu Jan 29 09:33:37 2004

wzp002 sent Event Monitor Restart information:

Title: dm_FCMS_adapter
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_FCMS_adapter
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  6951

Resources currently monitored:
/adapters/events/FC_adapter/0_8_0_0.8
/adapters/events/FC_adapter/0_9_0_0.8
/adapters/events/FC_adapter/0_10_0_0.8
/adapters/events/FC_adapter/0_12_0_0.8

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

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

Notification Time: Thu Jan 29 09:33:39 2004

wzp002 sent Event Monitor Restart information:

Title: dm_stape
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
Vendor: Hewlett-Packard Company
Version: B.01.05
Monitor PID:  7280

Resources currently monitored:
/storage/events/tapes/SCSI_tape/0_0_1_0.0.0

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

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

Notification Time: Thu Jan 29 10:51:12 2004

wzp002 sent Event Monitor Restart information:

Title: disk_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  3182

Resources currently monitored:
/storage/events/disks/default/0_0_1_1.0.0
/storage/events/disks/default/0_0_2_0.0.0
/storage/events/disks/default/0_2_0_0.8.0
/storage/events/disks/default/0_2_0_0.10.0
/storage/events/disks/default/0_2_0_0.12.0
/storage/events/disks/default/0_2_0_0.14.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.0.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.1.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.2.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.3.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.4.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.5.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.6.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.7.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.8.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.9.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.0.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.1.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.2.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.3.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.4.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.5.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.6.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.7.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.8.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.9.0
/storage/events/disks/default/0_10_0_0.8.0.255.0.0.0
/storage/events/disks/default/0_10_0_0.8.0.255.0.1.0
/storage/events/disks/default/0_10_0_0.8.0.255.0.2.0

INTERNAL ERROR: an internal error occurred while processing the restart
notification message. Some portion of the message may not be displayed.

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

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

Notification Time: Thu Jan 29 10:51:14 2004

wzp002 sent Event Monitor notification information:

/adapters/events/TL_adapter/0_8_0_0 is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Thu Jan 29 10:51:14 2004
Severity............: INFORMATION
Monitor.............: dm_TL_adapter
Event #.............: 18                  
System..............: wzp002

Summary:
     Adapter at hardware path 0/8/0/0 : Received an interrupt indicating that a
     primitive was transmitted


Description of Error:


lbolt value: 5777

   The Fibre Channel Driver received an interrupt indicating  
   that a primitive was transmitted
   Frame Manager Status Register =  0xa002c480


Probable Cause / Recommended Action:

The Tachyon TL adapter transmitted a primitive sequence.
  This is caused by the driver issuing a primitive sequence
  to the chip to be transmitted.
  No action is required. Informative message

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x4018752200000000
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          0x401873c600000000
     Additional System Data:
          System Model Number.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          EMS Version.....................: A.03.20
          STM Version.....................: A.34.00
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#18[/url]

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:
    Physical Device Path....: 0/8/0/0
    Vendor Id...............: 0x0000103C
    Serial Number(WWN)......: 50060B000023F6F2

I/O Log Event Data:

     Driver Status Code..................: 0x00000012
     Length of Logged Hardware Status....: 0 bytes.
     Offset to Logged Manager Information: 0 bytes.
     Length of Logged Manager Information: 47 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:  
00000006 00001691 00000001 00000001 A002C480 2F75782F 636F7265 2F6B6572
6E2F7773 696F2F74 645F6973 722E63





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

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

Notification Time: Thu Jan 29 10:51:14 2004

wzp002 sent Event Monitor notification information:

/adapters/events/TL_adapter/0_8_0_0 is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Thu Jan 29 10:51:14 2004
Severity............: INFORMATION
Monitor.............: dm_TL_adapter
Event #.............: 19                  
System..............: wzp002

Summary:
     Adapter at hardware path 0/8/0/0 : Received an interrupt indicating that a
     primitive was received


Description of Error:


lbolt value: 5777

   The Fibre Channel Driver received an interrupt indicating  
   that a primitive was received
   Frame Manager Status Register =  0xa002c480


Probable Cause / Recommended Action:

The Tachyon TL adapter received a primitive sequence.
  No action needed. Informative message.

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x4018752200000002
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          0x401873c600000001
     Additional System Data:
          System Model Number.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          EMS Version.....................: A.03.20
          STM Version.....................: A.34.00
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#19[/url]

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:
    Physical Device Path....: 0/8/0/0
    Vendor Id...............: 0x0000103C
    Serial Number(WWN)......: 50060B000023F6F2

I/O Log Event Data:

     Driver Status Code..................: 0x00000013
     Length of Logged Hardware Status....: 0 bytes.
     Offset to Logged Manager Information: 0 bytes.
     Length of Logged Manager Information: 47 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:  
00000006 00001691 00000001 00000001 A002C480 2F75782F 636F7265 2F6B6572
6E2F7773 696F2F74 645F6973 722E63





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

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

Notification Time: Thu Jan 29 10:51:20 2004

wzp002 sent Event Monitor Restart information:

Title: dm_TL_adapter
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_TL_adapter
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  5250

Resources currently monitored:
/adapters/events/TL_adapter/0_8_0_0
/adapters/events/TL_adapter/0_9_0_0
/adapters/events/TL_adapter/0_10_0_0
/adapters/events/TL_adapter/0_12_0_0
/adapters/events/TL_adapter/0_10_0_0.8.0.255.0
/adapters/events/TL_adapter/0_8_0_0.8
/adapters/events/TL_adapter/0_9_0_0.8
/adapters/events/TL_adapter/0_10_0_0.8
/adapters/events/TL_adapter/0_12_0_0.8.0.255.0
/adapters/events/TL_adapter/0_12_0_0.8
/adapters/events/TL_adapter/0_8_0_0.8.0.255.0
/adapters/events/TL_adapter/0_9_0_0.8.0.255.0

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

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

Notification Time: Thu Jan 29 10:51:22 2004

wzp002 sent Event Monitor Restart information:

Title: dm_core_hw
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  6475

Resources currently monitored:
/system/events/core_hw/core_hw

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

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

Notification Time: Thu Jan 29 10:51:27 2004

wzp002 sent Event Monitor Restart information:

Title: dm_ses_enclosure
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_ses_enclosure
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  6709

Resources currently monitored:
/storage/events/enclosures/ses_enclosure/0_10_0_0.8.0.255.0.15.0
/storage/events/enclosures/ses_enclosure/0_12_0_0.8.0.255.0.15.0
/storage/events/enclosures/ses_enclosure/0_8_0_0.8.0.255.0.15.0
/storage/events/enclosures/ses_enclosure/0_9_0_0.8.0.255.0.15.0

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

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

Notification Time: Thu Jan 29 10:51:28 2004

wzp002 sent Event Monitor Restart information:

Title: dm_memory
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_memory
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  7276

Resources currently monitored:
/system/events/memory/192

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

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

Notification Time: Thu Jan 29 10:51:30 2004

wzp002 sent Event Monitor Restart information:

Title: lpmc_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/lpmc_em
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  7354

Resources currently monitored:
/system/events/cpu/lpmc/cache_errors

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

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

Notification Time: Thu Jan 29 10:51:30 2004

wzp002 sent Event Monitor Restart information:

Title: sysstat_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
Vendor: Hewlett-Packard Company
Version: A.01.00
Monitor PID:  7600

Resources currently monitored:
/system/events/system_status/ui_host/wzp002

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

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

Notification Time: Thu Jan 29 10:51:34 2004

wzp002 sent Event Monitor Restart information:

Title: dm_FCMS_adapter
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_FCMS_adapter
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  7651

Resources currently monitored:
/adapters/events/FC_adapter/0_8_0_0.8
/adapters/events/FC_adapter/0_9_0_0.8
/adapters/events/FC_adapter/0_10_0_0.8
/adapters/events/FC_adapter/0_12_0_0.8

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

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

Notification Time: Thu Jan 29 10:51:36 2004

wzp002 sent Event Monitor Restart information:

Title: dm_stape
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
Vendor: Hewlett-Packard Company
Version: B.01.05
Monitor PID:  8068

Resources currently monitored:
/storage/events/tapes/SCSI_tape/0_0_1_0.0.0

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

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

Notification Time: Thu Jan 29 11:23:00 2004

wzp002 sent Event Monitor Restart information:

Title: disk_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  3213

Resources currently monitored:
/storage/events/disks/default/0_0_1_1.0.0
/storage/events/disks/default/0_0_2_0.0.0
/storage/events/disks/default/0_2_0_0.8.0
/storage/events/disks/default/0_2_0_0.10.0
/storage/events/disks/default/0_2_0_0.12.0
/storage/events/disks/default/0_2_0_0.14.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.0.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.1.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.2.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.3.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.4.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.5.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.6.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.7.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.8.0
/storage/events/disks/default/0_8_0_0.8.0.255.0.9.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.0.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.1.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.2.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.3.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.4.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.5.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.6.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.7.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.8.0
/storage/events/disks/default/0_9_0_0.8.0.255.0.9.0
/storage/events/disks/default/0_10_0_0.8.0.255.0.0.0
/storage/events/disks/default/0_10_0_0.8.0.255.0.1.0
/storage/events/disks/default/0_10_0_0.8.0.255.0.2.0

INTERNAL ERROR: an internal error occurred while processing the restart
notification message. Some portion of the message may not be displayed.

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

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

Notification Time: Thu Jan 29 11:23:02 2004

wzp002 sent Event Monitor notification information:

/adapters/events/TL_adapter/0_8_0_0 is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Thu Jan 29 11:23:02 2004
Severity............: INFORMATION
Monitor.............: dm_TL_adapter
Event #.............: 18                  
System..............: wzp002

Summary:
     Adapter at hardware path 0/8/0/0 : Received an interrupt indicating that a
     primitive was transmitted


Description of Error:


lbolt value: 5777

   The Fibre Channel Driver received an interrupt indicating  
   that a primitive was transmitted
   Frame Manager Status Register =  0xa002c480


Probable Cause / Recommended Action:

The Tachyon TL adapter transmitted a primitive sequence.
  This is caused by the driver issuing a primitive sequence
  to the chip to be transmitted.
  No action is required. Informative message

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x40187c9600000000
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          0x40187b3e00000000
     Additional System Data:
          System Model Number.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          EMS Version.....................: A.03.20
          STM Version.....................: A.34.00
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#18[/url]

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:
    Physical Device Path....: 0/8/0/0
    Vendor Id...............: 0x0000103C
    Serial Number(WWN)......: 50060B000023F6F2

I/O Log Event Data:

     Driver Status Code..................: 0x00000012
     Length of Logged Hardware Status....: 0 bytes.
     Offset to Logged Manager Information: 0 bytes.
     Length of Logged Manager Information: 47 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:  
00000006 00001691 00000001 00000001 A002C480 2F75782F 636F7265 2F6B6572
6E2F7773 696F2F74 645F6973 722E63





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

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

Notification Time: Thu Jan 29 11:23:02 2004

wzp002 sent Event Monitor notification information:

/adapters/events/TL_adapter/0_8_0_0 is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Thu Jan 29 11:23:02 2004
Severity............: INFORMATION
Monitor.............: dm_TL_adapter
Event #.............: 19                  
System..............: wzp002

Summary:
     Adapter at hardware path 0/8/0/0 : Received an interrupt indicating that a
     primitive was received


Description of Error:


lbolt value: 5777

   The Fibre Channel Driver received an interrupt indicating  
   that a primitive was received
   Frame Manager Status Register =  0xa002c480


Probable Cause / Recommended Action:

The Tachyon TL adapter received a primitive sequence.
  No action needed. Informative message.

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x40187c9600000002
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          0x40187b3e00000001
     Additional System Data:
          System Model Number.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          EMS Version.....................: A.03.20
          STM Version.....................: A.34.00
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#19[/url]

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:
    Physical Device Path....: 0/8/0/0
    Vendor Id...............: 0x0000103C
    Serial Number(WWN)......: 50060B000023F6F2

I/O Log Event Data:

     Driver Status Code..................: 0x00000013
     Length of Logged Hardware Status....: 0 bytes.
     Offset to Logged Manager Information: 0 bytes.
     Length of Logged Manager Information: 47 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:  
00000006 00001691 00000001 00000001 A002C480 2F75782F 636F7265 2F6B6572
6E2F7773 696F2F74 645F6973 722E63





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

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

Notification Time: Thu Jan 29 11:23:07 2004

wzp002 sent Event Monitor Restart information:

Title: dm_TL_adapter
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_TL_adapter
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  5620

Resources currently monitored:
/adapters/events/TL_adapter/0_8_0_0
/adapters/events/TL_adapter/0_9_0_0
/adapters/events/TL_adapter/0_10_0_0
/adapters/events/TL_adapter/0_12_0_0
/adapters/events/TL_adapter/0_10_0_0.8.0.255.0
/adapters/events/TL_adapter/0_8_0_0.8
/adapters/events/TL_adapter/0_9_0_0.8
/adapters/events/TL_adapter/0_10_0_0.8
/adapters/events/TL_adapter/0_12_0_0.8.0.255.0
/adapters/events/TL_adapter/0_12_0_0.8
/adapters/events/TL_adapter/0_8_0_0.8.0.255.0
/adapters/events/TL_adapter/0_9_0_0.8.0.255.0

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

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

Notification Time: Thu Jan 29 11:23:09 2004

wzp002 sent Event Monitor Restart information:

Title: dm_core_hw
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  6732

Resources currently monitored:
/system/events/core_hw/core_hw

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

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

Notification Time: Thu Jan 29 11:23:14 2004

wzp002 sent Event Monitor Restart information:

Title: dm_ses_enclosure
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_ses_enclosure
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  7051

Resources currently monitored:
/storage/events/enclosures/ses_enclosure/0_10_0_0.8.0.255.0.15.0
/storage/events/enclosures/ses_enclosure/0_12_0_0.8.0.255.0.15.0
/storage/events/enclosures/ses_enclosure/0_8_0_0.8.0.255.0.15.0
/storage/events/enclosures/ses_enclosure/0_9_0_0.8.0.255.0.15.0

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

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

Notification Time: Thu Jan 29 11:23:15 2004

wzp002 sent Event Monitor Restart information:

Title: dm_memory
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_memory
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  7587

Resources currently monitored:
/system/events/memory/192

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

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

Notification Time: Thu Jan 29 11:23:17 2004

wzp002 sent Event Monitor Restart information:

Title: lpmc_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/lpmc_em
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  7663

Resources currently monitored:
/system/events/cpu/lpmc/cache_errors

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

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

Notification Time: Thu Jan 29 11:23:17 2004

wzp002 sent Event Monitor Restart information:

Title: sysstat_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
Vendor: Hewlett-Packard Company
Version: A.01.00
Monitor PID:  7853

Resources currently monitored:
/system/events/system_status/ui_host/wzp002

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

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

Notification Time: Thu Jan 29 11:23:21 2004

wzp002 sent Event Monitor Restart information:

Title: dm_FCMS_adapter
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_FCMS_adapter
Vendor: Hewlett-Packard Company
Version: B.01.00
Monitor PID:  7906

Resources currently monitored:
/adapters/events/FC_adapter/0_8_0_0.8
/adapters/events/FC_adapter/0_9_0_0.8
/adapters/events/FC_adapter/0_10_0_0.8
/adapters/events/FC_adapter/0_12_0_0.8

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

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

Notification Time: Thu Jan 29 11:23:23 2004

wzp002 sent Event Monitor Restart information:

Title: dm_stape
Command: /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
Vendor: Hewlett-Packard Company
Version: B.01.05
Monitor PID:  8241

Resources currently monitored:
/storage/events/tapes/SCSI_tape/0_0_1_0.0.0

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

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

Notification Time: Thu Jan 29 16:20:41 2004

wzp002 sent Event Monitor notification information:

/storage/events/disks/default/0_2_0_0.8.0 is >= 1.
Its current value is MAJORWARNING(3).



Event data from monitor:

Event Time..........: Thu Jan 29 16:20:41 2004
Severity............: MAJORWARNING
Monitor.............: disk_em
Event #.............: 100091              
System..............: wzp002

Summary:
     Disk at hardware path 0/2/0/0.8.0 : Software configuration error


Description of Error:

     The device is in a condition where it requires action on the part of the
     device driver or a human operator.

Probable Cause / Recommended Action:

     The device has been reset by a Bus Device Reset message, a hard reset
     condition, or a power-on reset.

     If this is the case, no action is necessary.

     Alternatively, a removable medium has been loaded or replaced.

     If this is the case, no action is necessary.

     Alternatively, the mode parameters, microcode, or inquiry data for the
     device have been changed.

     If this is the case, no action is necessary.

     Alternatively, the installed version of the device driver does not match
     that of the installed version of HP-UX. Install the correct version of the
     driver.

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x4018c25900000000
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_disk_em.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          0x4018c25900000000
     Additional System Data:
          System Model Number.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          STM Version.....................: A.34.00
          EMS Version.....................: A.03.20
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091[/url]

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:
     Physical Device Path...: 0/2/0/0.8.0
     Device Class...........: Disk
     Inquiry Vendor ID......: HP 36.4G
     Inquiry Product ID.....: ST336753LC      
     Firmware Version.......: HPC4
     Serial Number..........: 3HX1RAZZ00007423JHE5

Product/Device Identification Information:

     Logger ID.........: sdisk
     Product Identifier: SCSI Disk
     Product Qualifier.: HP36.4GST336753LC
     SCSI Target ID....: 0x08
     SCSI LUN..........: 0x00

I/O Log Event Data:

     Driver Status Code..................: 0x0000007E
     Length of Logged Hardware Status....: 22 bytes.
     Offset to Logged Manager Information: 24 bytes.
     Length of Logged Manager Information: 34 bytes.

Hardware Status:

     Raw H/W Status:
          0x0000: 00 00 00 02   70 00 06 00   00 00 00 0A   00 00 00 00
          0x0010: 29 02 02 00   00 00

     SCSI Status...: CHECK CONDITION (0x02)
          Indicates that a contingent allegiance condition has occurred.  Any
          error, exception, or abnormal condition that causes sense data to be
          set will produce the CHECK CONDITION status.
     
SCSI Sense Data:

     Undecoded Sense Data:
          0x0000: 70 00 06 00   00 00 00 0A   00 00 00 00   29 02 02 00
          0x0010: 00 00
     
     SCSI Sense Data Fields:
          Error Code                      : 0x70
          Segment Number                  : 0x00
          Bit Fields:      
               Filemark                   : 0
               End-of-Medium              : 0
               Incorrect Length Indicator : 0
          Sense Key                       : 0x06
          Information Field Valid         : FALSE               
          Information Field               : 0x00000000
          Additional Sense Length         : 10
          Command Specific                : 0x00000000
          Additional Sense Code           : 0x29
          Additional Sense Qualifier      : 0x02
          Field Replaceable Unit          : 0x02
          Sense Key Specific Data Valid   : FALSE               
          Sense Key Specific Data         : 0x00 0x00 0x00
                       
          Sense Key 0x06, UNIT ATTENTION, indicates that the target has been
          reset by a BUS DEVICE RESET message, a hard reset condition, or by a
          power-on reset. If not a reset, then one of the following may have
          occurred.
             1. A removable medium may have been changed.
             2. The mode parameters in effect for this initiator have been
             changed by another initiator.
             3. The version or level of microcode has been changed.
             4. Tagged commands queued for this initiator were cleared by
             another initiator.
             5. INQUIRY data has been changed.
             6. The mode parameters in effect for this initiator have been
             restored from non-volatile memory.
             7. A change in the condition of a synchronized spindle.
             8. Any other event that requires the attention of the initiator.

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 2A 00 01 82   F0 B0 00 00   06 00
     
     Command Data Block Fields (10-byte fmt):
          Command Operation Code...(0x2A)..: WRITE
          Logical Unit Number..............: 0
          DPO Bit..........................: 0
          FUA Bit..........................: 0
          Relative Address Bit.............: 0
          Logical Block Address............: 25358512 (0x0182F0B0)
          Transfer Length..................: 6 (0x0006)

Manager-Specific Data Fields:
     Request ID.............: 0x08094139
     Data Residue...........: 0x00000C00
     CDB status.............: 0x00000002
     Sense Status...........: 0x00000000
     Bus ID.................: 0x08
     Target ID..............: 0x08
     LUN ID.................: 0x00
     Sense Data Length......: 0x12
     Q Tag..................: 0x73
     Retry Count............: 0


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

2007-7-23 19:30 michaelchen
回复 #4 michaelchen 的帖子

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

Notification Time: Sun Nov  5 07:16:32 2006

wzp002 sent Event Monitor notification information:

/storage/events/disks/default/0_8_0_0.8.0.255.0.1.0
is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Sun Nov  5 07:16:32 2006
Severity............: INFORMATION
Monitor.............: disk_em
Event #.............: 6                  
System..............: wzp002

Summary:
     Disk at hardware path 0/8/0/0.8.0.255.0.1.0 : New grown-defects have been
     added to the defect list.


Description of Error:

     One or more new grown-defects have been added to the list. This indicates
     that the disk was having difficulty reading or writing data blocks and
     those data blocks were successfully relocated with no data loss.

Probable Cause / Recommended Action:

     During an I/O operation, one or more bad sectors were found and
     automatically reallocated. The operation was successful. Occasional growth
     in the defect list is to be expected. If defects are added to the list
     frequently, contact your HP support representative to check the disk
     mechanism.

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x454d1f5000000000
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_disk_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.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          STM Version.....................: A.34.00
          EMS Version.....................: A.03.20
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/disk_em.htm#6[/url]

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:
     Physical Device Path...: 0/8/0/0.8.0.255.0.1.0
     Device Class...........: Disk
     Inquiry Vendor ID......: HP 36.4G
     Inquiry Product ID.....: ST336753FC      
     Firmware Version.......: HP03
     Serial Number..........: 3HX1RL8Q            

Product/Device Identification Information:

     Logger ID.........: disc30; sdisk
     Product Identifier: Disk
     Product Qualifier.: HP 36.4GST336753FC      
     SCSI Target ID....: 0x01
     SCSI LUN..........: 0x00

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 37 00 0D 00   00 00 00 FF   FF 00
     
     Command Data Block Fields (10-byte fmt):
          Command Operation Code...(0x37)..: READ DEFECT DATA
          Logical Unit Number..............: 0
          Primary Defect List Bit..........: 0
          Grown Defect List Bit............: 1
          Defect List Format Bits..........: 5
          Allocation Length................: 65535 (0xFFFF)

Additional Event Details :
     Number of new defects or errors.: 10
     Time interval ..................: 209 Day(s), 20 Hour(s), 55 Minute(s) and
     40 Second(s)
     Current number of defects/errors: 11


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

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

Notification Time: Sun Nov  5 07:16:42 2006

wzp002 sent Event Monitor notification information:

/storage/events/disks/default/0_9_0_0.8.0.255.0.1.0
is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Sun Nov  5 07:16:42 2006
Severity............: INFORMATION
Monitor.............: disk_em
Event #.............: 6                  
System..............: wzp002

Summary:
     Disk at hardware path 0/9/0/0.8.0.255.0.1.0 : New grown-defects have been
     added to the defect list.


Description of Error:

     One or more new grown-defects have been added to the list. This indicates
     that the disk was having difficulty reading or writing data blocks and
     those data blocks were successfully relocated with no data loss.

Probable Cause / Recommended Action:

     During an I/O operation, one or more bad sectors were found and
     automatically reallocated. The operation was successful. Occasional growth
     in the defect list is to be expected. If defects are added to the list
     frequently, contact your HP support representative to check the disk
     mechanism.

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x454d1f5a00000000
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_disk_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.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          STM Version.....................: A.34.00
          EMS Version.....................: A.03.20
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/disk_em.htm#6[/url]

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:
     Physical Device Path...: 0/9/0/0.8.0.255.0.1.0
     Device Class...........: Disk
     Inquiry Vendor ID......: HP 36.4G
     Inquiry Product ID.....: ST336753FC      
     Firmware Version.......: HP03
     Serial Number..........: 3HX1RL8Q            

Product/Device Identification Information:

     Logger ID.........: disc30; sdisk
     Product Identifier: Disk
     Product Qualifier.: HP 36.4GST336753FC      
     SCSI Target ID....: 0x01
     SCSI LUN..........: 0x00

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 37 00 0D 00   00 00 00 FF   FF 00
     
     Command Data Block Fields (10-byte fmt):
          Command Operation Code...(0x37)..: READ DEFECT DATA
          Logical Unit Number..............: 0
          Primary Defect List Bit..........: 0
          Grown Defect List Bit............: 1
          Defect List Format Bits..........: 5
          Allocation Length................: 65535 (0xFFFF)

Additional Event Details :
     Number of new defects or errors.: 10
     Time interval ..................: 209 Day(s), 20 Hour(s), 55 Minute(s) and
     39 Second(s)
     Current number of defects/errors: 11


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

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

Notification Time: Tue Nov  7 16:34:14 2006

wzp002 sent Event Monitor notification information:

/storage/events/disks/default/0_8_0_0.8.0.255.0.1.0
is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Tue Nov  7 16:34:14 2006
Severity............: CRITICAL
Monitor.............: disk_em
Event #.............: 101037              
System..............: wzp002

Summary:
     Disk at hardware path 0/8/0/0.8.0.255.0.1.0 : Media failure


Description of Error:

     The device was unsuccessful in reading or writing data for the current I/O
     request due to a data synchronization mark error on the medium.

Probable Cause / Recommended Action:

     Reformatting the medium may fix the problem.

     Alternatively, the medium in the device is flawed. If the medium is
     removable, replace the medium with a fresh one.

     Alternatively, if the medium is not removable, the device has experienced
     a hardware failure. Contact your HP support representative to have the
     device checked.

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x4550450600000000
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_disk_em.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          0x4550450600000000
     Additional System Data:
          System Model Number.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          STM Version.....................: A.34.00
          EMS Version.....................: A.03.20
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#101037[/url]

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:
     Physical Device Path...: 0/8/0/0.8.0.255.0.1.0
     Device Class...........: Disk
     Inquiry Vendor ID......: HP 36.4G
     Inquiry Product ID.....: ST336753FC      
     Firmware Version.......: HP03
     Serial Number..........: 3HX1RL8Q            

Product/Device Identification Information:

     Logger ID.........: sdisk
     Product Identifier: SCSI Disk
     Product Qualifier.: HP36.4GST336753FC
     SCSI Target ID....: 0x01
     SCSI LUN..........: 0x00

I/O Log Event Data:

     Driver Status Code..................: 0x0000007C
     Length of Logged Hardware Status....: 22 bytes.
     Offset to Logged Manager Information: 24 bytes.
     Length of Logged Manager Information: 34 bytes.

Hardware Status:

     Raw H/W Status:
          0x0000: 00 00 00 02   F0 00 03 00   0C 58 39 0A   00 00 00 00
          0x0010: 16 00 D2 80   00 86

     SCSI Status...: CHECK CONDITION (0x02)
          Indicates that a contingent allegiance condition has occurred.  Any
          error, exception, or abnormal condition that causes sense data to be
          set will produce the CHECK CONDITION status.
     
SCSI Sense Data:

     Undecoded Sense Data:
          0x0000: F0 00 03 00   0C 58 39 0A   00 00 00 00   16 00 D2 80
          0x0010: 00 86
     
     SCSI Sense Data Fields:
          Error Code                      : 0x70
          Segment Number                  : 0x00
          Bit Fields:      
               Filemark                   : 0
               End-of-Medium              : 0
               Incorrect Length Indicator : 0
          Sense Key                       : 0x03
          Information Field Valid         : TRUE
          Information Field               : 0x000C5839
          Additional Sense Length         : 10
          Command Specific                : 0x00000000
          Additional Sense Code           : 0x16
          Additional Sense Qualifier      : 0x00
          Field Replaceable Unit          : 0xD2
          Sense Key Specific Data Valid   : TRUE
          Sense Key Specific Data         : 0x80 0x00 0x86
                       
          Sense Key 0x03, MEDIUM ERROR, indicates that the command terminated
          with a nonrecovered error condition that was probably caused by a
          flaw in the medium or an error in the recorded data.  This sense key
          may also be returned if the device is unable to distinguish between a
          flaw in the medium and a specific hardware failure (sense key 0x04).
          For the RECOVERED ERROR, HARDWARE ERROR, or MEDIUM ERROR Sense Key,
          the Sense Key Specific data indicates that 134 retries were
          attempted.
                       
          The combination of Additional Sense Code and Sense Qualifier (0x1600)
          indicates: Data synchronization mark error.

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 28 00 00 0C   58 30 00 00   10 00
     
     Command Data Block Fields (10-byte fmt):
          Command Operation Code...(0x28)..: READ
          Logical Unit Number..............: 0
          DPO Bit..........................: 0
          FUA Bit..........................: 0
          Relative Address Bit.............: 0
          Logical Block Address............: 809008 (0x000C5830)
          Transfer Length..................: 16 (0x0010)

Manager-Specific Data Fields:
     Request ID.............: 0x0A5E2447
     Data Residue...........: 0x00000E00
     CDB status.............: 0x00000002
     Sense Status...........: 0x00000000
     Bus ID.................: 0x0A
     Target ID..............: 0x01
     LUN ID.................: 0x00
     Sense Data Length......: 0x12
     Q Tag..................: 0xF1
     Retry Count............: 45


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

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

Notification Time: Tue Nov  7 16:39:14 2006

wzp002 sent Event Monitor notification information:

/storage/events/disks/default/0_8_0_0.8.0.255.0.1.0
is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Tue Nov  7 16:39:14 2006
Severity............: CRITICAL
Monitor.............: disk_em
Event #.............: 100237              
System..............: wzp002

Summary:
     Disk at hardware path 0/8/0/0.8.0.255.0.1.0 : Media failure


Description of Error:

     The device was unsuccessful in reading or writing data for the current I/O
     request due to an error on the medium. The data could not be recovered.

Probable Cause / Recommended Action:

     Reformatting the medium may fix the problem.

     Alternatively, the medium in the device is flawed. If the medium is
     removable, replace the medium with a fresh one.

     Alternatively, if the medium is not removable, the device has experienced
     a hardware failure. Contact your HP support representative to have the
     device checked.

Additional Event Data:
     System IP Address...: 10.25.130.40
     Event Id............: 0x4550463200000000
     Monitor Version.....: B.01.00
     Event Class.........: I/O
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_disk_em.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          0x4550463200000000
     Additional System Data:
          System Model Number.............: 9000/800/L3000-7x
          OS Version......................: B.11.00
          STM Version.....................: A.34.00
          EMS Version.....................: A.03.20
     Latest information on this event:
          [url]http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100237[/url]

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:
     Physical Device Path...: 0/8/0/0.8.0.255.0.1.0
     Device Class...........: Disk
     Inquiry Vendor ID......: HP 36.4G
     Inquiry Product ID.....: ST336753FC      
     Firmware Version.......: HP03
     Serial Number..........: 3HX1RL8Q            

Product/Device Identification Information:

     Logger ID.........: sdisk
     Product Identifier: SCSI Disk
     Product Qualifier.: HP36.4GST336753FC
     SCSI Target ID....: 0x01
     SCSI LUN..........: 0x00

I/O Log Event Data:

     Driver Status Code..................: 0x0000007C
     Length of Logged Hardware Status....: 22 bytes.
     Offset to Logged Manager Information: 24 bytes.
     Length of Logged Manager Information: 34 bytes.

Hardware Status:

     Raw H/W Status:
          0x0000: 00 00 00 02   F0 00 03 00   0C 5C EC 0A   00 00 00 00
          0x0010: 11 00 E4 80   00 86

     SCSI Status...: CHECK CONDITION (0x02)
          Indicates that a contingent allegiance condition has occurred.  Any
          error, exception, or abnormal condition that causes sense data to be
          set will produce the CHECK CONDITION status.
     
SCSI Sense Data:

     Undecoded Sense Data:
          0x0000: F0 00 03 00   0C 5C EC 0A   00 00 00 00   11 00 E4 80
          0x0010: 00 86
     
     SCSI Sense Data Fields:
          Error Code                      : 0x70
          Segment Number                  : 0x00
          Bit Fields:      
               Filemark                   : 0
               End-of-Medium              : 0
               Incorrect Length Indicator : 0
          Sense Key                       : 0x03
          Information Field Valid         : TRUE
          Information Field               : 0x000C5CEC
          Additional Sense Length         : 10
          Command Specific                : 0x00000000
          Additional Sense Code           : 0x11
          Additional Sense Qualifier      : 0x00
          Field Replaceable Unit          : 0xE4
          Sense Key Specific Data Valid   : TRUE
          Sense Key Specific Data         : 0x80 0x00 0x86
                       
          Sense Key 0x03, MEDIUM ERROR, indicates that the command terminated
          with a nonrecovered error condition that was probably caused by a
          flaw in the medium or an error in the recorded data.  This sense key
          may also be returned if the device is unable to distinguish between a
          flaw in the medium and a specific hardware failure (sense key 0x04).
          For the RECOVERED ERROR, HARDWARE ERROR, or MEDIUM ERROR Sense Key,
          the Sense Key Specific data indicates that 134 retries were
          attempted.
                       
          The combination of Additional Sense Code and Sense Qualifier (0x1100)
          indicates: Unrecovered read error.

SCSI Command Data Block:

     Command Data Block Contents:
          0x0000: 28 00 00 0C   5C E0 00 00   10 00
     
     Command Data Block Fields (10-byte fmt):
          Command Operation Code...(0x28)..: READ
          Logical Unit Number..............: 0
          DPO Bit..........................: 0
          FUA Bit..........................: 0
          Relative Address Bit.............: 0
          Logical Block Address............: 810208 (0x000C5CE0)
          Transfer Length..................: 16 (0x0010)

Manager-Specific Data Fields:
     Request ID.............: 0x0A5E2C01
     Data Residue...........: 0x00000800
     CDB status.............: 0x00000002
     Sense Status...........: 0x00000000
     Bus ID.................: 0x0A
     Target ID..............: 0x01
     LUN ID.................: 0x00
     Sense Data Length......: 0x12
     Q Tag..................: 0xDE
     Retry Count............: 45


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

2007-7-24 15:41 michaelchen
回复 #5 michaelchen 的帖子

rp5470


ds2405 ST336753FC

c6t1d0   0/10/0/0.8.0.255.0.1.0

页: [1]
查看完整版本: HP rp5470 ds2405 疑问


Powered by Discuz! Archiver 5.5.0  © 2001-2006 Comsenz Inc.