Call us: 10am – 6pm ET

888 540-2010, 416 833-3501

Damaged Drive Capabilites

Atola TaskForce has an algorithm-based imaging engine developed based on our decades-long experience in data recovery. This imaging process enables data acquisition even from physically damaged hard drives, while protecting the media from further deterioration.

To handle damaged drives in the most gentle and thorough way Atola TaskForce includes these features:

Imaging damaged drive

Imaging damaged drive

Multi-pass imaging uses large blocks with short timeouts on the first few passes, scheduling reads inside slow areas for later and then using the smallest block size on the last pass when fewer sectors are left to be read. This technique helps achieve imaging speeds of 500 MB/sec in good areas of the drive, while approaching bad areas in the most gentle way possible and reaching unbeatable overall speed of disk imaging.

Block sizes and timeouts are adjustable. The default settings of the passes are optimized based on our decades-long experience in data recovery market to fit most problematic drives. Therefore, it is advisable to follow them, unless a particular drive requires specific settings.

Reverse direction. With this function selected, TaskForce will approach skipped areas of the drive from the other side on any selected pass. This way TaskForce can get more data from a drive before entering a damaged zone, which needs to be concentrated on during the following passes.

Disable read look-ahead. Most contemporary hard drives have read look-ahead functionality, which makes the drive read more blocks sequentially than requested by software. In good drives, this functionality helps the drive operate faster by reading more data and caching it. But with bad drives, read look-ahead leads to bad areas being addressed more often, which slows down the process and may lead to a complete freeze of the drive. In such cases, disabling read look-ahead option is advisable.

Calculate hash during imaging. With bad drives, the fewer times you read data on them, the longer they will last, which can be critical for bringing a criminal to justice in the court of law. It is therefore advisable that when imaging a damaged drive, hash calculation is done simultaneously with imaging: this way TaskForce only reads the data on the drive once.

When dealing with a damaged drive, we strongly recommend using segmented hashing because this method supports multi-pass imaging and handling of bad sectors, and provides better resiliency against data corruption.

If the diagnostics report shows that a part of drive’s head stack is damaged, TaskForce provides the possibility select good heads only to be imaged during an imaging session. This function helps avoid causing damaged to the healthy parts of the drive by disabling the damaged head.

Automated handling of freezing drive. Often the drive is unable to read data from the damaged sectors and goes into a long lasting retry mode before it gives up on a particular sector and return an error. To avoid causing further damage to the data on the drive and long waiting periods, TaskForce issues a reset command whenever a drive attempts to read a block of sectors longer than allowed by the pre-configured timeout, and continues imaging from the next planned block on the drive. If retry mode last despite two reset commands, TaskForce will perform power cycle command by forcibly cutting power to the drive for 5 seconds. And then will continue imaging from the next planned block. If the second power cycle does not help either, imaging will be terminated.

The numbers of reset and power cycle commands are adjustable. The default settings, though, are deemed optimal: they are set based on our decades-long experience and balance the need of data retrieving with the risk of further data loss.