recovering lost+found files

Raul A. Gallegos raul at
Sat Dec 7 16:14:08 EST 2002

Adam Myrow said the following on Sat, Dec 07, 2002 at 12:18:34PM -0600:
> Your best shot is to use the "file" command on the suspect files.  This
> may tell you what they are.  The "strings" command is also handy since it
> tries to display printable strings in binary files.  With any luck, you
> will be able to identify the critical files and restore/rename them and
> they won't be corrupt.  However, those types of crashes are pretty nasty.

Actually, to be honest I'm not sure why I said a power failure.  It was 
a power supply problem.  I think it's that anyway, I keep getting 
interrupt error problems and the drive sounds like it's powering 
cycling.  I can hear it sounding like when your first boot up the 
machine.  I also have a zip drive which is louder and it helped me hear 
it in the first place.  I removed that hdd and put in anther one in case 
it was the drive itself but it did the same thing.  A friend suggested 
it is most likely the power supply.

In any case I do have a ups which does come in very handy for sure.  
Sorry for the confusing message.  I figured I'd have to use strings or 
something to get those files back.  The problem is I'm not sure of the 
structure of the dpkg binaries to know what all goes where.  I might 
just look at my other Debian box and compare.


Ever wonder if alternate worlds exist besides our own?  Join the 
parallel-worlds mailing list to discuss this, and similar topics.  click
Raul A. Gallegos

More information about the Speakup mailing list