Data Recovery and Disk Utilities Forum @R-TT

Sorry for the long delay, looks like you recover files from an HFS+ disk, and R-Studio cannot save their forks correctly. Most likely, the files themselves are recovered correctly. See more in R-Studio's on-line help: Data Recovery on HFS/HFS+ File System.

So the questions:
1 What is the file system of the disk you're saving files to?
and
2 What is the files system of your computer?

У нас есть и русский форум. Он рабочий.

During recovering all files on drive - zillions of "The operaion was failed. (error #1001), why is that happening ? The file names seem to be ok!
Is it the bug? The free version could not reveal such problem so I've bought a license for $80 and got that. What should I do?

---------
Recovering Resource of /Volumes/WDP/Новая папка/$$$Folder387615/test_udp.pyc failed. The operation was failed. (error #1001)
Recovering Resource of /Volumes/WDP/Новая папка/$$$Folder389425/cs-dired-ref.tex failed. The operation was failed. (error #1001)
Recovering Resource of /Volumes/WDP/Новая папка/$$$Folder390434/viper-macs.elc failed. The operation was failed. (error #1001)
Recovering Resource of /Volumes/WDP/Новая папка/$$$Folder390667/nnimap.elc failed. The operation was failed. (error #1001)
Recovering Resource of /Volumes/WDP/Новая папка/$$$Folder391812/texnfo-upd.elc failed. The operation was failed. (error #1001)
Recovering Resource of /Volumes/WDP/Новая папка/$$$Folder404741/test_float.py failed. The operation was failed. (error #1001)
---------
Seems to me no .dng file was recovered - the only type i needed to recover

Hi, is there an fix for this error 1001. I have the same problem and post is over 2 years old?
This is not good. If i knew this i would NOT buy your software.

So what now then? End of using R-studio? or you going to do something about it after this old post 2 years????

A customer that is not happy.

We'll check that issue.

Ok I figured out the issue, it is the hard links / symlinks, R-Studio doesn't recover those right. Is there away around this?

Ok, after reformating the hard drive (in which I am recovering the files to) to HFS and then rescanning the hard drive to recover and exporting those files out, I still get the same results. In comparing the folder / file structure between the hard drive being recovered (Which again can be read in Linux without issues) and the recovered files there are again about 5.5 GB and 270,000 files that are missing in the recovery. Although This time I did not get any Error #1001 error codes.

Now what?

It is build 1.0.241

Ok here is what I am going to do. The first attempt was to recover the data to a drive formatted in NTFS as it is just easier in Linux, but now I am rescanning the drive and I am going to recover to a hard drive formatted in HFS with journaling tourned off so linux can write to it. I will see if that makes any difference.

Will up date and let you know hopefully later today.

tombuhn wrote:I am pretty sure I was, it shows a release date of Nov 4th , 2011 on your site and I purchased the software after that date so I am pretty sure I am, I can check later. Was this a known issue for an earlier version?

No, but we made a serous overhaul of our HFS module. I'll contact our developers with this case.

I am pretty sure I was, it shows a release date of Nov 4th , 2011 on your site and I purchased the software after that date so I am pretty sure I am, I can check later. Was this a known issue for an earlier version?

Did you use the latest version?