Arch Linux

jamdox

Member

Registered: 2015-05-02

Posts: 46

systemd oneshot service to run at su level? [SOLVED]

Hi all,

Migrating my home server over from osx, so I have a number of *ominous pause*

JOURNALED HFS+ DISKS

which I want to enable rw.

I know the traditional answer is to disable journaling, but the new hotness (?) is to unmount, run fsck.hfsplus, remount and suddenly...

"it just werks."

.

So I have the following systemd service in /etc/systemd/system/:

[Unit]
Description=Run fsck.hfsplus on journaled hfs+ drives and remount, enabling r/w.
After=tmp.mount
#tmp.mount seems to be the last mount

#list of disks and mountpoints
# /dev/sdd2 /mnt/Big2
# /dev/sde2 /mnt/Big3
# /dev/sdg2 /mnt/Big4
# /dev/sdf4 /mnt/Big5


[Service]
Type=oneshot
ExecStart=/user/bin/umount /mnt/Big2
ExecStart=/user/bin/umount /mnt/Big3
ExecStart=/user/bin/umount /mnt/Big4
ExecStart=/user/bin/umount /mnt/Big5
ExecStart=/user/bin/fsck.hfsplus -f /dev/sdd2
ExecStart=/user/bin/fsck.hfsplus -f /dev/sde2
ExecStart=/user/bin/fsck.hfsplus -f /dev/sdg2
ExecStart=/user/bin/fsck.hfsplus -f /dev/sdf4
ExecStart=/user/bin/mount -a


[Install]

This give me a generic-ish error

Job for diks.service failed. See "systemctl status diks.service" and "journalctl -xe" for details.

Running systemctl status diks.service gives

● diks.service - Run fsck.hfsplus on journaled hfs+ drives and remount, enabling r/w.
   Loaded: loaded (/etc/systemd/system/diks.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2015-05-02 13:55:56 CDT; 6s ago
  Process: 1254 ExecStart=/user/bin/umount /mnt/Big2 (code=exited, status=203/EXEC)
 Main PID: 1254 (code=exited, status=203/EXEC)

and journalctl gives me nothing.

My impression is that the script service isn't running at the single user level, so that's what I'm asking for help with in this post.

If you think the error is something different, or the whole thing is ill-advised, please let me know.

Last edited by jamdox (2015-05-02 19:35:26)

loqs

Member

Registered: 2014-03-06

Posts: 17,440

Re: systemd oneshot service to run at su level? [SOLVED]

Should the path  /user/bin/ should not be /usr/bin/ ?

jamdox

Member

Registered: 2015-05-02

Posts: 46

Re: systemd oneshot service to run at su level? [SOLVED]

fuuuuu... let me try this

EDIT: yeah, we seem to be fscking...

EDIT2: mostly works, just going to substitute uuid's for directories.

Thanks.

Last edited by jamdox (2015-05-02 19:29:52)