We are committed to providing fast, efficient, and affordable software solutions that set new standards in the software development industry.
  • Multi-pass imaging in R-Studio

R-Studio Technician versions can perform three types of object imaging:

  • Linear imaging (from the drive beginning to its end)
  • Runtime imaging (drive imaging in parallel with other drive operations)
  • Multi-pass imaging (performing drive imaging through several passes)

Their comparison chart can be reviewed in our article, Linear Imaging vs Runtime Imaging vs Multi-pass imaging.

Conventional drive imaging programs read a drive sequentially from the beginning to the end by sector blocks, or groups of consecutive drive sectors, that are read in one go. When they encounter areas with bad or slow sectors, they still try to read them entirely. That may lead to a complete loss of data from such blocks, or cause the program to switch to reading individual sectors - thus greatly reducing reading speed. Moreover, the program may eventually get stuck into areas while reading those bad sectors again and again, though such intensive reading from bad sectors may severely damage the drive surface, its heads, and other drive mechanics. As a result, the drive may die before the program starts reading data from the good parts of the drive.

Instead, a program using multi-pass imaging tries to extract data from drive's good parts first, ultimately leaving the bad and slow areas for later. Shortly thereafter, when it comes to a bad or slow sector block, it drops it and jumps to another area until it finds a block with no bad or slow sectors. It then continues reading data until it runs into another bad or slow block, where the process repeats. When the good areas have been read, the program starts reading data from slow and bad sectors. This approach maximizes the amount of data that can be recovered from a failing drive.

R-Studio can perform multi-pass imaging in its Technician and T80+ versions. Moreover, multi-pass imaging can be used together with special data recovery hardware like DeepSpar USB Stabilizer, which greatly increases chances for successful data recovery - even from drives in very poor hardware condition.

The multi-pass imaging implemented in R-Studio consists of four phases:

PHASE 1. Copying good data from the drive.
R-Studio reads data from the drive by sector blocks in this phase. The phase is performed in several steps.

Step 1. R-Studio reads data from the drive until it runs into a block with at least one bad sector. Then it skips a certain number of sectors and tries to read data at the new position. If it runs into another block with a bad sector, it increases the number of sectors to skip and repeats the process until it finds a block with no bad sectors. Then R-Studio continues reading the data until it runs into another block with a bad sector.
Phase 1. Front Edge Discovery
Click image to enlarge

R-Studio processes slow sectors in the same way.

When this step is completed, R-Studio has read data from most good areas and found the front blocks (edges) of bad and slow sector areas.

Step 2. R-Studio finds the rear edges of bad sector areas. It reads the skipped area from its rear, working backwards until it runs into a block with a bad sector. Then, R-Studio jumps to another bad sector area and the process is repeated until all bad sector areas have been processed.
Phase 1. Rear Edge Discovery
Click image to enlarge

When this step is completed, R-Studio has read data from some good areas and detected the front and rear blocks (or edges) of all bad sector areas.

In the next two steps, R-Studio processes slow sector areas without checking read speed against minimum I/O rate.

Step 3. R-Studio reads data from slow sector areas. It does this similarly to the process for bad sector areas.

It reads a slow sector area by blocks until it runs into a block with a bad sector. Then it skips a certain number of sectors, and so on, until it finds a block without bad sectors. It then continues reading data until it runs into another block with bad sector, and the process is repeated until all slow sector areas have been processed.
Phase 1. Slow area processing, front edge discovery
Click image to enlarge

Once this step is completed, R-Studio has effectively read data from all slow sector areas and detected the front blocks, or edges, of all bad sector areas within slow sector areas.

Step 4.. R-Studio finds the rear edges of bad sector areas in slow sector areas. It reads the skipped area from its end, working backwards until it runs into a block with a bad sector. Then, R-Studio jumps to another bad sector area and the process is going on until all bad sector areas have been processed.
Phase 1. Slow area processing, rear edge discovery
Click image to enlarge

Once this step is completed, R-Studio has read some new data from slow areas and detected the front and rear blocks, or edges, of all bad sector areas within slow sector areas.

Step 5.. R-Studio tries to read all skipped sector blocks. This is done without skipping bad sector blocks and checking read speed against minimum I/O rate.

When Phase 1 is completed, R-Studio has read most of the readable data and detected front and rear edges of all bad sector areas.

In the upcoming phases, R-Studio tries to read the rest of data and does that sector by sector rather than by sector blocks.

