vasek
Рекомендую проверить, точнее отключить autosuspend, для чего нужно загрузиться с параметром usbcore.autosuspend=-1
Перезагрузился с этой опцией.
Флешки пока работают. Ждем-с?
indeviral
Ну так сначала нужно взять одну гарантировано рабочую.
обе - проверены на других устройствах
indeviral
у вас с железом проблема.
По-моему вы правы, пробую перетыкать мышь в соседний USB-порт - она перестаёт работать - светодиод гаснет.
То есть у меня вырубаются USB-порты?

А, и да, я разные флешки пробывал втыкать.
vasek
А это что такое???
sdb 8:16 0 465.8G 0 disk
└─sdb1 8:17 0 465.8G 0 part /mnt/base
это доп.жёсткий диск
vasek
yaa
… смотри вывод lsblk - должна быть видна.
/quote]
неа, нету
>> lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 465.8G  0 disk
├─sda1   8:1    0  29.3G  0 part /
├─sda2   8:2    0  19.5G  0 part /home
├─sda3   8:3    0     2G  0 part
└─sda4   8:4    0   415G  0 part /mnt/win
sdb      8:16   0 465.8G  0 disk
└─sdb1   8:17   0 465.8G  0 part /mnt/base
sr0     11:0    1  1024M  0 rom
indeviral
udisk монтирует при обращении через фм.
udisksctl monitor
Покажите.
udisksctl monitor
Monitoring the udisks daemon. Press Ctrl+C to exit.
16:17:39.865: The udisks-daemon is running (name-owner :1.636).
втыкаю-вытыкаю - ничего нового не появляется
vasek

