Network filesystems don't mount on boot

Bug #1536294 reported by Jonathan Kamens on 2016-01-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Medium
Unassigned

Bug Description

Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

They don't mount at boot. If I list them by host name in /etc/fstab, mount says name resolution failed in the boot logs. If I list them by IP address, mount says the network is unreachable in the boot logs.

If fixed this by adding the following in /etc/systemd/system/remote-fs-pre.target.d/override.conf:

[Unit]
Requires=NetworkManager-wait-online.service
After=NetworkManager-wait-online.service

See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu as well.
---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: jik 2922 F.... pulseaudio
 /dev/snd/controlC1: jik 2922 F.... pulseaudio
 /dev/snd/controlC0: jik 2922 F.... pulseaudio
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
InstallationDate: Installed on 2016-01-16 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Predator G6-710
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-25-generic N/A
 linux-backports-modules-4.2.0-25-generic N/A
 linux-firmware 1.149.3
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/21/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A1
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer
---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
DistroRelease: Ubuntu 15.10
InstallationDate: Installed on 2016-01-16 (4 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Predator G6-710
NonfreeKernelModules: nvidia
Package: systemd 225-1ubuntu9
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Tags: wily
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 4.2.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/21/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A1
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1536294

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected wily
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

affects: linux (Ubuntu) → systemd (Ubuntu)
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in systemd (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily

Changed in systemd (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Jonathan Kamens (jik) wrote :

My computer was newly installed with 15.10, no prior Ubuntu version, so I don't know whether the problem is new in this release.

I don't see how a upstream kernel would be relevant. This is not a kernel issue, it's an issue with systemd trying to mount filesystems before the network is all the way up.

If you can give me a plausible theory for why the underlying kernel, rather than systemd, might be at fault here, then I'd be willing to take the time to build and test an upstream kernel. Absent such a plausible theory, it just seems like you're wasting my time because you haven't actually read and understood the details of the bug?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers