l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2001 Dec 30 17:14

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Red Hat system check
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Red Hat system check

begin: Ehrhart, Jay <ehrhart@ycoe.org> quote
> Over the weekend, my ofice lost power, the UPS was depleted and my Red Hat
> 7.0 box went down.
> Now I am having errors when I try to bring it backup. This is what happens;
> The boot starts normally.
> The message "contains a file system with errors, check forced" appears.
> "Unexpcted Inconsistency; run fsck manually"
> "An error occurred during the file system check"
> "Dropping you to a shell; the system will reboot when you leave the shell"
> "Give root password for maintenance, or type Control-D for normal startup"
> If I use control-D, it reboots and brings me back to the same place.

control d isn't what you want to do.

> When I enter the password and enter maintenance it shows;
> "Repair filesystem 1 #"

> So what do I need to do after I enter the password and enter maintenance to
> repair this?

the filesystem can be corrupted if the hard drive loses power during a write
operation (or a few other conditions).  fsck wants to make sure your
filesystem is ok.

apparently, on of your partitions has an error on it that fsck wants to fix.
the error is serious enough that fsck wants human intervention.  but ext2 is
a very resiliant filesystem, and fsck is a very intelligent program.   what
fsck wants to do is almost certain to be the right thing, but it still wants

you need to figure out on which partition fsck failed.  usually, when you
watch the system boot, it'll tell you.   something like:

Checking /dev/hda3
============================================ /                   63%
Filesystem inconsistancy.  Please run fsck manually (without the -a option).

i've never seen "repair filesystem 1 #" but perhaps that means /dev/hda1
needs to be repaired?

if you can't tell, just fsck all the partitions.  you can't hurt anything.
as long as the partition is unmounted, or at least mounted as read-only.

after doing this, you can safely reboot the system.

btw, you may want to use fsck -y which answers "yes" to all of fsck's


PGP Fingerprint: B9F1 6CF3 47C4 7CD8 D33E  70A9 A3B9 1945 67EA 951D
PGP Public Key:  finger p@dirac.org
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.