boot process isn't paused while fsck runs on partition: boot process is completed with fsck running in the background preventing partition from mounting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
mountall (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
util-linux (Ubuntu) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Binary package hint: usplash
I had a problem mounting my /dev/sdb1 partition the last couple of times after booting up Ubuntu. I got the following error when trying to mount the partition:
mount: /dev/sdb1 already mounted or /media/data busy
so I tried issuing the following command and I could see that fsck was running in the background, without having notified me, checking /dev/sdb1, and not while showing the splash screen and a progress bar like it usually does:
rune@runescomp:~$ sudo fuser -m /dev/sdb1
/dev/sdb1: 804
rune@runescomp:~$ ps aux | grep 804
root 804 5.0 3.4 72528 71164 ? D 21:29 0:50 fsck.ext3 -a /dev/sdb1
rune@runescomp:
Description: Ubuntu karmic (development branch)
Release: 9.10
rune@runescomp:
usplash:
Installed: 0.5.39
Candidate: 0.5.39
Version table:
*** 0.5.39 0
500 http://
100 /var/lib/
ProblemType: Bug
Architecture: i386
Date: Wed Sep 30 21:54:05 2009
DistroRelease: Ubuntu 9.10
MachineType: . .
NonfreeKernelMo
Package: usplash 0.5.39
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_DK.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: usplash
Uname: Linux 2.6.31-11-generic i686
UsplashConf:
# Usplash configuration file
# These parameters will only apply after running update-initramfs.
xres=1920
yres=1440
dmi.bios.date: 05/26/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: IP35 Pro XE(Intel P35-ICH9R)
dmi.board.vendor: http://
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: System Enclosure Manufacter
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: .
dmi.product.
dmi.sys.vendor: .
summary: |
- fsck automatically runs silently in the background after booting up + boot process isn't paused while fsck runs on partition: boot process is + completed with fsck running in the background preventing partition from + mounting |
Changed in ubuntu-release-notes: | |
status: | Fix Released → Fix Committed |
Changed in ubuntu-release-notes: | |
status: | Fix Committed → Fix Released |
Thank you for taking the time to report this bug and help to improve Ubuntu.
Effectively, this is by design; filesystems that aren't required to bring up the desktop should not block the desktop, they should be handled in parallel. However, there's probably a use case for users being able to configure mountall (which is what handles fscks and tells gdm when it's ok to start) to be more strict in waiting for additional filesystems to start up, as well as for mountall feeding progress information via usplash; so reassigning this to the mountall package for Scott to weigh in.
As a workaround, I believe you could change /etc/init/gdm.conf from
start on (filesystem and ...
to
start on (stopped mountall EXIT_STATUS=0 and ...
to declare that you don't want gdm to start up until all your drives are mounted. This is not something that should be set as a default in the distribution, however, since it would have adverse interactions for any users who automount network filesystems at boot time.