HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
EVA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

SAN Disk Error Message in Solaris

 
andiappan
Occasional Visitor

SAN Disk Error Message in Solaris

Hi Team,

In the Solaris Server EMC VMAX is connect we geting randomaly error message in the /var/adm/message below is the error message,

Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.warning] WARNING: /pci@7c0/pci@0/pci@8/SUNW,emlxs@0/fp@0,0/ssd@w50000972081cdd65,4 (ssd23):
Sep 28 12:26:58 smpzon01 Error for Command: write(10) Error Level: Retryable
Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.notice] Requested Block: 49573696 Error Block: 49573696
Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.notice] Vendor: EMC Serial Number: 4795C000@
Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.notice] ASC: 0x3f (reported LUNs data has changed), ASCQ: 0xe, FRU: 0x0
Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.warning] WARNING: /pci@7c0/pci@0/pci@9/SUNW,emlxs@0/fp@0,0/ssd@w50000972081cdd59,4 (ssd22):
Sep 28 12:26:58 smpzon01 Error for Command: write(10) Error Level: Retryable
Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.notice] Requested Block: 144005776 Error Block: 144005776

Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Sep 28 12:26:58 smpzon01 scsi: [ID 107833 kern.notice] ASC: 0x3f (reported LUNs data has changed), ASCQ: 0xe, FRU: 0x0

Please respond.

Kind Regards
Vinod
1 REPLY
PP BIJU KRISHNAN
Trusted Contributor

Re: SAN Disk Error Message in Solaris

1. Are you seeing these messages when someone is changing things on the storage array. Activities like creation of LUNs etc can result in such messages. If yes then there is nothing to worry, this is very normal.

2. Logonto the switch where the host is connected and run the command
fabriclog -s

Check if the port connected to the host is appearing in the log. If yes fix the problem with the port.