topic Re: DISK descriptor errors in Operating System - HP-UX

DISK descriptor errors

Kwahae_1 — Wed, 10 Sep 2008 07:41:18 GMT

Hi,

I am ruuning an HP-UX 11.11 box connected to an EMC Clarrion CX700 disk array. I am getting a lot of errors in my syslog. See attached syslog entries. What could be happening?

Re: DISK descriptor errors

Deepak Kr — Wed, 10 Sep 2008 07:51:14 GMT

Can you check dmesg output

# dmesg -

Also verify that disk is claimed in ioscan
#ioscan -fnC disk |grep

#lssf /dev/dsk/diskname ===how address
#diskinfo -v /dev/rdsk/diskname

Run dd to verify disk data read
#dd if=/dev/dsk/diskname of=/dev/null bs=1024

Re: DISK descriptor errors

Prashanth Waugh — Wed, 10 Sep 2008 09:06:51 GMT

Hi ,

excute the resmon command .

/opt/resmon/bin/resdata -R 349044744 -r /storage/even
ts/tapes/SCSI_tape/0_12_0_0.1.1.255.14.15.0 -n 349044742 -a

check what its showing

Regards
Prashant

Re: DISK descriptor errors

Kwahae_1 — Wed, 10 Sep 2008 09:13:58 GMT

Prashant,

The result is as below:
# r /storage/events/tapes/SCSI_tape/0_12_0_0.1.1.255.14.15.0 -n 349044742 -a <

CURRENT MONITOR DATA:

Event Time..........: Tue Sep 9 16:56:27 2008
Severity............: MAJORWARNING
Monitor.............: dm_stape
Event #.............: 100097
System..............: idmdsprd

Summary:
Disk at hardware path 0/12/0/0.1.1.255.14.15.0 : Recoverable error

Description of Error:

An attempt was made to access a device which was reserved by another
initiator.

Probable Cause / Recommended Action:

The device was unable to process the request at this time. The request
should be retried by the system. No further action is necessary. However,
if the condition persists, there may be hardware problems with the device
or the connectivity to the device.

Alternately, the device may be in the process of recovering from a
powerfail cycle.

Alternately, there may be a problem in the configuration of the
application software which is using the device causing access conflicts or
bottlenecks.

Additional Event Data:
System IP Address...: 192.168.142.22
System IP Address...: 192.168.142.20
Event Id............: 0x48c68e9b00000000
Monitor Version.....: B.01.05
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_stape.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x48c68e9b00000000
Additional System Data:
System Model Number.............: 9000/800/L3000-6x
OS Version......................: B.11.11
System Firmware Version.........: 42.19
System Serial Number............: DEH4305DM6
System Software ID..............: 1136424601
EMS Version.....................: A.03.20
STM Version.....................: A.35.00
System Current Product Number...: A6144B
System Original Product Number..: A6144B
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100097

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/12/0/0.1.1.255.14.15.0
Inquiry Vendor ID.......: unavailable
Inquiry Product ID......: unavailable
Firmware Version........: unavailable
Serial Number...........: unavailable

Product/Device Data:

Logger ID.........: atdd
Product Identifier: (not available/applicable)
Product Qualifier.: (not available/applicable)
SCSI Target ID....: (not available/applicable)
SCSI LUN..........: 0x00

I/O Log Event Data:

Driver Status Code..................: 0x00000005
Length of Logged Hardware Status....: 4 bytes.
Offset to Logged Manager Information: 8 bytes.
Length of Logged Manager Information: 30 bytes.

Hardware Status:

Raw H/W Status:
0x0000: 00 00 00 18

SCSI Status...: RESERVATION CONFLICT (0x18)
Indicates that the driver attempted to access a logical unit or an
extent within a logical unit that was reserved with a conflicting
reservation type for another SCSI device.

SCSI Sense Data: (not present in log record)

SCSI Command Data Block: (not present in log record)

Manager-Specific Information:

Raw Manager Data:
0x0000: 28 00 25 4E 00 00 00 00 00 00 00 18 00 00 00 00
0x0010: 28 0F 00 00 FE 00 00 06 00 00 00 00 00 00

Re: DISK descriptor errors

Sandeep_Chaudhary — Wed, 10 Sep 2008 09:26:11 GMT

check for SCSI reset :lbolt xxxxxxxxxx

errors
here u get ASCII id for disk.

The device that is giving you problem is 0x043300

b 31 - it is disk device. You may have disk problem.

ll /dev/dsk/* | grep 0x043300
This shold be disk c4t3d3
Check that disk - pvdisplay, diskinfo and dd test
dd if=/dev/rdsk/c4t3d3 of=/dev/null bs=1k

Re: DISK descriptor errors

Kwahae_1 — Wed, 10 Sep 2008 09:55:52 GMT

Hi Deepak,

dmesg - does not show any erros.
# dmesg -

Also verify that disk is claimed in ioscan
#ioscan -fnC disk |grep

Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 98 0/10/0/0.4.1.0.0.0.3 sdisk CLAIMED DEVICE DGC CX700WDR10
/dev/dsk/c38t0d3 /dev/rdsk/c38t0d3

#lssf /dev/dsk/diskname ===how address
sdisk card instance 38 SCSI target 0 SCSI LUN 3 section 0 at address 0/10/0/0.4.1.0.0.0.3 /dev/dsk/c38t0d3

#diskinfo -v /dev/rdsk/diskname
SCSI describe of /dev/rdsk/c38t0d3:
vendor: DGC
product id: CX700WDR10
type: direct access
size: 53769024 Kbytes
bytes per sector: 512
rev level: HP03
blocks per disk: 107538048
ISO version: 0
ECMA version: 0
ANSI version: 4
removable media: no
response format: 2
(Additional inquiry bytes: (32)68 (33)32 (34)20 (35)43 (36)4f (37)4e (38)54 (39)52 (40)4f (41)4c (42)4c (43)45 (44)52 (45)20 (46)30 (47)30 (48)30 (49)20 (50)20 (51)0 (52)0 (53)0 (54)3c (55)2 (56)60 (57)1 (58)9c (59)8 (60)c0 (61)13 (62)40 (63)0 (64)0 (65)0 (66)0 (67)0 (68)0 (69)0 (70)0 (71)0 (72)0 (73)0 (74)0 (75)0 (76)0 (77)0 (78)0 (79)0 (80)0 (81)0 (82)0 (83)0 (84)0 (85)0 (86)0 (87)0 (88)0 (89)0 (90)0 (91)2 (92)1 (93)0 (94)0 (95)53 (96)41 (97)33 (98)36 (99)32 (100)30 (101)0 (102)0 (103)0 (104)0 (105)0 (106)0 (107)0 (108)11 (109)8a (110)48 (111)0 (112)11 (113)8a (114)40 (115)0 (116)0 (117)0 (118)0 (119)0 (120)0 (121)0 (122)0 )

Run dd to verify disk data read
#dd if=/dev/dsk/diskname of=/dev/null bs=1024
# dd if=/dev/dsk/c38t0d3 of=/dev/null bs=1024
27551920+0 records in
27551920+0 records out

Re: DISK descriptor errors

Torsten. — Wed, 10 Sep 2008 10:02:44 GMT

Everything on your server is too old.

You are using a diagnostics software from december 2002!

First get a new version:

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=B6191AAE

Re: DISK descriptor errors

Prashanth Waugh — Wed, 10 Sep 2008 10:07:11 GMT

Hi ,

from ur ioscan and dd output it seems that
disk is good also it showing claimed status.

Regards
Prashant