There are a few more errors that appear but I can't capture (or read) them in time before agetty or whatever loads. What's strange to me is dosfsck is trying to run when I don't have any auto-mounted NTFS or FAT partitions. sda1 is /boot, ext2; sda2 is /, ext4; sda3 is /home, ext4; I believe this may have been caused by installing dosfstools (which I needed to do in order to format an SD card last night before bed). I haven't touched anything relating to the system in a few days, and it booted just fine last night...

Any ideas? I tried to load the rescue boot option and it didn't even get to a bash prompt...

PROBLEM: my `/etc/fstab` file had 2s in the last field for my not-necessary-at-boot filesystems.

SOLUTION: By changing the fields to zero (0), I told fsck not to check them at boot and avoided the problem. Thanks to BillWho for the /etc/fstab fix.

Last edited by zlg on Mon Oct 01, 2012 7:48 pm; edited 1 time in total

fsck checks for a file /fastboot and if it exists it will skip filesystem checking.

Not sure about dosfsck, but it might be worth a shot. You might have to boot a live media to create the file or try remounting rw

As far as I know, fsck looks at fstab to determine filesystems to check.

I had seen something about /fastboot on some other threads I saw. I'll give that a shot. I also thought that I might've left something in fstab to automatically mount, but it doesn't look like it:

Code:

# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#