Closed Roaders closed 2 years ago
I'm getting the same issue (Ubuntu 20.04 using the distributed version). But if I manually run "sudo mount..." (and copy the mount command from the log) it DOES mount. So the command is right.
I also see "FAT-fs (sda): Volume was not properly unmounted. Some data may be corrupt. Please run fsck." in the log, which I don't get when I run the mount manually.
I'm wondering if it's mounting and then unmounting? Or if there is some other mount error that isn't being logged?
it is caused by systemd which is using private mount
it is caused by systemd which is using private mount
thanks, @jaccc -- is there a fix/workaround?
Strangely, even though the "mount" is being private, the /var/run/usbmount symlink gets created no problem...
Aha, looks like Issue #25 explains the issue and the fact that the "native" usbmount is STILL too old!
Yes, I should have updated this. I did manage to get it working by cloning, building and installing the latest version from Github. I think that the issue I had initially was just that I had the wrong file system on the SD card.
I have setup a new raspberry pi lite OS specifically to test usbmount (so it's a brand new image downloaded today and there is very little else on the system). I am having quite a few issues getting usbmount to work.
Currently I have the latest version from apt-get (0.0.22) isntalled and I am the closest that I have been to getting usbmount to work. I currently get this output:
as you can see it runs the mount command - BUT the drive is not mounted. If I run the command myself (with sudo) then the drive is mounted fine. I am using the normal pi user. I am not sure what user usbmount uses.
I have also cloned the repo and built 0.0.24 locally and tried that. That does not work as well and doesn't run the mount command. I get: