catastrophic failure

[Michael Zacherl]

On 09.11.2007 12:34 Uhr, Tony Scharf wrote:
> aye..of course, I spoke too soon.  many of the files, particularly the
> more recent ones, have been damaged.  Ableton cant read any of its
> files, though some of the .wav files are ok.  The directory structure
> seems to have been completely hosed too, so reconstructing the tracks
> is going to be probably as much work as just writing new ones...

sad to hear that!
sounds like the software didn't manage to locate all of the chained 
blocks of the respective files. So some of them may be filled with garbage.
Some time ago I recovered a lot of data from a friend's laptop 
(Windows/NTFS) - he did a similar thing, destroying the partition table 
and formatting part of it.
He is a translator so he was lucky since the data was relatively easy to 
   identify when seeing a dump.
The crazy thing was that that happened a couple of hours before the 
deadline of a big project. But we managed. He had to retype just a 
little bit of the text. The most work was sorting the blocks into the 
correct order.

I'd keep an image of the disk anyway, just in case a brilliant mind 
comes up with some working idea.
When this accident happened, did you disconnect the drive immediately?

If not I'm trying to figure why some blocks are gone.
the inode table etc. shouldn't harm.
What's the original type of filesystem you had on this particular disk?

   Michael.



-- 
nonconform? noiseconform: http://blauwurf.at/