Hi Gary
To understand which service might be affected by the problem, could you
check if one either hal or rmvolmgr produce informative output?
Also another thing that might have changed is behaviour in the Mate
components in the UI that control the mounting. What do the GUI tools
say about mounting?
-Till
On 03.06.21 11:11, Gary Mills wrote:
A couple of weeks ago, I upgraded my OI systems to the current version
of OI. Everything seemed to work, although I didn't test everything.
Yesterday, I inserted a USB stick into one of the systems, and was
surprised that it didn't mount. It used to work. This event start me
on an investigation.
All of my USB sticks use a FAT32 filesystem and one FDISK partition.
They all automount on Windows 10 and show no errors. On my test OI
system, running the 2021-05-15 version of OI, they do not automount.
A reboot did not help. The "fstyp" command for the :1 device shows a
"pcfs" filesystem. I am able to mount and umount the device as root.
It shows the correct content.
When I booted the 2020-11-27 BE on that same system, the USB stick did
automount. A window popped up showing the contents of the device. It
also showed up in "mount | grep media". Another USB stick also
automounted the same way.
I conclude that something happened between those two versions of OI
to prevent USB sticks from mounting. I don't know what changed or
what is missing. Has anyone else seen the same problem?
Automounting is complicated. These are three services that have to
be operating properly for USB sticks to be automounted:
$ svcs hal dbus rmvolmgr
STATE STIME FMRI
online 20:54:09 svc:/system/dbus:default
online 20:54:11 svc:/system/hal:default
online 20:54:11 svc:/system/filesystem/rmvolmgr:default
All three of them are online on all of my OI systems.
_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev
