Per replicare un po' la stessa condizione descritta procedo così:
In pc acceso fermo sulla schermata di login di Debian, inserisco una chiavetta usb e mi collego in ssh.
Il disco non risulta in mount automatico.
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1,5G 0 1,5G 0% /dev
tmpfs 299M 1,4M 298M 1% /run
/dev/sda5 46G 25G 19G 58% /
tmpfs 1,5G 0 1,5G 0% /dev/shm
tmpfs 5,0M 8,0K 5,0M 1% /run/lock
tmpfs 299M 88K 299M 1% /run/user/106
tmpfs 299M 84K 299M 1% /run/user/1000
pur essendo visto come dispositivo usb e pur essendo gestibile da fdisk:
Bus 003 Device 003: ID 04f2:b159 Chicony Electronics Co., Ltd CNF8243 Webcam
Bus 003 Device 002: ID 13fe:3d23 Phison Electronics Corp. USB DISK Pro
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
bpxroot@debianq:~$ sudo fdisk -l | grep ^Disk\ /dev/sd
[sudo] password for bpxroot:
Disk /dev/sda: 298,09 GiB, 320072933376 bytes, 625142448 sectors
Disk /dev/sdb: 7,46 GiB, 8006926336 bytes, 15638528 sectors
inoltre è anche visibile in /dev/disk/by-uuid
bpxroot@debianq:~$ ls -la /dev/disk/by-uuid/
total 0
drwxr-xr-x 2 root root 200 ago 24 2023 .
drwxr-xr-x 7 root root 140 ago 24 2023 ..
lrwxrwxrwx 1 root root 10 ago 24 2023 0177e8bc-8764-49b1-816e-88eef7b24a8b -> ../../sda7
lrwxrwxrwx 1 root root 10 ago 24 2023 36E0-356D -> ../../sdb1
lrwxrwxrwx 1 root root 10 ago 24 2023 49386f18-8d88-4c37-8218-00e332596116 -> ../../sda4
lrwxrwxrwx 1 root root 10 ago 24 2023 6EFF820F3CDADEE2 -> ../../sda8
lrwxrwxrwx 1 root root 10 ago 24 2023 84A0AA21A0AA1A26 -> ../../sda2
lrwxrwxrwx 1 root root 10 ago 24 2023 9ec87039-6e11-4ab1-bc36-1d97bf8dddc7 -> ../../sda5
lrwxrwxrwx 1 root root 10 ago 24 2023 aa012360-3155-4154-9671-e72112392d5d -> ../../sda6
lrwxrwxrwx 1 root root 10 ago 24 2023 AE42C65642C622C7 -> ../../sda1
però volgio partire da una condizione più svantaggiata e faccio un eject in questo modo non viene più visto né da fdisk né in /dev/disk/by-uuid:
bpxroot@debianq:~$ eject /dev/sdb
bpxroot@debianq:~$
bpxroot@debianq:~$ sudo fdisk -l | grep ^Disk\ /dev/sd
Disk /dev/sda: 298,09 GiB, 320072933376 bytes, 625142448 sectors
bpxroot@debianq:~$ ls -la /dev/disk/by-uuid/ | grep sdb
bpxroot@debianq:~$
ma il bus usb continua a vederlo:
bpxroot@debianq:~$ lsusb
Bus 003 Device 003: ID 04f2:b159 Chicony Electronics Co., Ltd CNF8243 Webcam
Bus 003 Device 002: ID 13fe:3d23 Phison Electronics Corp. USB DISK Pro
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
adesso però voglio usare la chiavetta sempre da una connessione ssh, quindi do il comando eject con l'opzione -t e il disco usb torna a essere visibile sia in /dev/disk/by-uuid
bpxroot@debianq:~$ eject -t /dev/sdb
bpxroot@debianq:~$
bpxroot@debianq:~$ sudo fdisk -l | grep ^Disk\ /dev/sd
Disk /dev/sda: 298,09 GiB, 320072933376 bytes, 625142448 sectors
Disk /dev/sdb: 7,46 GiB, 8006926336 bytes, 15638528 sectors
bpxroot@debianq:~$
bpxroot@debianq:~$ ls -la /dev/disk/by-uuid/ | grep sdb
lrwxrwxrwx 1 root root 10 ago 24 16:24 36E0-356D -> ../../sdb1
ma continua a non essere in mount:
bpxroot@debianq:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 1,5G 0 1,5G 0% /dev
tmpfs 299M 1,4M 298M 1% /run
/dev/sda5 46G 25G 19G 58% /
tmpfs 1,5G 0 1,5G 0% /dev/shm
tmpfs 5,0M 8,0K 5,0M 1% /run/lock
tmpfs 299M 88K 299M 1% /run/user/106
tmpfs 299M 84K 299M 1% /run/user/1000
Allora provo a attivare il mount con udiskctl, ma mi chiede l'autenticazione come root. Il problema è che se mi autentifico poi il mount lo fa come utente root e non è questo che voglio.
$ udisksctl mount -b /dev/disk/by-label/MULTIBOOT
==== AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount-other-seat ====
Authentication is required to mount USB DISK Pro (/dev/sdb1)
Authenticating as: root
Password:
allora, dato che le credenziale mi vengono chieste per questa azione:
org.freedesktop.udisks2.filesystem-mount-other-seat
Regolata dalle impostazioni presenti in questo file:
/usr/share/polkit-1/actions/org.freedesktop.UDisks2.policy
modifico il suo default in questo modo:
impostazione originale:
<!-- mount a device attached to another seat -->
<action id="org.freedesktop.udisks2.filesystem-mount-other-seat">
<description>Mount a filesystem from a device plugged into another seat</description>
<description xml:lang="zh_TW">掛載插入其他位置的裝置的檔案系統</description>
...
<defaults>
<allow_any>auth_admin</allow_any>
<allow_inactive>auth_admin</allow_inactive>
<allow_active>auth_admin_keep</allow_active>
</defaults>
</action>
nuova configurazione:
<!-- mount a device attached to another seat -->
<action id="org.freedesktop.udisks2.filesystem-mount-other-seat">
<description>Mount a filesystem from a device plugged into another seat</description>
<description xml:lang="zh_TW">掛載插入其他位置的裝置的檔案系統</description>
...
<defaults>
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
A questo punto, senza riavviare alcun servizio il mount funziona con l'utenza corrente: