Device identification in case of same SN

votdev · 18. August 2020

The problem is that both devices attached to the JMicron based controller have the devicefile /dev/disk/by-id/usb-JMicron_Generic_0123456789ABCDEF-0:0 which is falsy, because a devicefile MUST be unique. Because OMV uses the /dev/disk/by-id devicefiles by default (because this is the only predictable one, /dev/sdX can change depending on timing issues during bootup, ...) the disks page only shows one.

OMV has already included UDEV rules to workaround this, but it seems not to work. Sadly i do not have such a crappy USB controller, so i can not test it. Because of that someone in the community must get it working and create a pull request on Github including the fixes or open an issue describing exactly what to fix.

You can find the UDEV rules here at /etc/udev/rules.d/99-openmediavault-dev-disk-by-id.rules or https://github.com/openmediava…ault-dev-disk-by-id.rules

If the rules did not work it might be because of a missing full path to the serial_id command. It is located in /usr/lib/udev/serial_id.

Rerax · 15. November 2020

Here's my best try in trying to get familiar with UDEV and my HornetTek HT-RAB237. I just copied pasted a previous one from https://github.com/openmediava…ault-dev-disk-by-id.rules and replaced the {ID_VENDOR_ID & ID_MODEL_ID} and it looks like it took out the random from my previous post. Please let me know if this helps and if there is something else I should test or add.

Code

This is the output when I ran udevadm info --query=all --name=/dev/sdX

P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
N: sda1
L: 0
S: disk/by-uuid/ad0eff7e-b1b7-485a-831f-dd27d84c7065
S: disk/by-id/usb-SanDisk_SDSSDH3_1T02_RANDOM__622374CDBF83-0:0-part1
S: disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0-part1
S: disk/by-partuuid/4b019603-fb86-47f5-a894-9b3e3ac951ff
S: disk/by-label/1TB
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
E: DEVNAME=/dev/sda1
E: DEVTYPE=partition
E: PARTN=1
E: MAJOR=8
E: MINOR=1
E: SUBSYSTEM=block
E: USEC_INITIALIZED=5674561
E: ID_VENDOR=SanDisk
E: ID_VENDOR_ENC=SanDisk\x20
E: ID_VENDOR_ID=152d
E: ID_MODEL=SDSSDH3_1T02
E: ID_MODEL_ENC=SDSSDH3\x201T02\x20\x20\x20\x20
E: ID_MODEL_ID=0561
E: ID_REVISION=0108
E: ID_SERIAL=SanDisk_SDSSDH3_1T02_RANDOM__622374CDBF83-0:0
E: ID_SERIAL_SHORT=RANDOM__622374CDBF83
E: ID_TYPE=disk
E: ID_INSTANCE=0:0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080650:080662:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=uas
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_2_1_0-scsi-0_0_0_0
E: ID_PART_TABLE_UUID=39c29a25-ee97-4738-a043-70457295818c
E: ID_PART_TABLE_TYPE=gpt
E: ID_FS_LABEL=1TB
E: ID_FS_LABEL_ENC=1TB
E: ID_FS_UUID=ad0eff7e-b1b7-485a-831f-dd27d84c7065
E: ID_FS_UUID_ENC=ad0eff7e-b1b7-485a-831f-dd27d84c7065
E: ID_FS_VERSION=1.0
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_UUID=4b019603-fb86-47f5-a894-9b3e3ac951ff
E: ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E: ID_PART_ENTRY_NUMBER=1
E: ID_PART_ENTRY_OFFSET=2048
E: ID_PART_ENTRY_SIZE=2000407183
E: ID_PART_ENTRY_DISK=8:0
E: DEVLINKS=/dev/disk/by-uuid/ad0eff7e-b1b7-485a-831f-dd27d84c7065 /dev/disk/by-id/usb-SanDisk_SDSSDH3_1T02_RANDOM__622374CDBF83-0:0-part1 /dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0-part1 /dev/disk/by-partuuid/4b019603-fb86-47f5-a894-9b3e3ac951ff /dev/disk/by-label/1TB
E: TAGS=:systemd:

------------------------------------------
This is what I pasted on /etc/udev/rules.d/99-openmediavault-dev-disk-by-id.rules

# JMS551 - Sharkoon SATA QuickPort Duo
# http://www.hornettek.com/hdd-enclosure/dual-bay/hornettek-usb-3-0-dual-2-5-hdd-sdd-enclosure-w-raid-ht-rab237.html
ACTION=="add", KERNEL=="sd*", SUBSYSTEM=="block", \
  ENV{ID_VENDOR_ID}=="152d", ENV{ID_MODEL_ID}=="0561", \
  PROGRAM="/usr/lib/udev/serial_id %N", \
  ENV{ID_SERIAL}="$env{ID_VENDOR}_$env{ID_MODEL}_$env{ID_SERIAL_SHORT}-$env{ID_INSTANCE}", \
  ENV{ID_SERIAL_SHORT}="%c", \
  ENV{ID_SERIAL}="$env{ID_VENDOR}_$env{ID_MODEL}_%c-$env{ID_INSTANCE}", \
  SYMLINK="disk/by-path/$env{ID_PATH}", \
  SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"

Alles anzeigen

votdev · 16. November 2020

Zitat von Rerax

Here's my best try in trying to get familiar with UDEV and my HornetTek HT-RAB237. I just copied pasted a previous one from https://github.com/openmediava…ault-dev-disk-by-id.rules and replaced the {ID_VENDOR_ID & ID_MODEL_ID} and it looks like it took out the random from my previous post. Please let me know if this helps and if there is something else I should test or add.

