Re: Help with fsck.

The opcion -y I suppose not is the most recomendable, because if you 
have problems whith inodes when the machine boot that is because the 
system not know how to associate the name of the file to the archive, 
then in this case, when you do an fsck of the device the system present 
to you the inode the date of creation of the file and the permisology in 
some cases you can remove it because they are files of 0 bytes and 
whitout importance for the system, but if you see that the file is newer 
and more of 0 byte the you must say to the system "save the file" the 
the system save the file in the directory "lost+found" in the root of 
the file system. After the process end you can go to that directory 
(lost+found) and edit the file that have name of the inode y put it in 
the path correct with  the name that it has been had.

In this proceess I think you can have much care, because if the system 
not boot that is because the system lost a link or need an importat file 
of the system and the administrator of the system have to investigate 
what is the mater.

I home it help you to undertand the problem.



Hunt,Russ wrote:

>Hi Gary
>
>Enter the root password.
>
>then, from the command line, run fsck on the hard drive in question.
>
>For example, if it's stopping on /dev/hda1, run "fsck /dev/hda1"
>
>You can also add the -y switch ("fsck -y /dev/hda1"). To clarify a bit,
>"fsck -y" means "run fsck and automatically answer 'y' to every question.".
>Can save on pressing the y key unless you want to see the questions fsck is
>asking
>
>Russ
>
>-----Original Message-----
>From: gary.park [mailto:[email protected]]
>Sent: 09 April 2003 09:15
>To: [email protected]
>Subject: Help with fsck.
>Importance: High
>Sensitivity: Personal
>
>
>Dear All,
>
>I seem to have developed a problem with the root of the installation of
>Redhat 7.1 on a PC, the filesystem is checked at boot after reporting
>inconsistencies and appears about 90 percent intact but obviously fails
>after that. The following is reported:
>
>root filesystem contains a file system with errors, check forced
>
>unattached inode 2617557
>
>/unexpected inconsistency; run fsck manually (ie, without -a or -p
>options)
>
>[FAILED]
>
>error
>dropping into shell
>
>However, once at the shell prompt all my attempts to run fsck prove
>useless. This is my inability I'm having problems with not Linuxs',
>although the manual for fsck is not the most revealing document.
>
>Please help - how do I get fsck to run (do I need to put something for
>ALL the options and operands or is it much simpler than that) and repair
>the fault.
>
>Many thanks
>
>Gary J Park
>
>
>
>
>_______________________________________________
>Seawolf-list mailing list
>[email protected]
>https://listman.redhat.com/mailman/listinfo/seawolf-list
>
>
>
>_______________________________________________
>Seawolf-list mailing list
>[email protected]
>https://listman.redhat.com/mailman/listinfo/seawolf-list
>  
>


-- 


			Lic. Juan E. Infante
		Gte. de Comunicaciones y Servidores
			Universidad Metropolitana
			Tlf: 242-63-71