Very Computer

> I am running RH 7.1.  The power went out at my house and my Linux system
> went down the hard way.  When I started the system back up after the power
> came back on I got the following error msg.:

> Checking Root filesystem
> / contains a file system with errors, check forced
> /:
> UNATTACHED inode 24577
> /: unexpected inconsistency; RUN fsck manually.
> (i.e., without -a or -p options)
> *** 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):

> After I type in the ROOT password I get a command prompt saying "filesystem
> #1".  When I type "fsck" the command prompt changes to "filesystem #2".  I
> repeated this all the way to "filesystem #250".  That's where I stopped.  As
> far as I know, it would have gone on forever!

> When I run the "shutdown -h now" command and restart my system I get the
> same problem.  Anyone know how I can get my system back up and running?
> Thanks for any and all help.

> Lamar

> > I am running RH 7.1.  The power went out at my house and my Linux system
> > went down the hard way.  When I started the system back up after the power
> > came back on I got the following error msg.:

> > Checking Root filesystem
> > / contains a file system with errors, check forced
> > /:
> > UNATTACHED inode 24577
> > /: unexpected inconsistency; RUN fsck manually.
> > (i.e., without -a or -p options)
> > *** 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):

> > After I type in the ROOT password I get a command prompt saying "filesystem
> > #1".  When I type "fsck" the command prompt changes to "filesystem #2".  I
> > repeated this all the way to "filesystem #250".  That's where I stopped.  As
> > far as I know, it would have gone on forever!

> > When I run the "shutdown -h now" command and restart my system I get the
> > same problem.  Anyone know how I can get my system back up and running?
> > Thanks for any and all help.

> > Lamar

> Lamar

> Try it with
> #fsck -y /dev/hdxx

> where /dev/hdxx corresponds to the partitions that need checking, which
> will give a "yes" answer to all the questions.

> Chris