Dependency resolver causes hang on boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
After upgrading to version 2.50 I had my server hang on boot without any useful messages. I could track this to a NFS type mount in fstab which is mounted under /home and that is another mounted fs in fstab. Like
/dev/xxx /home ext4 defaults 0 2
xxx:/srv/img /home/img nfs ro,nfsvers=3 0 0
Verified that with mountall v2.49 this works (kind of as it seems to be done first time when network has not finished setting resolv.conf from the info DHCP returns). But at least boot finishes and by the time one can log in the nfs mount is done.
Unlike with version 2.50 which either hangs, or when the mountpoint is moved somewhere under /, it boots but never mounts the NFS filesystem.
Since one of the bigger changes from 2.49 is trying to do those dependant mounts in the right order I suspect this caused the current situation.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: mountall 2.49
ProcVersionSign
Uname: Linux 3.11.0-7-generic x86_64
.run.mount.utab:
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Wed Sep 11 11:17:22 2013
InstallationDate: Installed on 2013-05-22 (111 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Alpha amd64 (20130521)
MarkForUpload: True
ProcKernelCmdline: BOOT_IMAGE=
SourcePackage: mountall
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in mountall (Ubuntu): | |
status: | Incomplete → Fix Committed |
Hi Stefan,
If you bring up the plymouth splash screen (hitting 'esc' at the video console, or booting with 'splash'), does it let you skip the stalled mount? And, which mount does it say is missing?
Can you boot with --verbose + splash on the kernel commandline, skip any missing mounts, and then attach /var/log/ upstart/ mountall. log?