Your message dated Tue, 4 Jul 2023 17:53:25 +0200
with message-id <8f52aa70-3e18-711f-bff4-49f30039e...@debian.org>
and subject line Re: Bug#1040325: Network drives other than NFS are no longer 
automatically mounted after boot
has caused the Debian Bug report #1040325,
regarding Network drives other than NFS are no longer automatically mounted 
after boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1040325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 252.6-1

Package: initscripts
Version: 3.06-4

Hi,

We have several CIFS drives specified in our /etc/fstab

Until Debian 11 (with isc-dhcp-client), they got automatically mounted 
all right after boot.

No longer in Debian 12 (with dhcpcd-base)

Even adding _netdev to the drives' options in /etc/fstab didn't help.

Some investigation showed that /etc/network/if-up.d/mountnfs (part of 
initscripts: this is the script responsible for mounting network drives 
when new connections are brought up) sources /lib/lsb/init-functions, 
which itself sources parts in /lib/lsb/init-functions.d

/lib/lsb/init-functions.d/40-systemd (part of systemd package) checks 
whether mountnfs.service is "masked", and if so, exits before mounting 
any drives.

=> which means that networked drives other than NFS are not mounted!

Manually "unmasking" mountnfs.service fixes the issue, however I have a 
feeling that on a future Debian upgrade, mountnfs.service might get 
masked again.

Thanks for looking into this,
-- 
Alain Knaff
Ingénieur Informaticien

LE GOUVERNEMENT DU GRAND-DUCHÉ DE LUXEMBOURG
Ministère de l'Environnement, du Climat et du Développement durable
Administration de l'environnement

1, avenue du Rock'n'Roll . L-4361 Esch-sur-Alzette
Tél. (+352) 40 56 56-309
E-Mail: alain.kn...@aev.etat.lu
www.emwelt.lu . www.environnement.public.lu . www.luxembourg.lu

--- End Message ---
--- Begin Message ---
Am 04.07.23 um 15:30 schrieb Alain Knaff:
Package: systemd
Version: 252.6-1

Package: initscripts
Version: 3.06-4

Hi,

We have several CIFS drives specified in our /etc/fstab

Until Debian 11 (with isc-dhcp-client), they got automatically mounted
all right after boot.

No longer in Debian 12 (with dhcpcd-base)

Even adding _netdev to the drives' options in /etc/fstab didn't help.

Some investigation showed that /etc/network/if-up.d/mountnfs (part of
initscripts: this is the script responsible for mounting network drives
when new connections are brought up) sources /lib/lsb/init-functions,
which itself sources parts in /lib/lsb/init-functions.d

/lib/lsb/init-functions.d/40-systemd (part of systemd package) checks
whether mountnfs.service is "masked", and if so, exits before mounting
any drives.

=> which means that networked drives other than NFS are not mounted!

Manually "unmasking" mountnfs.service fixes the issue, however I have a
feeling that on a future Debian upgrade, mountnfs.service might get
masked again.

Thanks for looking into this,

It appears you are using systemd as PID 1.
In this case, please purge the initscripts package. It is no longer needed and actually can cause issues.

In your case, if you want network drives to be mounted reliably during boot, you need to ensure that network-online.target is properly hooked up.

In case you are using NetworkManager, make sure NetworkManager-wait-online.service is enabled. For systemd-networkd, make sure systemd-networkd-wait-online.service.

I no longer use ifupdown, but I think the recommended practice there is to use "auto" instead of "allow-hotplug". That said, it also ships a ifupdown-wait-online.service service which you might want to use.

See also https://systemd.io/NETWORK_ONLINE/




Regards,
Michael

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---

Reply via email to