Problems getting WWID recognized

[Albert Chin]

On Wed, Aug 26, 2020 at 12:59:46PM -0300, Rafael David Tinoco wrote:
> >
> > On Wed, Aug 26, 2020 at 09:53:09AM -0300, Rafael David Tinoco wrote:
> > > Are you able to inquiry VPD for the LUNs coming from the open solaris
> > > storage server ?
> >
> > Nope. Info below. So what happens if "udevadm info -q all
> > --path=/sys/block/sdc" shows ID_SERIAL but "sg_vpd --page=sn
> > /dev/sdc" does not?
> 
> The ID_SERIAL is filled by the udev rules file. You have to check
> which rule is the one creating (or making it to skip the creation
> of) the ID_SERIAL. So, if udevadm has the ID_SERIAL, but it is not
> coming from the SCSI VPD page, it means that the serial was defined
> by some other script/wrapper - then inquiring SCSI VPD pages.
> 
> From 60-persistent-storage.rules we have:
> 
> scsi_id --export --whitelisted -d ...
> 
> scsi_id comes from /lib/udev/scsi_id and it also gets information from
> VPD pages 0x80, 0x83.

# /lib/udev/scsi_id --whitelisted --device=/dev/sdc
3600144f0f4e106e711ff54b6b7820049

> If you install sg3-utils-udev package it will create a file called:
> 
> /lib/udev/rules.d/55-scsi-sg3_id.rules
> 
> that will try to use VPD 0x80 and 0x83 pages for the ID_SERIAL
> attribute, but using the sg_inq tool from sg3-tools package.
> 
> To answer your question:
> 
> If udevadm info shows ID_SERIAL but sg_inq tool does not, it means
> that you have an udev rule creating the ID_SERIAL for you. In that
> case, you should make changes to udev rules, to make sure they use
> correct VPD pages for ID_SERIAL.

Ok, let me do some digging.

> Also, take a look at your storage server, making sure that 0x80 and
> 0x83 pages are available (SBC-4 standards define *at least* VPD 0x80
> as mandatory). Check my comment below...
> 
> > # sg_inq -e /dev/sdc
> > VPD INQUIRY, page code=0x00:
> >    Supported VPD pages:
> >      0x0        Supported VPD pages
> >      0x80       Unit serial number
> >      0x83       Device identification
> >      0x86       Extended INQUIRY data
> >      0xb0       Block limits (sbc2)
> >      0xb2       Logical block provisioning (sbc3)
> >
> > # sg_inq -e --page=0x80 /dev/sdc
> > VPD INQUIRY: Unit serial number page
> >   Unit serial number:
> 
> Could you try 0x80, 0x83, 0x86 as well ? Nothing there ? If there is
> SERIAL coming from your storage server, it is not behaving like
> described by SCSI SBC-4 standards.. but you could create a wrapper
> to be executed by udev (check bcache-tools package udev rules) that
> could get something else from your storage server and define it as
> ID_SERIAL.

# sg_inq -e --page=0x83 /dev/sdc
VPD INQUIRY: Device Identification page
  Designation descriptor number 1, descriptor length: 20
    designator_type: NAA,  code_set: Binary
    associated with the Addressed logical unit
      NAA 6, IEEE Company_id: 0x144f
      Vendor Specific Identifier: 0xf4e106e7
      Vendor Specific Identifier Extension: 0x11ff54b6b7820049
      [0x600144f0f4e106e711ff54b6b7820049]
  Designation descriptor number 2, descriptor length: 71
    transport: Internet SCSI (iSCSI)
    designator_type: vendor specific [0x0],  code_set: ASCII
    associated with the Target port
      vendor specific: iqn.2010-09.org.openindiana:02:4a7b9f0f-4777-631e-e19a-fb0b94963439
  Designation descriptor number 3, descriptor length: 8
    designator_type: Target port group,  code_set: Binary
    associated with the Target port
      Target port group: 0x0
  Designation descriptor number 4, descriptor length: 8
    designator_type: Relative target port,  code_set: Binary
    associated with the Target port
      Relative target port: 0x2

# sg_inq -e --page=0x86 /dev/sdc
VPD INQUIRY: extended INQUIRY data page
  ACTIVATE_MICROCODE=0 SPT=0 GRD_CHK=0 APP_CHK=0 REF_CHK=0
  UASK_SUP=0 GROUP_SUP=0 PRIOR_SUP=0 HEADSUP=0 ORDSUP=0 SIMPSUP=1
  WU_SUP=0 [CRD_SUP=0] NV_SUP=0 V_SUP=0
  NO_PI_CHK=0 P_I_I_SUP=0 LUICLR=0
  LU_COLL_TYPE=0 R_SUP=0 RTD_SUP=0 HSSRELEF=0 [CBCS=0]
  Multi I_T nexus microcode download=0
  Extended self-test completion minutes=0
  POA_SUP=0 HRA_SUP=0 VSA_SUP=0 DMS_VALID=0
  Maximum supported sense data length=0
  IBS=0 IAS=0 SAC=0 NRD1=0 NRD0=0
  Maximum inquiry change logs=0
  Maximum mode page change logs=0
  DM_MD_4=0 DM_MD_5=0 DM_MD_6=0 DM_MD_7=0
  DM_MD_D=0 DM_MD_E=0 DM_MD_F=0

-- 
albert chin (china at thewrittenword.com)