Async write error

[Thomas Greig]

Installed a new MAP3735NC Ultra 320 hdd in a HP Surestore Disk System 2100, on a L2000 HP-UX Server with hp-ux 11i.

When I use the disk I get the following error messages in dmesg:

full error-log is in the attatchment.

could this be a hardware-failure on the disk?

SCSI: Async write error -- dev: b 31 0x04e000, errno: 126, resid: 8192,
blkno: 31514328, sectno: 63028656, offset: -2089066496, bcount: 8192.
LVM: Recovered Path (device 0x1f04e000) to PV 0 in VG 5.
LVM: Restored PV 0 to VG 5.
SCSI: First party detected bus hang -- lbolt: 446172, bus: 4
lbp->state: 1060
lbp->offset: 368
lbp->uPhysScript: fa7ef000
From most recent interrupt:
ISTAT: 0a, SIST0: 90, SIST1: 00, DSTAT: 80, DSPS: 004d8000
lsp: 0000000000000000
lbp->owner: 0000000043cd9200
bp->b_dev: 1f04e000
scb->io_id: 414d11d
scb->cdb: 2a 00 04 0c fa e0 00 00 10 00
lbolt_at_timeout: 446072, lbolt_at_start: 445572
lsp->state: 5
scratch_lsp: 0000000048db9400
bp->b_dev: 1f04e000
scb->io_id: 414d11c
scb->cdb: 28 00 04 e8 ed c0 00 00 06 00
lbolt_at_timeout: 448272, lbolt_at_start: 445272
lsp->state: 205
Pre-DSP script dump [fffffffffa7ef070]:
e0100004 00000000 80000000 00000000
890b0000 fa7ef198 880b0000 fa7ef198
Script dump [fffffffffa7ef090]:
83030000 fa7ef368 0b000001 fa7ef5d0
80040000 fa7ef368 0f000001 fa7ef5c1
SCSI: Resetting SCSI -- lbolt: 446272, bus: 4
SCSI: Reset detected -- lbolt: 446272, bus: 4
LVM: Recovered Path (device 0x1f04e000) to PV 0 in VG 5.
LVM: Restored PV 0 to VG 5.

[Naveej.K.A]

Hi,

The error pointed is to the device at c4t15d0, does the ioscan -fnC disk show this device.

have you created the PV for this disk?

Power down your system, check that the scsi cables from the host to the disk station is connected properly.

regds
Naveej

[Robert-Jan Goossens]

Hi,

Could you check this document and the patch PHKL_29527

Document description: SCSI timeouts - large buffer cache configuration
Document id: CMTKBRC00012383

http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000072806646

Regards,
Robert-Jan

[Thomas Greig]

a patch-bundle received from HP solved the problem. the patches no the machine was not up-to-date.