this post was submitted on 20 Feb 2026
109 points (75.1% liked)
Technology
81621 readers
4613 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
can someone please tell me how to make .mount files start at boot for smb shares ffs? is the only thing systemd is failing for me.
I dont know what you are doing, but I have my smb shares simply in fstab and never heard of any .mount file
On modern systems, fstab entries are read by systemd and .mount files are automatically created for each entry. 😄
i am making them in salt-stack systemd templates/pillars. i will see what i miss when i do a fstab one.
Systemd can use .mount files to make services and stuff depend on the availability of a mount. They can either be created by hand or are created automatically from fstab.
IIRC You simply write/change the fstab as in every system. Then you say "systemctl daemon-reload" once, and this (re)creates your .mount files. Then "mount -a" or whatever you need.
thanks everyone.
https://wiki.archlinux.org/title/Samba#As_systemd_unit
That's the guide I followed on my desktop and laptop.
thanks,
Can you see if its trying and failing by using journalctl?
no matter what i do it only does on try.
Network not ready by time the mount is executed?
yup,
I have a service that pings the server:
And then I make the fstab entry depend on it:
I had something similar when I used to mount an NFS share. I had a bash line that would loop ping and then mount once ping succeeds. Having a separate service that pings and making the mount dependent on it is probably the better thing to do. Should also work when put in
Requires=in a.mountfile.My nfs mounts always add 1:45 to my boot even though I added _netdev to their lines in fstab. I don't get it.
Use
nofail doesn't interrupt the boot and 10 seconds is a more sane timeout. You can also use
And it will automatically mount the directory the first time it is accessed.