This topic has been closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
2012-02-25 01:13 PM
2012-03-02 12:53 AM
2012-03-02 01:20 AM
2012-03-02 05:19 AM
2012-03-02 06:36 AM
2012-03-02 07:34 AM
You got that right, mate
ExoZed wrote: So the only thing I'd add to your point about asking others, is that anyone in my position should probably not wait until they fail - before you do ANYTHING post your problem and see what people recommend.
2012-04-02 05:06 AM
Jack™ wrote: It seems your data recovery service did exactly what you did in step 3 to recover your data, except they most probably did not use a laptop and a USB-SATA adaptor.
Still, all well that ends well…
2012-04-07 02:54 PM
Hi Tom, good to hear from an "old-time" pro knowing his tools of trade. Of course, cloning the disk data before working on the data is basic. Read my post #8 referring to users that explained the tools available for this. Then remains the issue of the swapped bytes on a SFS HD. This has been explained by Azurlake's post #11. So it seems that you used a good old hex editor and then interleaved the data-parts to transform the data into FAT/NTFS type of data, after which any recovery software will be able to get back the files in RAW-mode. Wouldn't it be much easier to use the recovery tool that the owners of the San File System (SFS), Dataplow, have made available for free to everybody? It's called SFSExtract and you don't have to be a data recovery expert in order to use it.:cool: Read ukspamuk's post #3 for a short but precise report how to get about it....
Tierra wrote: .......We really do use a combination of hardware forensic cloning to get a true image from unstable hard drives, in-house code to extract most of the file system and a good old hex editor to get us the rest of the way.