Re: Root EXT3 FS move All files to Lost+Found after FSCK
- From: Phil Sherman <psherman@xxxxxxxxxxxxx>
- Date: Sun, 01 Apr 2007 02:54:50 GMT
Your fsck run placed the orphaned files in the lost+found directory. There's no way to relate them back to the original files unless you have before and after maps of the inodes - which nobody collects.
Your best bet is to reconstruct from your backups or rebuild from scratch.
If you have some critical files whose contents can be identified, you can try using grep to spit out file names containing matching content.
I had the same thing happen to me a three months ago on a RHEL4 system and decided that it wasn't worth the effort to try to recover the system. Fortunately, /home was (undamaged) on a different drive and I had backups of all tailored configuration files. I also had a detailed log of all installed software and the tailoring needed to integrate it with RHEL.
Phil Sherman
akim_ziadi@xxxxxxxxxxx wrote:
Hi All;.
Really need HELP; My Redhat 4 was not able to boot since a system
crash, reason No longr Journal for EXT3
We boot using Knoppix CDROM mount / partition /dev/sdb6, but mount
didn't succeed an request fsck
We then run fsck -y /dev/sdb6, A lot of correction have beed made
Try again, to mount /dev/sdb6 on /mnt "Now sucesfully", BUT :-
( Nothing in / bu all files have been move to /lost+found directory
with strange name starting #472829 .... ???
Question: How to recover thoses files to there orginal situation, in
another way, how to recover my root FS
What's #????? mean
Thanks for your help
- Prev by Date: Re: i have fedora 2 and a laptop
- Next by Date: newbie question
- Previous by thread: Re: i have fedora 2 and a laptop
- Next by thread: newbie question
- Index(es):
Relevant Pages
|