PHASE 2. Trimming.
R-Studio detects the front and rear sectors of bad sector areas in this phase. It reads the front block of a bad sector area by sectors until it runs into a bad sector. Then it reads the rear block of the bad sector area and works backwards until it runs into a bad sector.
Phase 2. Trimming
Click image to enlarge

When this phase is completed, R-Studio has read some new data from bad sector areas and detected the front and rear sectors of all bad sector areas.

PHASE 3. Scraping.
R-Studio tries to read data from bad sector areas sector by sector in this phase. There may be good or bad sectors in these areas.
Phase 3. Scraping
Click image to enlarge

When this phase is completed, R-Studio has read all readable data from the entire drive.

PHASE 4. Retrying (optional).
R-Studio tries to read data from bad sectors through several attempts in this phase.

You may control parameters of multi-pass imaging on the Bad sector processing tab of the Create Image dialog box.
Bad sector processing tab
Click image to enlarge

Image filename Specifies the name and path for the image file
Image type: Compressed image (R-Drive Image compatible): If this option is selected, R-Studio will create an image file which can be compressed, split into several parts, and password-protected. This image file is fully compatible with the images created by R-Drive Image, but incompatible with previous versions of R-Studio.
Byte-by-byte image: If this option is selected, R-Studio will create a simple exact copy of the object.
VMDK (VMware Virtual Machine Disk) image: If this option is selected, R-Studio will create an image of the VMware virtual disk type.
Drive sector map file A file with the sector map of the object to image. Optional for the RDI image type, mandatory for the byte-by-byte and VMDK image types.
Enable multi-pass image creation Turns multi-pass imaging on and off.
Perform reading in reverse order if possible Switches the direction of all phases/steps to reverse.
Minimum skip size Minimum size of drive area to skip when a bad sector is encountered.
Number of retries (Retrying phase) The number of read attempts in the Retrying phase.
Disable imaging phases Multi-imaging phases that can be skipped.

R-Studio shows multi-pass imaging progress and the statistics of multi-pass imaging during the process.
Multi-pass imaging progress
Click image to enlarge

Conclusions:
Multi-pass imaging is a very powerful tool for creating images of failing hard drives. In addition to extracting more good data from the drive, it also minimizes wear and tear of drive hardware - greatly reducing chances for the drive to completely fail during the process of its imaging. R-Studio implements in the most advanced way, ultimately providing a very flexible adjustment for all necessary imaging parameters.

Data Recovery Feedback
370 feedbacks
Rating: 4.8 / 5
I really love your R-Studio product, I am doing Data Recovery as a professional, I used RS since the early versions and I loved the product, as far as I can tell, R-Studio, especially the Tech Version (but including the standard) is one of the best and excellent tools for a pro to have in the arsenal of tools in a pro DR lab, especially combining with the specialized Data Recovery hardware providers like DeepSpar, and PC3000, the rest of `wannabees` out there are waste of time, strongly recommend
I lost more than 200K files from my NAS due to a mistake. I tried 3 different recovery solutions over the 4 TB raid disks, and all of them performed ok but to be honest none of them were able to Raw recover the files and rename them with meaningful names out of the Metadata like R-TT did, then I was able to sort again my files and pictures and kind of restore all of them.

R-TT may not be the easiest or most user-friendly solution, but the algorithm used for the renaming saved me THOUSAND of hours of opening ...
Just recovered my old ext4 partition with R-Studio after trying testdisk and R-Linux without success. That partition was overwritten by another ext4 partition and I was losing my hope until I tried R-Studio demo. It detected all my files and directories again!

Bought it and 100% recommend it for anyone with a similar issue.
Genuinely tried every free program available without luck of recovering a deleted file from months ago. Thinking my file was deleted forever and lose all hope I came across this website as a recommendation.

I was reluctant as it seemed pricey compared to other programs, but damn worth every penny. It managed to even find files I thought were wiped from existence.

Kudos to r-tools, thank you!
Why make incremental backups, when there is R-Studio?

I`m an IT professional who has worked from home for over a decade. Early on in my career, I configured an HP ProLiant Server (Raid 1+0) as a workstation that I would remote into from my laptop. As technology evolved, I began to use it only for email and as a config file repository.

A short while ago, one of the drives degraded, but the HP ProLiant Server (Raid 1+0) still functioned fine on the remaining drive. I was complacent and didn`t replace the ...