Mathiasdm wrote: > /dev/hda1 FAT32 +-3GB (Acer recovery partition) I've never heard of this Acer recovery before, but it may be liable to confuse dosfsck, causing it to take so long and ultimately fail. It may be worth a try to investigate if older versions of dosfsck have this problem, too.
> Why does it drop into a shell? If any of the file system checks at boot time should fail, you are automatically dropped into kind of an "emergency" root shell. This is to give you a chance to fix the problem before the boot procedure continues. You *should* be able to leave this shell using the 'exit' command or by pressing Ctrl-D. > Ctrl-C and Ctrl-D didn't work anymore What do you mean by "didn't work anymore"? Do you get any screen output after pressing Ctrl-D? What happens? If your computer just doesn't react to keypresses (seems to be "hanging"), try holding Alt+SysRq and pressing 'R'. This will put your keyboard into raw mode. After that, repeat your Ctrl-... procedure. This is only a guess, though -- it all depends on what you mean by "didn't work anymore" ;) Anyway, whatever the problem with this partition is, there may be a temporary workaround. It seems you haven't laid your hands on the command line too often yet, so I'll try to be verbose, just in case. In the root shell, type in 'nano /etc/fstab'. Using the nano editor should be pretty much self-explanatory. Find the line which tries to mount your hda1 partition. The last character in this line, an integer, specifies which priority the partition should have in the boot-up file system check. Probably, it says '2' right now. Change this into '0', meaning "skip this partition". Save your file, exit nano, and exit the shell. On the next reboot, the recovery partition won't be checked anymore. -- filesystem check fails on boot, but filesystem isn't bad https://launchpad.net/bugs/48563 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
