Linux does a scheduled fsck (file system check) after a certain number of boots. It takes a while and there should be a progress bar. I've seen 27, 37, you name it. Any time it finds what it thinks is an error it will give directions and ask permission to fix something. Any time I've had an fsck failure fsck screwed up a fix and it was time to re- format the partition. It's been possible to save files from the partitions before the re-format.
If I fumble around the help files it will say how to set the scheduled mounts per fsck for a partition. I've tried 1000000 without much luck. I don't know the max. fsck is similar to the Windoze file system check it does when it thinks the system was turned off without shutdown. fsck seems to be a common tool across different Linux's. Now if I do an install on a dual or triple or quad boot, install changes the partition's UUID. This is messy because booting one of the other images won't be able to find the previous UUID to do an fsck on it so fsck fails. Do an "exit" to continue, or Ctrl-Alt-Del. With a bit of editing on /boot/grub/menu.lst and /etc/fstab this can be straightened out. As far as I can tell, Ubuntu developers have no intention of fixing this mess. Jerry -- Gutsy shutdown doesn't https://bugs.launchpad.net/bugs/119308 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
