[karmic] fsck on mounted filesystems breaks boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: upstart
As always with karmic as of today and this time also
with current ubuntu-boot PPA.
If any filesystem except "/" has an fstab(5) fs_passno value other than "0"
booting stops because fsck complains about not wanting to check
a mounted file system.
This bug was triggered by setting fs_passno of /boot to "2".
boot messages
#######
* Starting early crypto disks... [ OK ]
* Starting remaining crypto disks... [ OK ]
* Checking file systems...
fsck from util-linux-ng 2.16
/dev/sda6 is mounted. e2fsck: Cannot continue, aborting.
fsck died with exit status 8
* File system check failed.
A log is being saved in /var/log/
Please repair the file system manually.
* A maintenance shell will now be started.
/var/log/
#######
Log of fsck -C -R -A -a·
Tue Sep 22 01:58:48 2009
fsck from util-linux-ng 2.16
/dev/sda6 is mounted. e2fsck: Cannot continue, aborting.
fsck died with exit status 8
Tue Sep 22 01:58:52 2009
----------------
mount information at problem time
#######
# cat /proc/mounts | grep boot
/dev/sda6 /boot ext2 rw,noatime,
# mount | grep boot
/dev/sda6 on /boot type ext2 (rw,noatime)
fstab
#######
proc /proc proc defaults 0 0
/dev/mapper/root / ext4 errors=
/dev/sda6 /boot ext2 defaults,noatime 0 0
/dev/mapper/home /home ext4 defaults,
/dev/mapper/var /var btrfs defaults,
UUID=3a8850d6-
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0