usbmount not running hook scripts

Turbocapitalist · 02-20-2019, 08:36 AM

usbmount is finding devices and mounting them just fine, but it is not running any hook scripts I have put in /etc/usbmount/mount.d/ The scripts there have execute permissions and can run standalone manually. Here is a log snippet:

Code:

Feb 20 18:25:06 d usbmount[1255]: mountpoint /media/usb0 is available for /dev/sda4
Feb 20 18:25:06 d usbmount[1255]: executing command: mount -text4 -osync,noexec,nodev,noatime,nodiratime,ro /dev/sda4 /media/usb0
Feb 20 18:25:06 d kernel: [  602.601902] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
Feb 20 18:25:06 d usbmount[1255]: executing command: run-parts /etc/usbmount/mount.d
Feb 20 18:25:06 d usbmount[1255]: usbmount execution finished

Despite what is reported in the logs nothing seems to happen. The script is not run.

What should I be looking at to get the script there (or anywhere elese) to execute?

This is on Raspbian GNU/Linux 9.8 (stretch) and I've already done the /etc/systemd/system/systemd-udevd.service.d/override.conf hack to get systemd to stop blocking the mounts. Is there something else to change or remove to get usbmount to run a script?

Edit: daemon logs:

Code:

Feb 20 18:25:05 d systemd-udevd[1232]: Process '/usr/share/usbmount/usbmount add' failed with exit code 1.

hoes · 02-20-2019, 01:45 PM

Have you looked at the manual of run-parts?

Turbocapitalist · 02-20-2019, 01:48 PM

Yes, and if I manually run run-parts using the line as given in the log then the script(s) run fine there. The scripts themselves seem to be OK. The weird part is that they ran once automatically today just fine.

hoes · 02-20-2019, 02:17 PM

Still sounds very strange.
How do you check that your scripts ran?
You could also inspect the usbmount source code to get a better understanding of the flow.

r37 · 02-20-2019, 03:25 PM

Are you sure that it is a usbmount-related problem? Cannot it be caused by weird systemd behavior?
Honestly, I do not know whether it is possible to get rid of systemd on Raspbian, but maybe it is worth testing on another system, e.g. on Devuan...

Turbocapitalist · 02-21-2019, 12:39 AM

I'm also guessing that it is a systemd problem blocking the script somehow. It's not possible to remove systemd, it is neither an init system nor modular, so a distro either goes all-in or avoids it completely. The mounting works fine, it's just that the script won't run (though it did run once) and I've found a systemd work-around.

There seems to be a Devuan GNU/Linux 2.0 (ascii) image for the Raspberry Pi Zero. I will give that a test parallel to this, but I would really like to find a solution or non-systemd work-around for Raspbian.

boncye · 04-24-2020, 07:35 AM

Quote:

Originally Posted by Turbocapitalist

I'm also guessing that it is a systemd problem blocking the script somehow. It's not possible to remove systemd, it is neither an init system nor modular, so a distro either goes all-in or avoids it completely. The mounting works fine, it's just that the script won't run (though it did run once) and I've found a systemd work-around.

There seems to be a Devuan GNU/Linux 2.0 (ascii) image for the Raspberry Pi Zero. I will give that a test parallel to this, but I would really like to find a solution or non-systemd work-around for Raspbian.

Hi Turbocapitalist, i have exactly the same problem. Can you tell me your workaround?

Turbocapitalist · 04-24-2020, 07:56 AM

Perhaps. That was over a year ago and there were several similar projects going concurrently. So I have no clear recollection.

Going through some old notes, the work-around might have been this systemd unit file:

Code:

[Unit]
Description=flashdrive script trigger
Requires=media-usb0.mount
After=media-usb0.mount

[Service]
ExecStart=/usr/local/bin/myownscript.sh

[Install]
WantedBy=media-usb0.mount

If that was not it, then the solution was probably upgrading the distro to Devuan.