I tried upgrading to mountall-0.2.0~boot3 again and the same thing
happened -- I couldn't boot. The boot process just stopped at the point
where the filesystems would be checked and mounted. It didn't ask to
manually run fsck, so I'm not sure what's wrong.
I modified the script section of /etc/init/mountall.conf as follows so
that I could collect a log of what mountall-0.2.0~boot3 was doing:
script
# in case I need to manually run fsck before mountall runs
/bin/bash -li
# create a writeable place to put a log file
mount -t tmpfs none /tmp
# redirect stderr/stdout of all of this to a log file
(
set -x
cat /proc/mounts
. /etc/default/rcS
[ -f /forcefsck ] && force_fsck="--force-fsck"
[ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix"
[ -n "$TMPTIME" ] && tmptime="--tmptime=$TMPTIME"
mountall --debug --daemon $force_fsck $fsck_fix $tmptime
) >/tmp/mountall.log 2>&1
# so that i can copy the log file to a more permanent location
/bin/bash -li
end script
Attached is the log file.
** Attachment added: "mountall-0.2.0~boot3 debug output during failed boot"
http://launchpadlibrarian.net/33338987/mountall-0.2.0%7Eboot3_will_not_boot.log
** Changed in: mountall (Ubuntu)
Status: Incomplete => New
--
/forcefsck doesn't add '-f' argument to fsck (for ext4, ext3, ext2)
https://bugs.launchpad.net/bugs/435707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
