nepo Posted January 10, 2019 Posted January 10, 2019 hi orangepi 2e+ with ARMBIAN 5.65 stable Ubuntu 18.04.1 LTS 4.14.84-sunxi syslog I want to mount my external hard disks with cat /etc/udev/rules.d/91-intenso.rules KERNEL=="sd?1", SUBSYSTEMS=="usb", ATTRS{serial}=="31700000000000007023", SYMLINK+="Intenso", ACTION=="add", RUN+="/bin/mount /dev/Intenso /mnt/Intenso" Normally no problem, tested with Armbian_5.65_Orangepiplus2e_Ubuntu_xenial_default_3.4.113 and Workstation PC Linux 4.15.0-43-generic #46~16.04.1-Ubuntu. With my current version, I have a problem. The udev-rule is/seem ok Spoiler orangepi@orangepiplus2e:~$ sudo udevadm test /sys/class/block/sdb1 calling: test version 237 Load module index Parsed configuration file /lib/systemd/network/99-default.link Created link configuration context. Reading rules file: /etc/udev/rules.d/10-wifi-disable-powermanagement.rules Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules Reading rules file: /lib/udev/rules.d/50-firmware.rules Reading rules file: /lib/udev/rules.d/50-udev-default.rules Reading rules file: /lib/udev/rules.d/55-dm.rules Reading rules file: /lib/udev/rules.d/60-block.rules Reading rules file: /lib/udev/rules.d/60-bridge-network-interface.rules Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules Reading rules file: /lib/udev/rules.d/60-crda.rules Reading rules file: /lib/udev/rules.d/60-drm.rules Reading rules file: /lib/udev/rules.d/60-evdev.rules Reading rules file: /lib/udev/rules.d/60-gnupg2.rules Reading rules file: /lib/udev/rules.d/60-input-id.rules Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules Reading rules file: /lib/udev/rules.d/60-persistent-input.rules Reading rules file: /lib/udev/rules.d/60-persistent-storage-dm.rules Reading rules file: /lib/udev/rules.d/60-persistent-storage-tape.rules Reading rules file: /lib/udev/rules.d/60-persistent-storage.rules Reading rules file: /lib/udev/rules.d/60-persistent-v4l.rules Reading rules file: /lib/udev/rules.d/60-sensor.rules Reading rules file: /lib/udev/rules.d/60-serial.rules Reading rules file: /lib/udev/rules.d/60-sunxi-tools.rules Reading rules file: /lib/udev/rules.d/60-vlan-network-interface.rules Reading rules file: /lib/udev/rules.d/61-persistent-storage-android.rules Reading rules file: /lib/udev/rules.d/64-btrfs-dm.rules Reading rules file: /lib/udev/rules.d/64-btrfs.rules Reading rules file: /lib/udev/rules.d/70-joystick.rules Reading rules file: /lib/udev/rules.d/70-mouse.rules Reading rules file: /lib/udev/rules.d/70-power-switch.rules Reading rules file: /lib/udev/rules.d/70-touchpad.rules Reading rules file: /lib/udev/rules.d/70-uaccess.rules Reading rules file: /lib/udev/rules.d/71-axp-power-button.rules Reading rules file: /lib/udev/rules.d/71-power-switch-proliant.rules Reading rules file: /lib/udev/rules.d/71-seat.rules Reading rules file: /lib/udev/rules.d/73-seat-late.rules Reading rules file: /lib/udev/rules.d/73-special-net-names.rules Reading rules file: /lib/udev/rules.d/73-usb-net-by-mac.rules Reading rules file: /lib/udev/rules.d/75-net-description.rules Reading rules file: /lib/udev/rules.d/75-probe_mtd.rules Reading rules file: /lib/udev/rules.d/78-graphics-card.rules Reading rules file: /lib/udev/rules.d/78-sound-card.rules Reading rules file: /lib/udev/rules.d/80-debian-compat.rules Reading rules file: /lib/udev/rules.d/80-drivers.rules Reading rules file: /lib/udev/rules.d/80-ifupdown.rules Reading rules file: /lib/udev/rules.d/80-net-setup-link.rules Reading rules file: /lib/udev/rules.d/84-nm-drivers.rules Reading rules file: /lib/udev/rules.d/85-hdparm.rules Reading rules file: /lib/udev/rules.d/85-nm-unmanaged.rules Reading rules file: /lib/udev/rules.d/85-regulatory.rules Reading rules file: /lib/udev/rules.d/90-alsa-restore.rules Reading rules file: /lib/udev/rules.d/90-console-setup.rules Reading rules file: /etc/udev/rules.d/91-intenso.rules Reading rules file: /lib/udev/rules.d/95-dm-notify.rules Reading rules file: /lib/udev/rules.d/99-systemd.rules rules contain 24576 bytes tokens (2048 * 12 bytes), 14122 bytes strings 1935 strings (25186 bytes), 1249 de-duplicated (11751 bytes), 687 trie nodes used GROUP 6 /lib/udev/rules.d/50-udev-default.rules:56 LINK 'disk/by-id/ata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1' /lib/udev/rules.d/60-persistent-storage.rules:53 LINK 'disk/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1' /lib/udev/rules.d/60-persistent-storage.rules:76 IMPORT builtin 'blkid' /lib/udev/rules.d/60-persistent-storage.rules:90 probe /dev/sdb1 raid offset=0 LINK 'disk/by-uuid/21cbd081-a7b7-4fb3-a6a9-bf2e08aee280' /lib/udev/rules.d/60-persistent-storage.rules:93 LINK 'disk/by-label/Intenso_3TB' /lib/udev/rules.d/60-persistent-storage.rules:94 LINK 'disk/by-id/wwn-0x50000394aba82e19-part1' /lib/udev/rules.d/60-persistent-storage.rules:98 LINK 'Intenso' /etc/udev/rules.d/91-intenso.rules:1 RUN '/bin/mount /dev/Intenso /mnt/Intenso' /etc/udev/rules.d/91-intenso.rules:1 handling device node '/dev/sdb1', devnum=b8:17, mode=0660, uid=0, gid=6 preserve permissions /dev/sdb1, 060660, uid=0, gid=6 preserve already existing symlink '/dev/block/8:17' to '../sdb1' found 'b8:17' claiming '/run/udev/links/\x2fIntenso' creating link '/dev/Intenso' to '/dev/sdb1' preserve already existing symlink '/dev/Intenso' to 'sdb1' found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1' creating link '/dev/disk/by-id/ata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1' to '/dev/sdb1' preserve already existing symlink '/dev/disk/by-id/ata-TOSHIBA_MG03ACA300_33Q8K5YEF-part1' to '../../sdb1' found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fwwn-0x50000394aba82e19-part1' creating link '/dev/disk/by-id/wwn-0x50000394aba82e19-part1' to '/dev/sdb1' preserve already existing symlink '/dev/disk/by-id/wwn-0x50000394aba82e19-part1' to '../../sdb1' found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-label\x2fIntenso_3TB' creating link '/dev/disk/by-label/Intenso_3TB' to '/dev/sdb1' preserve already existing symlink '/dev/disk/by-label/Intenso_3TB' to '../../sdb1' found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-path\x2fplatform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1' creating link '/dev/disk/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1' to '/dev/sdb1' preserve already existing symlink '/dev/disk/by-path/platform-1c1c000.usb-usb-0:1.2:1.0-scsi-0:0:0:0-part1' to '../../sdb1' found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-uuid\x2f21cbd081-a7b7-4fb3-a6a9-bf2e08aee280' creating link '/dev/disk/by-uuid/21cbd081-a7b7-4fb3-a6a9-bf2e08aee280' to '/dev/sdb1' preserve already existing symlink '/dev/disk/by-uuid/21cbd081-a7b7-4fb3-a6a9-bf2e08aee280' to '../../sdb1' Unload module index Unloaded link configuration context. LINK 'Intenso' /etc/udev/rules.d/91-intenso.rules:1 RUN '/bin/mount /dev/Intenso /mnt/Intenso' /etc/udev/rules.d/91-intenso.rules:1 But orangepi@orangepiplus2e:~$ ls /mnt/Intenso/ orangepi@orangepiplus2e:~$ But If I mount manually orangepi@orangepiplus2e:~$ sudo mount /dev/Intenso /mnt/Intenso/ orangepi@orangepiplus2e:~$ ls /mnt/Intenso/ Filme FRITZ lost+found Musik recup_dir.86 Serien Where is my fault ? Bye nepo
nepo Posted January 11, 2019 Author Posted January 11, 2019 hi I have upgraded my SD-version Armbian_5.65_Orangepiplus2e_Ubuntu_xenial_default_3.4.11 to mainline aka 4.14.70 Armbian 5.60 et voila the system mount my harddisk. It seems not to be a problem with the mainline-kernel. So, Where are the differences ? xenial vs bionic or/and Armbian 5.60 vs Armbian_5.65 bye
nepo Posted January 15, 2019 Author Posted January 15, 2019 hi Unfortunately no solutions for my udev-problem, but a small workaround to implement my external hard disks. Mount with fstab and nofail option fstab Quote External devices External devices that are to be mounted when present but ignored if absent may require the nofail option. This prevents errors being reported at boot. For example: /etc/fstab /dev/sdg1 /media/backup jfs nofail,x-systemd.device-timeout=1 0 2 The nofail option is best combined with the x-systemd.device-timeout option. This is because the default device timeout is 90 seconds, so a disconnected external device with only nofail will make your boot take 90 seconds longer, unless you reconfigure the timeout as shown. Make sure not to set the timeout to 0, as this translates to infinite timeout. In my case UUID=xxxxxxxxxxxx /mnt/mountpoint ext4 nofail,x-systemd.device-timeout=1,rw,auto,users 0 0 To unmount correctly if unplugged I use an udev-rule orangepi@orangepiplus2e:~$ cat /etc/udev/rules.d/90-USB_festplatten.rules ACTION=="remove", KERNEL=="sd?1", ENV{ID_SERIAL_SHORT}=="33Q8K5YEF", RUN+="/bin/umount /mnt/mountpoint" bye
Recommended Posts