Bug#1086710: reportbug: if-up.d/mountnfs is always a NO-OP and should be fixed or removed
Mark Hindley
mark at hindley.org.uk
Tue Nov 5 13:18:21 GMT 2024
Control: close -1
Athanasius,
On Tue, Nov 05, 2024 at 01:07:41PM +0000, Athanasius wrote:
> My /home/users is correctly mounted, but that is possibly as part of
> the systemd integration of lightdm and that login process otherwise.
>
> My /mnt/tuesday/data0 NFS mount has *not* happened.
>
> And, indeed, I have this from the boot-time, before my user login:
>
> 2024-11-05T12:58:48.309395+00:00 emilia mount[5040]: mount.nfs: Network is unreachable
> 2024-11-05T12:58:48.309748+00:00 emilia systemd[1]: home-users.mount: Failed with result 'exit-code'.
> 2024-11-05T12:58:48.309856+00:00 emilia systemd[1]: Failed to mount home-users.mount - /home/users.
> 2024-11-05T12:58:48.310259+00:00 emilia mount[5042]: mount.nfs: Network is unreachable
> 2024-11-05T12:58:48.341092+00:00 emilia systemd[1]: mnt-tuesday-data0.mount: Failed with result 'exit-code'.
> 2024-11-05T12:58:48.341209+00:00 emilia systemd[1]: Failed to mount mnt-tuesday-data0.mount - /mnt/tuesday/data0.
>
> i.e. systemd process failing to mount them, because it tried *before*
> the network was properly configued.
Sorry it isn't fixed (yet!), but I am glad you are closer to finding the cause.
Since initscripts is not involved, I will close this.
Good luck!
Mark
More information about the Debian-init-diversity
mailing list