Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
MacLemon
@MacLemon@chaos.social  ·  activity timestamp last week

Been fighting Debian #Trixie 13 for two days now. It seems to be impossible to auto mount an NFS4 share at boot. Manually it works fine.

Not even with `ro,auto,sync,default,hard,noatime,retrans=15,x-systemd.after=network-online.target,x-systemd.automount,x-systemd.requires=network-online.target,_netdev,clientaddr=
192.0.2.13` in `fstab`.

This used to work in Debian #Bookworm 12, Ubuntu jammy (22) and noble (24).

Next attempt: `autofs` or directly in OCI container

  • Copy link
  • Flag this post
  • Block
Franziska
@kunsi@chaos.social replied  ·  activity timestamp last week

@MacLemon Does systemd even create the correct `.mount` files?

If yes, you should be able to use the journal to tell why it doesn't want to mount (just give it the unit name)

If not, you could try to generate the ,mount and .automount files manually: https://git.franzi.business/kunsi/bundlewrap/src/branch/main/bundles/nfs-client/files

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.1-alpha.8 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login