this post was submitted on 20 Feb 2026
113 points (75.3% liked)

Technology

81621 readers
4601 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. 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.
  9. Check for duplicates before posting, duplicates may be removed
  10. 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
[–] avidamoeba@lemmy.ca 4 points 19 hours ago (1 children)

Network not ready by time the mount is executed?

[–] Eryn6844@piefed.blahaj.zone 2 points 18 hours ago (1 children)
[–] tinsuke@lemmy.world 4 points 18 hours ago (1 children)

I have a service that pings the server:

cat <<EOF | sudo tee /etc/systemd/system/ping-smb.service
[Unit]
Description=Blocks until pinging 192.168.1.10 succeeds
After=network-online.target
StartLimitIntervalSec=0

[Service]
Type=oneshot
ExecStart=ping -c1 192.168.1.10
Restart=on-failure
RestartSec=1

[Install]
WantedBy=multi-user.target
EOF

sudo systemctl enable ping-smb.service

And then I make the fstab entry depend on it:

x-systemd.requires=ping-smb.service
[–] avidamoeba@lemmy.ca 3 points 17 hours ago

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 .mount file.