Sure, Sure, if I have this problem again I will do all of this stuff that you ask. But the name of the thread is "filesystem check fails on boot, but filesystem isn't bad." This is a problem that it seems that not only I have had. I think it is probably is helpful to tell people that they can delete the fsck binaries and it will solve the problem. With respect to user error, the 8.10 install was straight off the official release CD. The only thing that I did differently than the absolute basic install was to partition some free space on my hard drive for the new file system. If the "out-of-the-box" installer cannot configure fstab correctly based on that kind of an operation, then that is hardly user error.
There are dozen of "flus" that people catch that are not caused by influenza: point taken. The same medicine, however, usually helps you feel better with all of them. Name of thread: "filesystem check fails on boot, but filesystem isn't bad." Problem I am having: filesystem check fails on boot, but filesystem isn't bad. I thought it might be useful to someone else who was having the same (or a similar) problem to know that deleting the fsck binaries fixes the problem for me. If the problem happens again I will do all the stuff that you ask before I post. On Fri, May 29, 2009 at 5:37 AM, Theodore Ts'o <ty...@mit.edu> wrote: > Hyperfitz, > > Can you open a new bug report, please? *Please* don't assume that > just because you have the same symptoms as someone else, that it is the > same bug. > > If two people went to the doctor, both complaining of a headache, one > might just have the flu, and another might have brain cancer. It is > not helpful to conflate the two in a single discussion. > > Please include in your bug report the output of the "blkid" program, the > output of "cat /proc/partitions", and the output of the failed fsck > transcript. It is also helpful if you try running e2fsck by hand, with > an explicit device specifier (i.e., "e2fsck /dev/hda5" or "e2fsck > /dev/sda3"). > > Also note that 99.9999% of the time these sort of problem is caused by > user error, or some kind of configuration error of /etc/fstab, or the > LABEL= specifier in /etc/fstab combined with more than one filesystem > with a label such as "/" --- especially if you have installed the > machine more than once and the Ubuntu installer has assigned more than > one filesystem with the label "/". > > -- > filesystem check fails on boot, but filesystem isn't bad > https://bugs.launchpad.net/bugs/48563 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “e2fsprogs” source package in Ubuntu: Incomplete > > Bug description: > Binary package hint: e2fsprogs > > Hello, > > I've just installed ubuntu dapper drake, and I have a persistent problem > where it fails the filesystem check during bootup, and I get dropped into a > root shell. Ignoring the problem lets me boot up, and if I check the > filesystem from the live CD (with fsck /dev/hda -f) it comes up clean. For > some reason it seems to be checking the root filesystem (/dev/hda5) even > though that's already been checked earlier on, and should be mounted at this > stage. The other filesystems check clean. I looked at the script > (/etc/rcS.d/S30checkfs.sh), and the fsck command includes the '-R' flag > which should tell it not to check the root filesystem, so I don't understand > why this is happening. As far as I can guess, the problem is that: a) for > some reason fsck is not picking up the fact that dev/hda5 is mounted as > root. b) because of this, it's checking the filesystem while still mounted, > and finding an error because of that. > > I've tried doing the following: > - booting from a live CD and checking the filesystem from that, including a > read/write bad blocks test. It always comes up clean or with a minor error, > but the same error comes up again when I reboot from the hard disk. > - rebuilding my partition table using fdisk (writing down the cylinder > numbers, deleting it and recerating it) > - looking at fstab. It's pasted below. > > # /etc/fstab: static file system information. > # > # <file system> <mount point> <type> <options> <dump> <pass> > proc /proc proc defaults 0 0 > /dev/hda5 / ext3 defaults,errors=remount-ro 0 > 1 > /dev/hda3 /local ext3 defaults 0 2 > /dev/hda1 /media/hda1 ext3 defaults 0 2 > /dev/hda4 /media/hda4 ext3 defaults 0 2 > /dev/hda7 /var ext3 defaults 0 2 > /dev/hda6 none swap sw 0 0 > /dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0 > /local/home /home auto defaults,bind 0 0 > /local/usr-local /usr/local auto defaults,bind 0 0 > > For the moment I'm carrying on using the system as it is, but I'm not happy > to do this in the long term if there's a persistent error. I've tried to do > everything I can to fix the problem, and it hasn't worked, so I'm filing > this as a possible bug. If you need any help finding the problem, I'm happy > to post logs etc. > -- filesystem check fails on boot, but filesystem isn't bad https://bugs.launchpad.net/bugs/48563 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
