Help with fsck!

Erik Lagergren

unread,

Oct 30, 2000, 12:15:18 PM10/30/00

to

Hi,

I got a problem I'm rather new to linux so I don't know much. Once I
didn't exit linux as I should and now when I try to boot it says that my
harddrive "contains a file system with error, check forced". It runs
the check and finds an error "unexpected inconsistency"; RUN fsck
manually. I've tried that but haven't succeeded.
Anyone?

--
Erik

Timothy Giedd

unread,

Oct 30, 2000, 2:29:55 PM10/30/00

to

I have had that problem.

Back in 1999 when I had Red Hat v5.2 and just starting Linux I was a
total newbie. When I installed it I screwed up and put everything on
the root file system.
About a month after using Linux and not shutting it down properly (using
the control-alt-delete combination as a user or 'shutdown now' as the
root user) I booted up, and it said "/dev/hda3: UNEXPECTED
INCONSISTENCY: RUN fsck MANUALLY.

As you said, I did, but not much happened.
It would not load Linux, and wouldn't work.

After a month of research I tried it again. I went to the single user
mode as root by entering the command "init s" I then ran the command
"fsck /" It ran it, fixed several file allocation problems, deleted
both (unnecessary) files, and it then worked fine. I fixed it 12/14/99
and it worked until I upgraded to v6.2 in July. I now ALWAYS terminate
my Linux sessions using the three-fingered (control-alt-delete) salute
as a user, and 'shutdown -h now' as root. No more problems.
I love Linux.

Leroy Smith
lc...@lcsc.com

RogerB

unread,

Oct 30, 2000, 2:30:38 PM10/30/00

to

You have to run it from a resue disk. I don't think it will
work if the file system is mounted. Most distros have a rescue option
from their boot disk with options on the cd or a second disk like debian.
If it say that your superblock is knackered you can use this line
2efsck -f -b 8193 /dev/hdx where x is you broken partition eg. a b etc.
The 8193 is the location of your superblock and if that is broke add
8192 to the number(16385) and try again repeat the add untill you find one.
Sometime just the -f works to.

Hagbard Celine

unread,

Oct 30, 2000, 5:02:05 PM10/30/00

to

Erik Lagergren <eri...@swipnet.se> wrote:
OK, you obviously can't do a 'man fsck', so here goes :o)

You'll need to make a note of the drive that has the error, then boot from
floppy. If you have an emergency disk(s), use that, otherwise, you might
be able to use a setup disk, depending on the distribution you installed.
Slackware's setup disks will work fine, for example, but Debian's might
present a problem, as it throws you right into an install script, if
memory serves.

Anyway... Once you have booted from floppy, you can run an 'fsck -r' on the
problem drive. If /dev/hda has the error, for example, you would run
'fsck -r /dev/hda'. This will run a check on the drive, and when an error is
found, will ask you for confirmation to correct it. Hopefully, this should
do the job for you. given that the error is not too serious. Once the fsck is
finished, you should be able to reboot to your normal system.

Hope this helps,
Hagbard

> Hi,

> --
> Erik

--
Jesus saves sinners - and redeems them for valuable prizes.

dpace

unread,

Nov 2, 2000, 2:09:55 PM11/2/00

to

Which hard drive has the error?
How do you run the fsck command?
What reply message do you get after running fsck?

Proper example:

fsck /dev/hda1

answer Y to any questions.

--
David Pace - Free commodity/stock graphing software
and Linux links at http://www.daveware.com