Solaris[TM] reports ASC/ASCQ 0x29/0x00 when attached to a Sun StorEdge[TM] 6130

Asset ID:	1-72-1007892.1
Update Date:	2010-08-27
Keywords:

Solution Type Problem Resolution Sure

Solution 1007892.1 : Solaris[TM] reports ASC/ASCQ 0x29/0x00 when attached to a Sun StorEdge[TM] 6130

Related Items


Sun Storage 6130 Array

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays

PreviouslyPublishedAs
210895

Symptoms
Users see the following messages either logged to the console, or logged into /var/adm/messages:

Jan 18 12:45:22 myhost Error for Command: write(10) Error Level: Retryable
Jan 18 12:45:22 myhost scsi: [ID 107833 kern.notice] Requested Block: 38 Error Block: 38
Jan 18 12:45:22 myhost scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Jan 18 12:45:22 myhost scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Jan 18 12:45:22 myhost scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x1

Resolution
These messages when attached to the SE6130 represent a request, external to the array, by another object on the Fibre Channel SCSI bus. The message is reported as the outstanding read, write, or other operation (in this case write), was interrupted by this bus reset. The SE6130 is alerting the host driver that the operation must be retried, due to this circumstance.
The causes of this message are typically:

*Host power on or boot cycle
*Fibre Channel Segment failure

These messages are harmless as long as the IO request does not return an Error Level: Fatal. However if you suspect a problem, it is advisable to
review the hosts that have access to the 6130, and review whether either of the above conditions have been met.

Product
Sun StorageTek 6130 Array (SATA)
Sun StorageTek 6130 Array

Internal Comments
This was a result of escalation 1-14563148.

In this case, the customer was going through boot cycles on multiple hosts, causing IO requests to be interrupted on the other hosts. A review of the 6130

majorEventLog.txt file will reveal an entry or more as follows:

Date/Time: Wed Jan 18 12:43:46 EST 2006

 Sequence number: 23303

 Event type: 1202

 Event category:

 Error Priority: Informational

 Description: Fibre channel - TGT reset received Event specific codes: 0/0/0 Component type:

 Controller Component location: Controller in slot A

 Logged by: Controller in slot A

This Event Type denotes an external request for a SCSI Target Reset. As it happens, the messages were corrolated by the following entry in the /var/adm/messages, in Solaris 10:

Jan 18 12:45:23 v440-2 scsi_vhci: [ID 734749 kern.warning] WARNING: vhci_scsi_reset 0x1

 Jan 18 12:45:23 v440-2 scsi: [ID 243001 kern.warning] WARNING: /pci@1c,600000/SUNW,qlc@1/fp@0,0 (fcp4):

 Jan 18 12:45:23 v440-2 FCP: WWN 0x200600a0b819ddbb reset successfully

which shows that the scsi_vhci driver initiated the SCSI reset.

ASC, ASCQ, 6130, power on, bus reset, 0x29
Previously Published As
83700

Change History
Date: 2006-02-03
User Name: 25440
Action: Approved
Comment: Publishing.
Version: 3
Date: 2006-02-03
User Name: 25440
Action: Accept
Comment:
Version: 0
Date: 2006-02-03
User Name: 37842
Action: Approved
Comment: Made minor formatting changes.

Attachments

This solution has no attachment