Various commands used to figure out how to identify disk to make udev rules for launching scripts etc.
udevadm info --name=/dev/ttyUSB0 --attribute-walk
looking at device '/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb7/7-2/7-2:1.0/ttyUSB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
looking at parent device '/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb7/7-2':
KERNELS=="7-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{idProduct}=="6001"
ATTRS{idVendor}=="0403"
ATTRS{serial}=="ftE2CX8D"
ATTRS{product}=="USB Serial Converter"
KERNEL=="ttyUSB[0-9]*", SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="ftE2CX8D", SYMLINK+="crs309", OWNER="vociferous"
# udevadm control --reload
# udevadm trigger
udevadm info -a -n /dev/sdb | less
udevadm info -a -n /dev/sdb | grep serial
udevadm monitor --environment --udev
udevadm info /dev/sdd1 #ENV VARS
udevadm control --reload
udevadm test $(udevadm info --query=path --name=/dev/sdd) 2>&1
udevadm trigger# /etc/udev/rules.d/70-backup_kserv.rules
ACTION=="add", SUBSYSTEM=="block", KERNEL=="sd[a-z]?", ENV{ID_SERIAL_SHORT}=="ZHZ2BN6T", SYMLINK+="iron14tb", RUN+="/usr/bin/systemctl start backup_kserv"
# /etc/udev/rules.d/69-backup_media.rules
ACTION=="add", SUBSYSTEM=="block", KERNEL=="sd[a-z]?", ENV{ID_SERIAL_SHORT}=="5000c500da01855f", SYMLINK+="mediabackup", RUN+="/usr/bin/systemctl start backup_media"Last modified: Tue Jun 24 14:55:56 2025