Code

This is the output when I ran udevadm info --query=all --name=/dev/sdX

P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
N: sda1
L: 0
S: disk/by-uuid/ad0eff7e-b1b7-485a-831f-dd27d84c7065
S: disk/by-id/usb-SanDisk_SDSSDH3_1T02_RANDOM__622374CDBF83-0:0-part1
S: disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0-part1
S: disk/by-partuuid/4b019603-fb86-47f5-a894-9b3e3ac951ff
S: disk/by-label/1TB
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
E: DEVNAME=/dev/sda1
E: DEVTYPE=partition
E: PARTN=1
E: MAJOR=8
E: MINOR=1
E: SUBSYSTEM=block
E: USEC_INITIALIZED=5674561
E: ID_VENDOR=SanDisk
E: ID_VENDOR_ENC=SanDisk\x20
E: ID_VENDOR_ID=152d
E: ID_MODEL=SDSSDH3_1T02
E: ID_MODEL_ENC=SDSSDH3\x201T02\x20\x20\x20\x20
E: ID_MODEL_ID=0561
E: ID_REVISION=0108
E: ID_SERIAL=SanDisk_SDSSDH3_1T02_RANDOM__622374CDBF83-0:0
E: ID_SERIAL_SHORT=RANDOM__622374CDBF83
E: ID_TYPE=disk
E: ID_INSTANCE=0:0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080650:080662:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=uas
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_2_1_0-scsi-0_0_0_0
E: ID_PART_TABLE_UUID=39c29a25-ee97-4738-a043-70457295818c
E: ID_PART_TABLE_TYPE=gpt
E: ID_FS_LABEL=1TB
E: ID_FS_LABEL_ENC=1TB
E: ID_FS_UUID=ad0eff7e-b1b7-485a-831f-dd27d84c7065
E: ID_FS_UUID_ENC=ad0eff7e-b1b7-485a-831f-dd27d84c7065
E: ID_FS_VERSION=1.0
E: ID_FS_TYPE=ext4
E: ID_FS_USAGE=filesystem
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_UUID=4b019603-fb86-47f5-a894-9b3e3ac951ff
E: ID_PART_ENTRY_TYPE=0fc63daf-8483-4772-8e79-3d69d8477de4
E: ID_PART_ENTRY_NUMBER=1
E: ID_PART_ENTRY_OFFSET=2048
E: ID_PART_ENTRY_SIZE=2000407183
E: ID_PART_ENTRY_DISK=8:0
E: DEVLINKS=/dev/disk/by-uuid/ad0eff7e-b1b7-485a-831f-dd27d84c7065 /dev/disk/by-id/usb-SanDisk_SDSSDH3_1T02_RANDOM__622374CDBF83-0:0-part1 /dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:0-part1 /dev/disk/by-partuuid/4b019603-fb86-47f5-a894-9b3e3ac951ff /dev/disk/by-label/1TB
E: TAGS=:systemd:

------------------------------------------
This is what I pasted on /etc/udev/rules.d/99-openmediavault-dev-disk-by-id.rules

# JMS551 - Sharkoon SATA QuickPort Duo
# http://www.hornettek.com/hdd-enclosure/dual-bay/hornettek-usb-3-0-dual-2-5-hdd-sdd-enclosure-w-raid-ht-rab237.html
ACTION=="add", KERNEL=="sd*", SUBSYSTEM=="block", \
  ENV{ID_VENDOR_ID}=="152d", ENV{ID_MODEL_ID}=="0561", \
  PROGRAM="/usr/lib/udev/serial_id %N", \
  ENV{ID_SERIAL}="$env{ID_VENDOR}_$env{ID_MODEL}_$env{ID_SERIAL_SHORT}-$env{ID_INSTANCE}", \
  ENV{ID_SERIAL_SHORT}="%c", \
  ENV{ID_SERIAL}="$env{ID_VENDOR}_$env{ID_MODEL}_%c-$env{ID_INSTANCE}", \
  SYMLINK="disk/by-path/$env{ID_PATH}", \
  SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"

Alles anzeigen

Thanks for contributing your findings. I've added them in openmediavault 5.5.17, see https://github.com/openmediava…b981958e875bd7d1f8a8ac421

Rerax · 21. November 2020

Zitat von votdev

Thanks for contributing your findings. I've added them in openmediavault 5.5.17, see https://github.com/openmediava…b981958e875bd7d1f8a8ac421

Just tested on the latest OMV update and it looks like it works. Thank you for updating.

Also, I don't think I would be using the S.M.A.R.T. feature as often, but do these enclosures only work with one temp/status showing?

I've tried with couple disks on sda, and it looks like it's only working for sdb.

Backslash Backslash · 9. Januar 2024

I am having the same issue with Sabrent USB-SATA adapters giving the same Serial Numbers. Noting the UDEV database work a few years ago, is there a "fix for Dummies" I can apply?

My common SNs are WY22VE1Y & WD-WXK1A10X4320.

I do use /dev/disk/by-UUID, however, it would make life easier to be able to trust the SNs.

votdev · 9. Januar 2024

Zitat von Backslash Backslash

I am having the same issue with Sabrent USB-SATA adapters giving the same Serial Numbers. Noting the UDEV database work a few years ago, is there a "fix for Dummies" I can apply?

My common SNs are WY22VE1Y & WD-WXK1A10X4320.

I do use /dev/disk/by-UUID, however, it would make life easier to be able to trust the SNs.

Please check these links and open a feature request with all the required info. Please read the links carefully to find out what data is required to create an UDEV rule that is fixing your issue.

Jetzt mitmachen!