Pillar Axiom: Solaris errors "inquiry data has changed", "Corrupt label; wrong magic number"

Asset ID:	1-72-1571891.1
Update Date:	2014-12-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1571891.1 : Pillar Axiom: Solaris errors "inquiry data has changed", "Corrupt label; wrong magic number"

Applies to:

Pillar Axiom 500 Storage System - Version Not Applicable and later
Pillar Axiom 600 Storage System - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

Customer can see this type of message in the host logs:

Jul 19 22:21:36 lxxxxxx003 genunix: [ID 936769 kern.info] ssd19 is /pci@500/pci@2/pci@0/pci@3/pci@0/pci@3/SUNW,emlxs@0,1/fp@0,0/ssd@w21000024ff4d3b21,1
Jul 19 22:21:36 lxxxxxx003 scsi: [ID 107833 kern.warning] WARNING: /pci@500/pci@2/pci@0/pci@3/pci@0/pci@3/SUNW,emlxs@0,1/fp@0,0/ssd@w21000024ff4d3b21,1 (ssd19):
Jul 19 22:21:36 lxxxxxx003 Corrupt label; wrong magic number

Jul 19 22:08:06 lxxxxxx002 scsi: [ID 107833 kern.notice] Requested Block: 22888872 Error Block: 22888872
Jul 19 22:08:06 lxxxxxx002 scsi: [ID 107833 kern.notice] Vendor: Pillar Serial Number:
Jul 19 22:08:06 lxxxxxx002 scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
Jul 19 22:08:06 lxxxxxx002 scsi: [ID 107833 kern.notice] ASC: 0x3f (inquiry data has changed), ASCQ: 0x3, FRU: 0x0
Jul 19 22:08:06 lxxxxxx002 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g000b080005004569 (ssd30):
Jul 19 22:08:06 lxxxxxx002 Error for Command: write(10) Error Level: Retryable

Changes

In our case, the customer was unaware of LUNs creation and mapping taking care place on his servers.

Cause

To match a Solaris host LUN with a Pillar LUN, use the LUN ID behind the ssd@ string in the messages: /scsi_vhci/ssd@g000b080005004569 (ssd30).

The example bellow shows where to find a LUN ID in the Axiom graphical interface:

LUN id in the GUI

LUNs have been created and mapped on to te solaris server (date to match, the Axiom uses UTC to log while the Solaris is using local time that is GMT +7):

2013-07-19T15:08:51.308 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-05/10000090FA1AE5BB
2013-07-19T15:08:51.307 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-05/10000090FA19902C
2013-07-19T15:08:47.921 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-04/10000090FA19902C
2013-07-19T15:08:47.920 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-04/10000090FA1AE5BB
2013-07-19T15:08:44.455 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-03/10000090FA19902C
2013-07-19T15:08:44.454 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-03/10000090FA1AE5BB
2013-07-19T15:08:40.938 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-02/10000090FA1AE5BB
2013-07-19T15:08:40.938 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-02/10000090FA19902C
2013-07-19T15:08:37.573 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-01/10000090FA1AE5BB
2013-07-19T15:08:37.572 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/fra-01/10000090FA19902C
2013-07-19T15:08:34.110 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-04/10000090FA19902C
2013-07-19T15:08:34.109 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-04/10000090FA1AE5BB
2013-07-19T15:08:30.789 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-03/10000090FA1AE5BB
2013-07-19T15:08:30.788 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-03/10000090FA19902C
2013-07-19T15:08:27.409 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-02/10000090FA1AE5BB
2013-07-19T15:08:27.409 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-02/10000090FA19902C
2013-07-19T15:08:23.984 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-01/10000090FA19902C
2013-07-19T15:08:23.983 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx003/db-01/10000090FA1AE5BB
2013-07-19T15:08:20.668 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-07/10000090FA199170
2013-07-19T15:08:20.667 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-07/10000090FA1993A1
2013-07-19T15:08:17.345 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-06/10000090FA1993A1
2013-07-19T15:08:17.344 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-06/10000090FA199170
2013-07-19T15:08:13.925 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-05/10000090FA1993A1
2013-07-19T15:08:13.925 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-05/10000090FA199170
2013-07-19T15:08:10.499 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-04/10000090FA1993A1
2013-07-19T15:08:10.498 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-04/10000090FA199170
2013-07-19T15:08:06.995 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-03/10000090FA199170
2013-07-19T15:08:06.994 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-03/10000090FA1993A1
2013-07-19T15:08:02.444 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-02/10000090FA199170
2013-07-19T15:08:02.443 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-02/10000090FA1993A1
2013-07-19T15:07:58.151 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-01/10000090FA199170
2013-07-19T15:07:58.151 INFORMATIONAL LUN_MAPPING_HOST_CREATED /lxxxxxx002/zone-01/10000090FA1993A1

--------------------------------------------------------------------------------------------------------

The message "Corrupt label; wrong magic number" means that the disks have not yet been labeled by Solaris. Use the format utility to resolve.

The message ASC: 0x3f (inquiry data has changed), ASCQ: 0x3, FRU: 0x0 means that the disk status has changed, in this case freshly mapped and needs no further action.

Solution

No action is necessary. These messages are informational only and arise when creating a new mapping.

Attachments

This solution has no attachment