Gus Wirth wrote: > James G. Sack (jim) wrote: > [snip] >> rbw sent me some data that revealed the presence of EZ-Disk rather than >> Ontrack DriveManager. >> >> The remap63 trick says to ignore 63 sectors (per the DriveManager >> trickery), which produces nonsense if you _aren't_ using DriveManager! >> >> There is a remap option (as opposed to remap63) which says to skip _one_ >> sector, which is supposed to be the way EZ-Disk does its magic. >> >> AFAIK, Rodney hasn't gotten a chance yet to go back and look with the >> 1-sector offset hda=remap. > > I wonder if the EZ-Drive programs work the same across all versions. I > found that there was up to a version 9 supplied by Western Digital. If > the way it works changed at some version level, maybe the hda=remap > trick doesn't work any more. The last change I can see for this was > around 1996, but Western Digital currently supplies something called > Data Lifeguard. I haven't grabbed it yet to see if it's the same thing. > >> Recovery tools can do irreversible things. Best to: >> a) have a backup .. the old recipe of working on a bit-copied disk is >> appropriate for serious recovery (or forensic) work. >> b) don't use a tool without understanding what it's going to do <heh>. > > Yep. Depending on the cost of the data, if it's work more than $50 then > just buy a bigger disk, pop this disk and the new disk in a machine, dd > everything from the old disk to the new one, then only play with the new > disk. > > Also a correction to my previous post. It looks like PRecover isn't even > out in alpha yet so that link can be ignored. I just saw it pop up when > doing a search on Sourceforge. >
Another thing to worry about is that the dmesg output that accused the disk of having an EZD-modified mbr may be mistaken. That's why I asked rbw for dd-captured data to look at to get a little better understanding of the situation. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
