iostat -Eni

Sorry for asking basics. What exactly is the situation if device ID is same in iostat -Eni. What we must do then? Is there any relation b/w iostat and cfgadm?

c1d0             Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: HITACHI HDS7225 Revision:  Device Id: id1,cmdk@AHITACHI_HDS7225SBSUN250G_0634NRBXHJ=VDS41DT4FRBXHJ
Size: 250.05GB <250054705152 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0

Device id will be different and will not be the same.
Relationship--> none.
You can just use them to check the controllers and targets for the specific disk device

Thanks a lot incredible. But I am not clear ( sorry ). If there is error in Hard Errors, then it is meant that the disk got errors. Also how to know abt disk errors in /var/adm/messages.

what this output is saying:iostat -Eni
c2t0d0 Soft Errors: 5 Hard Errors: 0 Transport Errors: 0
Vendor: VMware, Product: VMware Virtual S Revision: 1.0 Device Id: id1,sd@f23f1b5594aac949900064d1f0000
Size: 4.29GB <4294966784 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 5 Predictive Failure Analysis: 0
c2t1d0 Soft Errors: 5 Hard Errors: 0 Transport Errors: 0
Vendor: VMware, Product: VMware Virtual S Revision: 1.0 Device Id: id1,sd@f23f1b5594aac949900064d1f0000
Size: 4.29GB <4294966784 bytes>
as the device ID is same.

For disk errors, look for cxtxdx in the messages or the sd device equivalent..

# iostat -Ei
cmdk0     Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: HITACHI HDS7225 Revision:  Device Id: id1,cmdk@AHITACHI_HDS7225SBSUN250G_0634NRBXHJ=VDS41DT4FRBXHJ
Size: 250.05GB <250054705152 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0

Example, sd0 below, you can check against and compare the iostat -E and iostat -En command to find the correct disk.

Dec 4 12:45:06 az43backup1 scsi: Sense Key: Unit Attention Dec 4
12:45:06 az43backup1 scsi: ASC: 0x29 (scsi bus reset occurred),
ASCQ: 0x2, FRU: 0x0
Dec 4 12:45:06 az43backup1 scsi: WARNING: /pci@1c,600000/scsi@2 (glm0):
Dec 4 12:45:06 az43backup1 MSGREJ not expected Dec 4 12:45:06
az43backup1 scsi: WARNING: /pci@1c,600000/scsi@2 (glm0):
Dec 4 12:45:06 az43backup1 got SCSI bus reset Dec 4 12:45:09 az43backup1
scsi: WARNING: /pci@1c,600000/scsi@2 (glm0):
Dec 4 12:45:09 az43backup1 MSGREJ not expected Dec 4 12:45:09
az43backup1 scsi: WARNING: /pci@1c,600000/scsi@2 (glm0):
Dec 4 12:45:09 az43backup1 got SCSI bus reset Dec 4 12:45:09 az43backup1
scsi: WARNING: /pci@1c,600000/scsi@2/sd@0,0
(sd4):
Dec 4 12:45:09 az43backup1 auto request sense failed (reason=reset) Dec
4 12:45:12 az43backup1 scsi: WARNING: /pci@1c,600000/scsi@2/sd@1,0
(sd0):
Dec 4 12:45:12 az43backup1 SCSI transport failed: reason 'reset':
retrying command
Dec 4 12:45:12 az43backup1 scsi: WARNING: /pci@1c,600000/scsi@2/sd@2,0
(sd2):
Dec 4 12:45:12 az43backup1 SCSI transport failed: reason 'reset':
retrying command