hey-- thanks for that! thanks for reminding me!! now that i have enough drive space, i'll bet i can do this!!
i actually attempted to get Knoppix on more than one occasion. seems every time i work on getting that Torrent, i spend half-an-hour trying to install torrent software, configuring firewall / ports... fool around w/ YumEx for another hour, and by then so distracted and behind schedule from wasting my own time, that i concede to return another day! haha... ugh!
I assume you have experience w/ this as being a "best-of-breed" data recovery for Fedora Core 5? (anyone?)
below is just my own little anecdotal account of "data loss", data recovery utilities, patience, and ignorance-- not specific to the Fedora Core 5 Filesystem issue i presented above, but perhaps useful for someone's search terms. to learn of my experience may help someone to prevent their own disaster. If you're in a hurry to find Fedora-specifc data recovery info, this probably isn't a thread for you...
i learned the value of patience from an experience i had a few years ago when i ruined the MFT on a 120GB NTFS WinXP drive. i had just spent a weekend consolodating 'the stuff' from several 40GB drives onto my "huge-at-the-time" 120GB HDD (so later, i'd wipe the little ones, use for building 'new' systems). once i had finished the consolodation, i proceeded to use PQ Partition Magic / Boot Magic to create a "dual boot" setup for my 'master system'. When Boot Magic (a WinXP Utility) performs its actions (as i distantly recall), it goes through a re-boot process in which it writes certain data to the 'slave' drive-- essentially for making it part of the new dual-boot setup, thereby modifying the standalone properties of that slave drive (very naughty for it to do so w/out ample "this is going to muck w/ your slave drive!" warning signs) -- a modification which renders that 'slave drive' useless if not allowed to complete. as if the hand of Evil pushed my own, midway in the re-boot (at powerdown) i decided i didn't want that dual-boot afterall, so i halted the process. it was my own ignorant intervention which, by interrupting the PQ Boot / Boot Magic process, i had effectively 'hidden' all of that consolodated data under a totally whacked MBR-- and not even Partition Magic could undo what it had begun (naughty PM that it is!). so there i was w/ a ton of data on one drive, and several 'empty' smaller drives. it would be over a year before i finally found the time and patience to extract, piece by piece using Runtime Software's "Get Data Back"
-- an most EXCELLENT, superior tool in my opinion-- QUITE IMPRESSIVE in its ability to sniff out those folders while offering multiple possible 'images' it offers the user to preview. in action, it was very cool because some snapshots were paritially recognizeable by folder-name, while others were obviously "Not right", and only one stood out as the obvious, correct impression-- but the fact that i was able to try each 'recovery' w/ limitless indecision was really nice. at no time was anything written to that drive, so i had no fear of further data loss. i kept the Get.Data.Back "image" on my working Desktop because i would frequently dip into the 'damaged' drive for a file or two-- and 'recover' them individually, as needed (tedious, and time consuming, but effectively protected the data). had i the resources to 'dump' the entire Get Data Back image onto another drive, my problems would have been over-- as if nothing had happened, but i wasn't so financially endowed at the time. so, because i know how frustrating it can be to land in that kind of situation, i hope that maybe someone will pick up on this via Google if they need it. i say that because, of the entire process-- the most difficult part was finding Get Data Back would do precisely what i needed. i cringe at the countless hours spent looking at DOS floppy utilities (of which ACR "Media Tools Professional"
, i believe was head of its class-- very powerful, advanced skill required, more than i needed, and probably less friendly for that particular situation).
for the record, i've been using other resources since the drive discussed in this thread became unbootable. hence my gradual loss of concern for it [by 'it', meaning the 'stuff' on there, not the actual learning to solve the problem] in general-- it's why i've not done any major actions to the drive yet. short of any natural disaster, i'd rather not lose that data for laziness / not properly educating myself... so, it became a temporarily insurmountable task-- by which i hope to learn some real Linux "recovery" skills. this has been a good experience-- i would otherwise not have known the Forensic value of Knoppix, but since learning of it here-- i see it all over, described for precisely these uses (forensics, and data restoration).
funny how the learning takes place-- some of the best stuff learned outside of the classroom!