fstab entry causes emergency mode to come up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
After upgrading from 14.04 to 14.10 and also from 14.10 to 15.04, the system goes into emergency mode when there is an entry in the /etc/fstab file for a <removable> hard drive that isn't connected. Here's the fstab file that caused it and the HITACHI entry has been commented out which fixed the problem.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb2 during installation
UUID=b7b39e46-
# /boot/efi was on /dev/sdb1 during installation
UUID=A0D7-CA74 /boot/efi vfat defaults 0 1
# swap was on /dev/sdb3 during installation
UUID=156b7a15-
#UUID=12EF-3326 /media/ben/HITACHI vfat rw,user,umask=0
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Mon Aug 17 10:54:23 2015
InstallationDate: Installed on 2014-09-03 (347 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitec
SourcePackage: ubuntu-
Symptom: dist-upgrade
UpgradeStatus: Upgraded to vivid on 2015-08-17 (0 days ago)
VarLogDistupgra
affects: | ubuntu-release-upgrader (Ubuntu) → mountall (Ubuntu) |
What exactly do you mean when you say "emergency mode"?
The expected behavior, when you boot Ubuntu and have a filesystem referenced in /etc/fstab for which the device is absent, is that the system will prompt, via plymouth, whether to continue waiting for the filesystem or to skip mounting it. This should be the case up through Ubuntu 14.10. For Ubuntu 15.04, with the switch to systemd the behavior will be different; but should still not result in the system booting to anything that could be considered "emergency mode".