PC-3000 Flash SSD Edition, version 4.0

1. SSD data recovery algorithms

Indilinx — IDX110M00-LC Solid State Drive recovery method has been implemented.
JMicron- JMF601/602 Solid State Drives recovery method has been implemented.
Now all analysis algorithms have ECC autodetection and correction of all data critical at analysis algorithm implementation.

2. ECC (Error Correction Codes) used in SSD have been added

ECC correction mode has been modified. Operations are carried out much quicker, including operations for the most difficult cases. Much more ECC types are now supported, special correction codes for SSD that have high power correction have been added.

Speed and safety have been optimized in ECC autodetection mode.

3. Support of SSD with capacity up to 2 Tb

All versions after the version 4.0 of PC-3000 Flash SSD Edition support creation of task with the total capacity up to 2 Tb. The task retains its compactness and speed of operations. All tasks from the previous versions are supported as well.

4. Driver x64

PC-3000 Flash SSD Edition has now a driver for 64-bit OS. This driver has obligatory digital signature and is installed correctly at Win7 x64, Vista x64. You can obtain this driver at your personal update box, or at PC-3000 Flash SSD Edition installation CD.

5. PC-3000 Flash SSD Edition manual has been published

All official users of PC-3000 Flash SSD Edition can download the updated manual for PC-3000 Flash SSD Edition from their personal update box in Manuals/PC3000Flash_part1.pdf subcatalogue.

It gives brief description how to work on PC-3000 Flash SSD Edition and general data about working with memory microchips. Describtion of adapters for various types of memory chips and recommendations how to use them are provided.

6. Complete description on data recovery from SSD

Complete description on data recovery from SSD has become the indispensable part of PC-3000 Flash SSD Edition solution starting from the version 4.0. This manual has the complete, systematized step-by-step description of operations necessary to recover data from the certain models of Solid State drives. It is visualized by multiple illustrations and recommendations for each model. New models of SSD and the descriptions of working with them are constantly being added to this manual.

The latest version of the complete manual can be downloaded from the personal update box in Manuals/PC3000Flash_part2.pdf subfolder.

7. What's new in interface

When you read memory microchip, autoverification is switched off by default because the modern ECCs (Error Correction Codes) have high correction power, moreover time is saved at reading. If there are many irrecoverable errors, you can set mark autoverification flag.
When «ECC autodetection» operation is executed successfully, you'll see the automatic offer to make correction. You can launch data correction later from the menu.
If you launch ECC autodetection and then correction on one of the memory chips, correction will be applied to all memory chips. In the same way, when supported ECC type is detected on one of line results in «Transformation graph», correction will be done to all results on the line.
We have added the method of preliminary preparation «Join by blocks N sources» that helps to integrate the selected number of results into result according to the indicated block size. This mode is primarily intended for working with SSD.
When downloading external files, «Read only» flag is off, which helps the automatic methods to correct important data.
When you select one of lines in left-hand part of the interface in «service information» mode, now you can add the corresponding sector into search results and comments to it.

8. Virtual translator for built image

This mode is designed to recover the data from built image with broken integrity. The origin of this problem could be serious damage of important structures or the usage of some common algorithm that did not fit for 100%. This situation is similar to hard disk translator damage, when the data are split into several pieces with correct data, but with broken integrity between these pieces (i.e. excess or no data is within the breakpoints).

The physical meaning of translator corruption is the following: the drive has the data, the data is available and not damaged, but data parts are shifted.

That mode is used independently for each analysis result, received after data processing for this task. This mode table exists on a screen permanently. When some result is selected, the data from shift tables are loaded automatically. The mode is available only when the analysis result is selected. On "Chips" and "Results of preparation" this table is not active.

The main visual mode for translator recovery is modified Explorer mode. Explorer mode is used to detect shifts and check the result after the map was corrected. This helps quickly find the results after correction. For example, when corrected shift is added, this mode shows you complete content of some directory.

The main idea of this method is consistent composition of shifts table. Certain knowledge about logical file system structures (FAT and NTFS) should be used.

WARNING! When FAT file system partition recovery is processed, Folder validity control should not been used. It is possible, on a first translator generation step, the necessary directory could be located on a wrong place during the shifts.

Zoom

Modified visual Explorer mode. Translator recovery Explorer mode.Zoom

The list of tools, modes and methods used for drive translator recovery:

Table of shifts and its context window (located in the right part of the screen)
Modified "HEX" tab with interface designed for shifts adding, changing and searching the shift size for current selected sector.
Shift search mode. That mode is available from the button in HEX tab. It lets you find GREP sectors near the sector you are looking for that is displayed in HEX tab and fits demanded criteria (files or folders with a certain type, for example) and add new shift point.
GREP Search mode. That mode could be used for similar cases as "Shift search mode" is used. However , when this mode is launched more that once, it is necessary to clean the results list. It can happen new shift points, that were not considered by previous search results, were added.

Shift table.

Shift table has context menu, that has next commands:

Add shift point (Ctrl+Insert)
Delete (Ctrl+Del)
Refresh
Compress table
Legend
Calculate LBA
Clear (works with a range of sectors, similar to "compress table" method)
Save to file (shift table is exported to a text file).

Add shift point. This method is designed for manual shift point input.

Add shift point
When shift point is added or deleted in manual mode (from shift points context menu) or when shift point table is cleared, explorer object tree will not be automatically updated.

Compress the table. When explorer needs to read certain sector, but shift table has records, software is searching for the record with smaller or equal LBA number. And it considers this very shift at reading. For example, when you will try to read LBA = 1000 and there is a record in shift table from LBA = 999 + 5 sectors, software will read 1005 sector.

If the table has more than 2 records with the same shift, it is possible to leave only one from the edge. It will not affect the actions Explorer will perform.

But you should know, the more records shift table has, the less wrong record influence (with incorrect shift). It is reccommended to compress table only when shifts search and adding is completed.

Compress table method (same as clear table method) works with a range of sectors that is set in a startup dialog window (check the picture bellow).The shift table is one for whole storage device, and sometimes it is necessary to compress (or clean) the part of that table, that is relative to certain range of sectors, without affecting the other ones. For example, if there are two partitions, and one shift table is built for the first partition it it necessary to compress table for the second partition. In this case we set the range of the second partition, to avoid compressing first partition table we don't need to compress.

Compression range set window

Legend. When adding points to shift table new concept - information validity - is used.

Authentic shifts are the shifts, that were get with automated methods for objects, that have indication about their certain location or their location is known from other true data (for example, boot sector position is known from MBR slots, and FAT partition folders has certain cluster number). If shift points are added , nearest search table points are searched (with the biggest and smallest LBA number) and next situations are possible in this case:

These points are not found or the found points have another shift, so the added point validity was not changed.
Valid point is added, but one of the found points has the same shift size and its validity is smaller. In this case this point validity parameter is set to valid.
Point with small validity is added, but one of the found points has same shift size and the validity parameter. In this case validity parameter of the added point is set to valid.
Point with small validity is added, and one of the found points does not have validity parameter, but has the same shift. In this case the validities of both points are summarized (correspondingly, validity parameter of both points is changed).

Calculate LBA. The principle of Explorer shifts point LBA Calculation for a certain sector with shifts table is described below within "Compress table" method. Sometimes it is necessary to calculate the shift for some interim sector. This method is used in order not to look through the whole table of shifts. User has to enter necessary LBA number and press OK button to see the result.

Input LBA window

Calculation result window

9. Fixed errors

Memory leaks error have been fixed.

Go up

Go Home