>
> I'm not sure why your system needed to be checked for each boot.
> Perhaps you can post the exact error message? I'm pretty sure it wasn't
> fragmentation. What it *might* be saying (but again we can't verify
> without an error message) is that your filesystem contains errors that
> cannot be fixed in non-interactive mode (i.e. you need to run fsck
> manually).
>
> It's hard to tell you what option you need when we are unsure what
> problem you are trying to fix.
>
Look for the thread "running e2fsck pre-boot" on this list.
Willie Wong had the answer: tune2fs, not e2fsck.
$man tune2fs
...
It is strongly recommended that either -c (mount-count-depen-
dent) or -i (time-dependent) checking be enabled to force peri-
odic full e2fsck(8) checking of the filesystem. Failure to do
so may lead to filesystem corruption (due to bad disks, cables,
memory, or kernel bugs) going unnoticed, ultimately resulting in
data loss or corruption.
...
I ran it before on my SSD and it worked like a charm. But I neglected
to run it on the
SD card that holds /home and /var on my eee. Now it is starting to
display the same symptons. Yes I know, ext2 is rather retro, but I was
persuaded to use it by reading the forums and now it's a lot simpler
just to run tune2fs rather thman scrap the system and start again.
mw
