i/o request failed event # 17

[Alberto Hurtado]

I have the following message:
Event #.............: 17
Severity............: CRITICAL
Monitor.............: disk_em

Summary:
Disk at hardware path 4/1/0.8.0.5.0.2.5 : I/O request failed.
This is in a disk of a box xp-256 with disks spare. These messages had never been presented with those disks. The question is because now the system reports this situation if the box physically doesn't have messages in its internal laptop.

[Jeff Schussele · Accepted solution]

Hi Alberto,

Are there any "accompanying" messages in the server's syslog.log file at roughly the same time. Maybe along the lines of a PV link switch? It may be that your having link timeouts or even failures. These would only show on the server as they aren't array faults per se. And could show up as an I/O request failed - which would trigger the PV link switch & the actual I/O operation would then be actually successfully completed.
If they're timeouts, you may only need to increase the timeout values on the PVs or LVs to give them more time under high load/heavy traffic conditions.

HTH,
Jeff

[Sanjay_6]

Hi,

This is what it says about this error.

/Quote/

Probable Cause / Recommended Action: The bus device reset may have occurred or the device has failed. The bus device reset could have occurred because the power was cycled or that the device is a part of an enclosure and a device in that enclosure was pulled out or put in, or that the interface card had a problem and it reset thebus. If these errors continue, there may be a problem with the device or the card.

/EndQuote/

http://docs.hp.com/hpux/onlinedocs/diag/ems/disk_em.htm

Hope this helps.

Regds

[Andrew Merritt_2]

In addition to the causes listed in the event text, other hardware problems might cause this, such as a faulty or badly connected cable.

I'd recommend a hardware expert to check things out.

Has anything changed on the system recently?

Andrew

[Prashant Zanwar_4]

Try probing the disk through

First check the syslog messages on particular disk. If you have some powerfailed messages or so, and if it has came back online, then check ioscan output.

ioscan -fnC disk | raidscan | grep < particular disk device >

this will help in knowing if anything is wrong.

diskinfo also should help you.

Do a mount -s to see error messages of mount.
If device is alright and you have mount errors, then do vgchange -a y /dev/, this reactivates any de-activated LV's in the VG.

Also let us know what you did in last.

Hope above helps you.

Thanks and rgdz
Prashant

[Prashant Zanwar_4]

I am sorry, it was mount -a.

Thanks
Prashant