fsck fails. Code: Bad EIP value. Segmentation fault.
 

Linux newbie. Sarge installation on an OmniBook 4000CT (486DX4 32Mb RAM machine).

I did have it running fine, but after spending several days in modconf and then restarting, I started getting this message while booting:

fsck.ext2 for device /dev/hda6 exited with signal 11

I am then offered to fix the problem manually by typing in the root password or to continue with Control-D

If I continue I can login without a problem.

Attempts to run fsck once logged on as root also fail, but this time I get the same error in English:

Code: Bad EIP value. Segmentation fault.


Googling for "signal 11" I found out that signal 11 is segmentation fault, something trying to access the wrong memory or what not. People got it with RAID controllers or on Dell machines with 1Gb memory, but neither is my case.

What do I do? Any ideas? Any questions?

fsck is to check a fs for consistency under Unix clones thereof. Journaling fs such as fs in freebsd :bckgr fsck
Extended Instruction Pointer: EiP

How does that help?
Why post such nonsense?

Sorry , anybody can explain why press crt-D ?

Re: fsck fails. Code: Bad EIP value. Segmentation fault.
 

I had the same kind of problem but with ubuntu, but I still haven't been able to sort it out did you mange to fix the problem or not.. I did the right thing and fsck continued and could not read the nodes or some sort I suddenly found my self not being able to run grub full and error 17 occured..