Intensive read

Intensive read is a very useful function for head problem or bad sector condition. Here is a typical case about this function.

Yesterday we got a patient drive with strong bad sectors, and the customer need the database file, it’s very important for them.

We connected this drive to DC and with shadow disk, and could access to the file successfully:

Then try to recover those files:

A moment later, all those files retrieved success:

But when we open them with Winhex, we found one file is full of 4040 bits, what means the retrieved was failed:

Compared with other file:

The customer needs all the files….even one is broken, all those files are invalid (they are working together).

Then we open the intensive read function in shadow disk control page:

Then recover this file again:

Listen to the sound, it apparently different with former. After this file has been retrieved, open it with Winhex again:

Now we can see this broken file was retrieve success.

PS: Intensive Read function may have a bad effect to head. So we should recover all the data which we can recover without this function, then open it at last.

Bookmark

• July 7, 2009 -- Depop Head in F> repair for Seagate Drive
• June 12, 2009 -- Head instability problem
• July 31, 2009 -- Hidden LBA function introduce
• July 31, 2009 -- A case about image in DC
• July 28, 2009 -- How to check the bad sectors on SA