Re: BOOT fs (startup) get corrupted

From: Michele Andreoli (
Date: Sun Aug 20 2000 - 11:08:24 CEST

On Sat, Aug 19, 2000 at 08:11:50PM +0200, dumas patrice nicely wrote:
> Hi, (I promise it is the last message...)
> I have a problem with muLinux, that I can't well reproduce. Sometimes the
> BOOT fs, that is on the floppy, not compressed, and mounted under
> /startup, gets corrupted. I get the message,
> mounting unchecked fs, do e2fsck,
> and also some errors sometimes while reading files, or doing cat,
> or the like. When I do a e2fsck, it totally destroys the filesystem. Does
> someone have such a problem, or an idea why it happens or how to check
> ext2 problems ?

On the BOOT section I left a very little free disk space for saving
profiles. Unfortunately, if you save more that ONE profile, you destroy
the filesystem.

> Michele, I know the disk is overcrowded, but could it be possible to have
> e2fsck on it ? The one I have is certainly much too big, but it is not a
> dynamic executable, maybe it exists linked with the libc5 ? I think the
> response is no, but... ;-)

e2fsck is in the EXT floppy, linked with libc5. To put e2fsck in the
first floppy mean to remove 5-6 command from it :-(


I'd like to conclude with a positive statement, but I can't 
remember any. Would two negative ones do?       -- Woody Allen
To unsubscribe, e-mail:
For additional commands, e-mail:

This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:15 CET