Recovery Guides: step-by-step iRecover operations:
Checking Disk Health.

The situation:
  • A disk is showing problems when reading data, the disk's physical status needs to be checked.

What we need before we begin:

  • A PC that runs Windows and has the disk attached; the disk must be connected directly (no USB/FireWire).
  • iRecover installed. You can use the trial version for this particular procedure.

What we assume before you begin:

  • You have a working knowledge of Windows.

Some thoughts before we get going:

When recovering data from a disk, the disk's physical status must be good. If the disk shows read problems or other mechanical issues that prevent you from accessing the disk, the recovery will be impaired. This is especially true if you are recovering data from a broken RAID0 or RAID5. If you run into a disk that has read problems, and you need the data on that disk, you should:
- check the disk to find out what the problem is,
- decide how to proceed: clone the disk, create an image file of the disk, or (if the problems are very small) go ahead with the recovery.
The RAID Recovery Guide has more details on how to deal with this type of situation.

Here we go:
The Beginning: Start iRecover, you'll be greeted by the Main Screen.

Select "Data Recovery for Windows and Linux".

Please note that checking the disk's health status can be done with the trial version.

Select A Disk: Here you will select the disk you wish to check. Right-click the disk and select "S.M.A.R.T. information", as indicated.
SMART Status: You will now see the SMART status for the selected disk. The attributes that are of interest to us are high-lighted in this screen shot. If any of these attributes are not 0 (look in the "RAW" column), the disk has problems. If "Current Pending Sector Count" is not 0, the problem is even more severe and the disk is getting worse as we speak.

If you need help interpreting the numbers here, simply select "Save to File" and post the resulting file with your support request in our support forum.
Find details on how to request support here.

(*) - the more observant among you will notice that we've used VirtualBox to create this guide. The reason for this is simple: it allows us to create a situation that is custom-made for the guide. So, while perhaps not all too realistic, it helps us get the point across. I'm sure you understand.
Please note that the disks used in the guide are very small, again for demonstration purposes. The larger the disks, the longer some of the steps will take. Anywhere from a few hours to a few days is possible, so be patient. Keep an eye on the process to make sure that there is progress. And remember, you can contact us for any questions you may have.

http://www.diydatarecovery.nl