далее вставить флэшку … и смотреть логи (journalctl
там много букв, но вроде ругается на осутствие правил, которые мы грохнули по предыдущему совету
Apr 24 12:08:13 pampas kernel: usb 3-3: new high-speed USB device number 26 using xhci_hcd
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: Device is queued (SEQNUM=5676, ACTION=add)
Apr 24 12:08:13 pampas kernel: usb 3-3: New USB device found, idVendor=058f, idProduct=6387, bcdDevice= 1.00
Apr 24 12:08:13 pampas kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 24 12:08:13 pampas kernel: usb 3-3: Product: Mass Storage
Apr 24 12:08:13 pampas kernel: usb 3-3: Manufacturer: Generic
Apr 24 12:08:13 pampas kernel: usb 3-3: SerialNumber: 1805DCD4
Apr 24 12:08:13 pampas systemd-udevd[334862]: Validate module index
Apr 24 12:08:13 pampas systemd-udevd[334862]: Check if link configuration needs reloading.
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: Device ready for processing (SEQNUM=5676, ACTION=add)
Apr 24 12:08:13 pampas systemd-udevd[334862]: Successfully forked off 'n/a' as PID 345820.
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: Worker [345820] is forked for processing SEQNUM=5676.
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Processing device (SEQNUM=5676, ACTION=add)
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Failed to get watch handle, ignoring: No such file or directory
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/40-gphoto.rules:9 Importing properties from results of builtin command 'usb_id'
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3:1.0: Device is queued (SEQNUM=5677, ACTION=add)
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3:1.0: SEQNUM=5677 blocked by SEQNUM=5676
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: Device is queued (SEQNUM=5678, ACTION=bind)
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: SEQNUM=5678 blocked by SEQNUM=5676
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:13 Skipping builtin 'usb_id' in IMPORT key
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'hwdb --subsystem=usb'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: hwdb modalias key: "usb:v058Fp6387:Mass Storage"
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:15 Importing properties from results of builtin command 'hwdb 'usb:v058fp6387''
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: No entry found from hwdb.
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:15 Failed to run builtin 'hwdb 'usb:v058fp6387'': No data available
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:52 MODE 0664
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Setting permissions /dev/bus/usb/003/026, uid=0, gid=0, mode=0664
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Handling device node '/dev/bus/usb/003/026', devnum=c189:281
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: sd-device: Created db file '/run/udev/data/c189:281' for '/devices/pci0000:00/0000:00:14.0/usb3/3-3'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Failed to get watch handle, ignoring: No such file or directory
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Device processed (SEQNUM=5676, ACTION=add)
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: sd-device-monitor: Passed 755 byte to netlink monitor
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3:1.0: Device ready for processing (SEQNUM=5677, ACTION=add)
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3:1.0: sd-device-monitor: Passed 294 byte to netlink monitor
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: SEQNUM=5678 blocked by SEQNUM=5677
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: Processing device (SEQNUM=5677, ACTION=add)
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: /usr/lib/udev/rules.d/40-gphoto.rules:9 Importing properties from results of builtin command 'usb_id'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: Failed to access usb_interface: No such file or directory
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: /usr/lib/udev/rules.d/40-gphoto.rules:9 Failed to run builtin 'usb_id': No such file or directory
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: /usr/lib/udev/rules.d/50-udev-default.rules:14 Importing properties from results of builtin command 'hwdb --subsystem=usb'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: hwdb modalias key: "usb:v058Fp6387d0100dc00dsc00dp00ic08isc06ip50in00"
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: /usr/lib/udev/rules.d/80-drivers.rules:5 RUN 'kmod load '$env{MODALIAS}''
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: sd-device: Created db file '/run/udev/data/+usb:3-3:1.0' for '/devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: Running built-in command "kmod load 'usb:v058Fp6387d0100dc00dsc00dp00ic08isc06ip50in00'"
Apr 24 12:08:13 pampas systemd-udevd[345820]: Loading module: usb:v058Fp6387d0100dc00dsc00dp00ic08isc06ip50in00
Apr 24 12:08:13 pampas systemd-udevd[345820]: Failed to look up module alias 'usb:v058Fp6387d0100dc00dsc00dp00ic08isc06ip50in00': Function not implemented
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: Device processed (SEQNUM=5677, ACTION=add)
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3:1.0: sd-device-monitor: Passed 449 byte to netlink monitor
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: Device ready for processing (SEQNUM=5678, ACTION=bind)
Apr 24 12:08:13 pampas systemd-udevd[334862]: 3-3: sd-device-monitor: Passed 290 byte to netlink monitor
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Processing device (SEQNUM=5678, ACTION=bind)
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: Failed to get watch handle, ignoring: No such file or directory
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/40-gphoto.rules:9 Importing properties from results of builtin command 'usb_id'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:13 Skipping builtin 'usb_id' in IMPORT key
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'hwdb --subsystem=usb'
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: hwdb modalias key: "usb:v058Fp6387:Mass Storage"
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:15 Importing properties from results of builtin command 'hwdb 'usb:v058fp6387''
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: No entry found from hwdb.
Apr 24 12:08:13 pampas systemd-udevd[345820]: 3-3: /usr/lib/udev/rules.d/50-udev-default.rules:15 Failed to run builtin 'hwdb 'usb:v058fp6387'': No data available
vasek
Поддержу indeviral
indeviral
Установите udisks2
самое простое (почитай Wiki)
systemctl -a | grep -i udisk
udisks2.service                                                      loaded    active   running   Disk Manager

В части проблем с UDEV - для анализа желательно увеличить логирование - способов несколько, но в данном случае проще запустить команду
udevadm control -l debug
далее вставить флэшку … и смотреть логи (journalctl
( ~ )  >> sudo systemctl -a | grep -i udisk
  udisks2.service                                                                                                                             loaded    active   running   Disk Manager
( ~ )  >> 0.status udisks2
● udisks2.service - Disk Manager
     Loaded: loaded (/usr/lib/systemd/system/udisks2.service; disabled; vendor preset: disabled)
     Active: active (running) since Wed 2022-04-20 18:17:00 +05; 3 days ago
       Docs: man:udisks(8)
   Main PID: 1352 (udisksd)
      Tasks: 5 (limit: 6960)
     Memory: 4.2M
        CPU: 8.621s
     CGroup: /system.slice/udisks2.service
             └─1352 /usr/lib/udisks2/udisksd

Apr 20 18:16:52 pampas systemd[1]: Starting Disk Manager...
Apr 20 18:16:52 pampas udisksd[1352]: udisks daemon version 2.9.4 starting
Apr 20 18:17:00 pampas systemd[1]: Started Disk Manager.
Apr 20 18:17:02 pampas udisksd[1352]: Acquired the name org.freedesktop.UDisks2 on the system message bus
( ~ )  >> 0.restart udisks2
удав и глазом не моргнул
indeviral
значит надо разбираться что за сервис и что за параметры вы ему пытаетесь передать. И оно вообще когда-то работало?
покажите:
usb-mount@*.service
положили вы его наверно в /etc/systemd/system/ хотя не факт.
у меня нет такого
( ~ )  >> 0.status usb-mount@*.service
( ~ )  >> 0.list | grep mount
  proc-sys-fs-binfmt_misc.automount                                                           loaded active running   Arbitrary Executable File Formats File System Automount Point
  -.mount                                                                                     loaded active mounted   Root Mount
  dev-hugepages.mount                                                                         loaded active mounted   Huge Pages File System
  dev-mqueue.mount                                                                            loaded active mounted   POSIX Message Queue File System
  home.mount                                                                                  loaded active mounted   /home
  mnt-base.mount                                                                              loaded active mounted   /mnt/base
  mnt-win.mount                                                                               loaded active mounted   /mnt/win
  proc-sys-fs-binfmt_misc.mount                                                               loaded active mounted   Arbitrary Executable File Formats File System
  run-user-1000-gvfs.mount                                                                    loaded active mounted   /run/user/1000/gvfs
  run-user-1000.mount                                                                         loaded active mounted   /run/user/1000
  sys-fs-fuse-connections.mount                                                               loaded active mounted   FUSE Control File System
  sys-kernel-config.mount                                                                     loaded active mounted   Kernel Configuration File System
  sys-kernel-debug.mount                                                                      loaded active mounted   Kernel Debug File System
  sys-kernel-tracing.mount                                                                    loaded active mounted   Kernel Trace File System
  tmp.mount                                                                                   loaded active mounted   /tmp
  systemd-remount-fs.service                                                                  loaded active exited    Remount Root and Kernel File Systems
( ~ )  >> 0.list | grep usb
  sys-devices-pci0000:00-0000:00:1a.0-usb1-1\x2d1-1\x2d1.1-1\x2d1.1:1.0-bluetooth-hci0.device loaded active plugged   /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/bluetooth/hci0
( ~ )  >> 
indeviral
yaa
В смысле рестартануть systemd-udevd.service?
Не помогло.
А должно было?)
замените
ENV{SYSTEMD_WANTS}="usb-mount@%E{ID_FS_UUID}\x20%E{AUTOMOUNT_NAME}.service"
на
RUN+="/bin/systemctl start usb-mount@%E{ID_FS_UUID}\x20%E{AUTOMOUNT_NAME}.service"
По крайней мере это его точно запустит.

Увы. Поменял строчки. Теперь "99-automount.rules" име
ACTION=="add", SUBSYSTEM=="block", ENV{ID_FS_USAGE}=="filesystem", DRIVERS=="usb-storage", GOTO="automount_go"
ACTION=="remove", SUBSYSTEM=="block", ENV{ID_FS_USAGE}=="filesystem", DRIVERS=="usb-storage", RUN{program}+="/bin/rmdir /media/%E{AUTOMOUNT_NAME}"
GOTO="automount_end"

LABEL="automount_go"
ENV{AUTOMOUNT_NAME}="%E{ID_FS_UUID}"
ENV{ID_FS_LABEL}!="", ENV{AUTOMOUNT_NAME}="%E{ID_FS_LABEL}"
GROUP="storage", TAG+="systemd", RUN+="/bin/systemctl start usb-mount@%E{ID_FS_UUID}\x20%E{AUTOMOUNT_NAME}.service"

LABEL="automount_end"
но после рестарта "systemd-udevd" у удава так и не появились признаки совести