Problems getting WWID recognized
Rafael David Tinoco
rafaeldtinoco at ubuntu.com
Wed Aug 26 17:11:25 UTC 2020
So, you see... your ID_SERIAL is coming from:
Vendor Specific Identifier Extension: 0x11ff54b6b7820049
from VPD page 0x83
> # /lib/udev/scsi_id --whitelisted --device=/dev/sdc
> 3600144f0f4e106e711ff54b6b7820049
> > > # 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
Try installing sg3-utils and check if rules from 55-scsi-sg3_id
satisfy your need. I'm aware that the rules file takes both VPDs into
consideration for the ID_SERIAL. Only thing left to try, if that does
not work, is to open a bug against systemd-udev:
$ dpkg -S /lib/udev/rules.d/60-persistent-storage.rules
udev: /lib/udev/rules.d/60-persistent-storage.rules
then let me know the bug #. I can't guarantee a fix but I'll make sure
to look into it for the next development cycle (as for this one we are
close to freeze date). Meanwhile you will be able to get a rules entry
that works for your case as a workaround.
Cheers o/
More information about the ubuntu-users
mailing list