you might try reinstalling a fresh OS onto a different drive, then mount your old partitions as data paratitions and attempt to fsck them with you correctly working OS. also explore the alternate superblock backups (man fsck?) to increase you chances. not sure if there are any other options out there. dont forget to check lost+found for file remnants especially if you have very important data to recover. At 07:37 PM 11/3/00 -0600, you wrote: >Hi, >I managed to screw up my hard drive to the point where it won't boot >anymore--fsck locks up when it tries to fix it, before that started >happening, it was corrupted already due to a bad ./configure script (not >written by me, btw) that managed to lock up my computer to the point of >making 'ps' not even work. > >In debugging that configure script I stupidly forced several hard reboots on >my computer (no real classy way to shut down a computer that can't even >figure out the pids of its processes) and now I can't get at the data on the >hard drive. Unfortunately, I had my honor's project on there (a large final >project I need to have finished to graduate from school next semester.) > >So, generally, is there some way to get at this data if the inodes are >corrupted? Without spending mucho bucks that I don't have on a data >recovery team? > >Thanks, >Dave > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org >For additional commands, e-mail: tclug-list-help at mn-linux.org >