lost+found files... this is certainly no help!

The files in lost+found are analogous to files chkdsk will produce in c:\ when it does what fsck did.  Both tools try to make sense of data on disk when the structure built around that data to manage it as a filesystem is corrupt.  Bits of what appear to be contiguous data are given a new file handle so the user can interact with that data in the hopes that some of it can be recovered.

It is pretty rare, I think, that this is practical.  I've had some success rebuilding things like text files (more common in UNIX than Windows) since I can open them, read them, and maybe know for each fragment how it fits overall.  Binary or encrypted files there is little to no chance of manually reintegrating the fragments fsck has left you into the original file.  

There may be tools out there to help with this but this situation happens so infrequently to me that I have never been willing to spend money on them.  Instead, you will likely have to recover materials from backup or live without if there is no backup.

Thanks, turnbulld, for providing to me absolutely no guidance.  I'm really not intersted in your opinion.  I'm looking for strategy here.... so....  let's try a different approach.

I can see the files in the /mnt/MOUNT0 directory.  The files that I'm concerned with are virtual hard disk files - rather large.  Perhaps you could walk me through (step-by-step) the process of ascertaining these files from the other "noise", for example:

"Dear, Pantz.  Since the files you are looking for are virtual disks and are more than likely rather large, run the following command to determine the respective size of each file".

That would be a great start.

Then maybe give me a heads up about how to actually verify that the virtual disk is intact.

Do I have to earn your points for you?

Referred to me as 'mightiness'.

Solution made sense...  correctly re-iterated to me that I am simply "f'd".

:(