SCSI: Async Write Error

[Ameena Shaik]

Hi All,

Need your help..
I am Getting an error message as follows
in syslog. can any one help me out why these messages occur.

Server model is rp3440 which is connected to XP12K.

SCSI: Async write error -- dev: b 31 0x259000, errno: 13, resid: 1024,
blkno: 13406, sectno: 26812, offset: 13727744, bcount: 1024.

AUTOPATH : Path 0xbc259000 failed! Rerouting to alternate path

SCSI: Async write error -- dev: b 31 0x699000, errno: 13, resid: 1024,
blkno: 13406, sectno: 26812, offset: 13727744, bcount: 1024.

AUTOPATH : Path 0xbc699000 failed! Rerouting to alternate path

SCSI: Async write error -- dev: b 31 0x6e9000, errno: 13, resid: 1024,
blkno: 13406, sectno: 26812, offset: 13727744, bcount: 1024.

AUTOPATH : Path 0xbc6e9000 failed! Rerouting to alternate path

SCSI: Async write error -- dev: b 31 0xa89000, errno: 13, resid: 1024,
blkno: 13406, sectno: 26812, offset: 13727744, bcount: 1024.

AUTOPATH : Path 0xbca89000 failed! Rerouting to alternate path

SCSI: Async write error -- dev: b 31 0x749000, errno: 13, resid: 1024,
blkno: 13406, sectno: 26812, offset: 13727744, bcount: 1024.

AUTOPATH : Path 0xbc749000 failed! Rerouting to alternate path
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.

SCSI: Async write error -- dev: b 31 0x169000, errno: 13, resid: 1024,
blkno: 13406, sectno: 26812, offset: 13727744, bcount: 1024.

AUTOPATH : Path 0xbc169000 failed! Rerouting to alternate path

AUTOPATH : All the paths to the end device 0x1f6e9000 failed!

AUTOPATH : All the paths to the end device 0x1f749000 failed!


Regards,

Ameena Shaik

[johnsonpk]

Hi Ameena,

It seems you have problem in SAN .To isolate the problem
Check for N0_HW in ioscan
check the event.log(/var/opt/resmon/log/event.log)
check the HBA status
ioscan -fnC fc
fcmsutil

Thanks!
Johnson

[Ameena Shaik]

Hi Johnson


I have checked the ioscan output and also checked the HBA status. It is working fine.
Actually we have 4 fc HBA cards all are 2 GB 2 ports FC cards, But only one port is connected on each FC Card.


Regards,
Ameena Shaik.

[johnsonpk]

Hi Ameena,
Is that error still comming in syslog?

You may need to identify the disk by

>>SCSI: Async write error -- dev: b 31 0x699000, errno: 13, resid: 1024,
blkno: 13406, sectno: 26812, offset: 13727744, bcount: 1024.

ls -l /dev/dsk/ |grep 0x699000



and do a pvdisplay to identify the vg
then check the pv status in the vgdisplay


If it is available check in the SAN side for the root cause

Thanks!!
Johnson

[Ganesan R]

Hi,

For me it looks you FC connectivity problem.
All paths from one particular FC card should have failed and because of that i/o is rerouted to the other available path.

You need to check the fc cards, fc connectivity, SAN switch port to confirm both HBA is able to access the luns.

[Viktor Balogh]

check the output of

# fcmsutil /dev/fcd0
# fcmsutil /dev/fcd1
# fcmsutil /dev/fcd2
# fcmsutil /dev/fcd3

If there is a line like:

Driver state = AWAITING_LINK_UP

then something is wrong either with the card or with the FC switch, XP box or port...
Check the cable if there is light on both ends...

[Viktor Balogh]

You can also check with cstm if you see any problems with your FC cards:

# cstm
cstm> map all
cstm> sel dev ;info
cstm> il