No, that first list IS in order, this is how it should be counting from left to right (hence the index numbers). I've showed the by-id paths because they seem to have no relation to the SCSI IDs.
And no, perish the thought, they're all connected to a scsi controller on pci-express.
So to reiterate, I'd like to rename these drives based on the scsi port they're connected to
Unfortunately not for me, in fact they're quite not-in-order
0 [3:0:0:0] /dev/sdb ata-Samsung_SSD_860_EVO_250GB_S3YJNF0M717186E
1 [2:0:0:0] /dev/sda ata-ST4000VN008-2DR166_ZDH60ERC
2 [7:0:0:0] /dev/sdd ata-ST4000VN008-2DR166_ZDH5T2L1
3 [6:0:0:0] /dev/sdc ata-ST4000VN008-2DR166_ZGY3DRBN
lrwxrwxrwx 1 root root 9 Oct 31 18:24 pci-0000:01:00.0-ata-3 -> ../../sda
lrwxrwxrwx 1 root root 9 Oct 31 18:24 pci-0000:01:00.0-ata-4 -> ../../sdb
lrwxrwxrwx 1 root root 9 Oct 31 18:24 pci-0000:02:00.0-ata-3 -> ../../sdc
lrwxrwxrwx 1 root root 9 Oct 31 18:24 pci-0000:02:00.0-ata-4 -> ../../sdd
I'm thinking on how to get udev to do what I do.. The attributes that I want are in the parent device of the actual disk, not in the disk itself..
vault# udevadm info -a /dev/sda
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sda':
KERNEL=="sda"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="16"
ATTR{removable}=="1"
ATTR{events_async}==""
ATTR{inflight}==" 0 0"
ATTR{ro}=="0"
ATTR{alignment_offset}=="0"
ATTR{stat}==" 821 292 327584 7238 152 61 1494 3130 0 3196 8768 0 0 0 0"
ATTR{ext_range}=="256"
ATTR{hidden}=="0"
ATTR{events_poll_msecs}=="-1"
ATTR{size}=="7814037168"
ATTR{capability}=="51"
ATTR{discard_alignment}=="0"
ATTR{events}=="media_change"
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ata3/host2/target2:0:0/2:0:0:0':
KERNELS=="2:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{type}=="0"
ATTRS{queue_type}=="simple"
ATTRS{vpd_pg83}==""
ATTRS{evt_mode_parameter_change_reported}=="0"
ATTRS{eh_timeout}=="10"
ATTRS{model}=="ST4000VN008-2DR1"
ATTRS{evt_media_change}=="0"
ATTRS{evt_inquiry_change_reported}=="0"
ATTRS{evt_capacity_change_reported}=="0"
ATTRS{evt_soft_threshold_reached}=="0"
ATTRS{dh_state}=="detached"
ATTRS{unload_heads}=="0"
ATTRS{blacklist}==""
ATTRS{device_busy}=="0"
ATTRS{iorequest_cnt}=="0xcb5"
ATTRS{vpd_pg80}==""
ATTRS{device_blocked}=="0"
ATTRS{state}=="running"
ATTRS{queue_depth}=="32"
ATTRS{rev}=="SC60"
ATTRS{evt_lun_change_reported}=="0"
ATTRS{wwid}=="t10.ATA ST4000VN008-2DR166 ZDH60ERC"
ATTRS{ncq_prio_enable}=="0"
ATTRS{queue_ramp_up_period}=="120000"
ATTRS{ioerr_cnt}=="0x205"
ATTRS{inquiry}==""
ATTRS{iodone_cnt}=="0xc9c"
ATTRS{timeout}=="30"
ATTRS{iocounterbits}=="32"
ATTRS{scsi_level}=="6"
ATTRS{vendor}=="ATA "
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ata3/host2/target2:0:0':
KERNELS=="target2:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ata3/host2':
KERNELS=="host2"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ata3':
KERNELS=="ata3"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1c.0/0000:01:00.0':
KERNELS=="0000:01:00.0"
SUBSYSTEMS=="pci"
DRIVERS=="ahci"
ATTRS{revision}=="0x11"
ATTRS{broken_parity_status}=="0"
ATTRS{resource3}==""
ATTRS{subsystem_device}=="0x9215"
ATTRS{current_link_speed}=="5 GT/s"
ATTRS{max_link_speed}=="5 GT/s"
ATTRS{msi_bus}=="1"
ATTRS{enable}=="1"
ATTRS{resource1}==""
ATTRS{local_cpulist}=="0-3"
ATTRS{local_cpus}=="f"
ATTRS{max_link_width}=="1"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{ari_enabled}=="0"
ATTRS{current_link_width}=="1"
ATTRS{numa_node}=="-1"
ATTRS{d3cold_allowed}=="1"
ATTRS{driver_override}=="(null)"
ATTRS{subsystem_vendor}=="0x1b4b"
ATTRS{device}=="0x9215"
ATTRS{vendor}=="0x1b4b"
ATTRS{class}=="0x010601"
ATTRS{irq}=="97"
ATTRS{dma_mask_bits}=="64"
looking at parent device '/devices/pci0000:00/0000:00:1c.0':
KERNELS=="0000:00:1c.0"
SUBSYSTEMS=="pci"
DRIVERS=="pcieport"
ATTRS{local_cpulist}=="0-3"
ATTRS{max_link_speed}=="5 GT/s"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x0f48"
ATTRS{broken_parity_status}=="0"
ATTRS{aer_rootport_total_err_nonfatal}=="0"
ATTRS{revision}=="0x0e"
ATTRS{dma_mask_bits}=="32"
ATTRS{secondary_bus_number}=="1"
ATTRS{current_link_speed}=="5 GT/s"
ATTRS{irq}=="87"
ATTRS{enable}=="1"
ATTRS{max_link_width}=="1"
ATTRS{msi_bus}=="1"
ATTRS{subsystem_vendor}=="0x8086"
ATTRS{aer_rootport_total_err_fatal}=="0"
ATTRS{ari_enabled}=="0"
ATTRS{local_cpus}=="f"
ATTRS{subordinate_bus_number}=="1"
ATTRS{d3cold_allowed}=="1"
ATTRS{numa_node}=="-1"
ATTRS{current_link_width}=="1"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{device}=="0x0f48"
ATTRS{class}=="0x060400"
ATTRS{driver_override}=="(null)"
ATTRS{aer_rootport_total_err_cor}=="0"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""So for some time now I've been happily using OMV inside a QNAP TS-451+, and it's working much better than the stuff qnap gives. However, there's only thing I'm missing from this arrangement. If a drive fails, I have to basically guess which bay is the one that houses it. Is there a good way to make hdd devices have stable device names? I'm thinking something on the order of a udev rule, so I could assign disks to paths, and when it fails, i can see that instead of /dev/sda failing it's something like /dev/bay0 or something of the sort
systemd already does something similar to ethernet ports.
If anyone already has something similar done, I'd love to hear about it