serioup problem after running fsck

[Michael Velez]

> -----Original Message-----
> From: redhat-list-bounces at redhat.com 
> [mailto:redhat-list-bounces at redhat.com] On Behalf Of Qi, Xlaoyan
> Sent: Monday, March 14, 2005 3:07 PM
> To: redhat-list at redhat.com
> Subject: serioup problem after running fsck
> 
> Hi All,
> 
> When I restarted My linux (Precision 670 work station) with 
> Linux enterprise version 3 preinstalled this morning, 
> following error shows: 
> 
> " Checking root filesystem
> 
>   / contains a file system with errors, check forced.
> 
>   Eoor reading block 35063145 (Attempt to read block from 
> filesystem resulted in short read) while reading indirect 
> blocks of inode 17531077
> 
>  
> 
>   /: UNEXPECTED INCONSISTENCY; RUN fsck manually.
> 
> "
> 
> So I did as shown suggested, run "fsck -y"
> 
>  
> 
> Now I have trouble to get into KDE, only gnome safe can work. 
> Also "chkconfig -list" and a lot of other commands can not 
> work either.
> 
>  
> 
> What should I do? 
> 
>  
> 
> Thanks for suggestion.
> 
>  
> 
> Cynthia
> 
>  
> 
>  
> 
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=subscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
> 

I haven't used fsck in over a decade so I'm sure there are better people on
this list to answer this question.  But here are my two cents.

The easiest and first thing is to run fsck again (although I have my doubts
that this would help given the errors you have).  Running it once is no
guarantee that the file system has been completely checked.  You need to run
it until you no longer get any errors (at least that's how it worked 15
years ago).  I once ran fsck 10 times before I had a clean file system and
it worked beautifully after that.  Fsck should always be run in single user
mode.

Did you shut down the machine properly the last time you used it?  If you
did shut down the machine properly the last time, then you may have a disk
problem (although I doubt this is it and it's more likely that the machine
was not completely shut down before the power was cut).  Your vendor must
have supplied you with a CD to check the hardware.  Before you check
anything, back up anything valuable. If you didn't shut down the machine
properly, ALWAYS shutdown properly using the shutdown command from the
command line or the shutdown menu in KDE (I believe ctl-alt-del will give
you the shutdown menu).

I don't know what that particular error you have is.

But the fact that there are a lot of commands that do not work is scary.  If
there were only a few or if you only had a few files missing, you could just
look in the lost+found directory in '/' and use the 'file' command on any
file in the directory to test whether it is an executable or not. If it's a
text file, you can use an editor to view the contents of the file and just
rename it to the correct file name. If it's an executable, you could just
try to execute it and see what happens and then potentially rename it to the
correct name.

The lost+found directory is used to connect any file that's 'lost' (ie. No
longer connected), back to the directory hierarchy.  Since it is the
directory hierarchy that holds the name of the file, the name of a file in
the lost+found directory is actually its inode number (which is how the file
system identifies a file).  Once you recognize what file you are looking at,
you can just rename it to the normal name and place it in the right
directory.

Anyway, hope this helps.
Michael