Data Recovery Story, Data Recovery Case Study,Data Recovery Tools
Today, I encountered the typical malfunction for 7200.9 and 7200.10. The following is terminal log for that malfunction:
Interface task reset
1024k x 16 SDRAM
TONKA40 – 1_Disk M-31 11-15-05 15:49
Buzz – Head Mask FFFF – Switch to full int.
Spin Ready
(P)PATA Reset
Failed sys sect. write
Read Ver Retrys
Read Ver Retrys
Read Ver Retrys
Read Ver Retrys
Read Ver Failure!
Failed sys sect. write
Unable To Load Overlay 01|000A Continued…
Posted in Seagate Data Recovery.
– July 31, 2009
Today I encountered a case of 7200.11, in which the drive can be detected, but LBA is 0. Repair LBA=0 doesn’t work.
So I try the command “m,2,2,,,,,22″, but still it doesn’t work either. Continued…
Posted in Data Recovery Story.
– July 31, 2009
Today, I encounter a case of Hitachi 5425, which is locked. The article is to tell you step by step to unlock the drive. Continued…
Posted in Hitachi Data Recovery.
– July 31, 2009
This article is to tell users how to install driver for HD Doctor. First, you need to connect usb cable to console box and then run the main program. Then a wizard will tell you step by step. Continued…
Posted in Data Recovery Story.
– July 31, 2009
Today, a client told me that his Hitachi Doctor can’t work normally. The console will beep twice at power on and it automatically switch power off then. According to my experience, I know it is problem of cables or power supply. Continued…
Posted in Data Recovery Story.
– July 31, 2009
Today I encounter a case of B540, which can be detected but can’t be zerofilled by HD Doctor for Seagate. First, you should check whether the drive is read-only or not. Find a reserved sector to randomly write a byte and see whether the byte can be saved or not. Continued…
Posted in Seagate Data Recovery.
– July 31, 2009
Today, I encounter a head problem case for 5416 family. The drive can’t be detected and firmware can’t be accessed. There are two possibilities: NVRAM corruption and head damage. So how judge the problem, please read the following words. Continued…
Posted in Hitachi Data Recovery.
– July 31, 2009
Today, I encounter a strange case for Hitachi 5416 family. The drive can’t be detected and firmware can’t be accessed when boot from SA-A. However, after boot from SA-C, firmware can be accessed and no key modules are corrupted by firmware check. Continued…
Posted in Hitachi Data Recovery.
– July 31, 2009
Firmware problem is the most common problem in both HDD repair and data recovery. The general principle for firmware repair is to find the donor firmware and upload the corrupted firmware. But this is what the most bore and important problem is: how and where to find the donor firmware?
Now, depending on SA emulation tech on DC, we could avoid this terrible problem for Hitachi drive. There is a typical case about SA emulation.
Yesterday we got a patient drive with a typical firmware problem symbol, which after load from HDD, nothing shows except the error status:
Then load from file, we could access the service area and check the corrupt modules:
Now we connected the drive to Data Compass and show how SA emulation worked.
When the drive connected to DC, we can see the error status and couldn’t access to data area:
Then back to the Control page, choose the right series in “HITACHI HDD LOAD”:
A moment later, we can see the status go to “ready” status, and now we could access the data area:
Posted in Data Compass, Data Recovery Story.
– July 29, 2009
Today,I helped a client get back the data from a 7200.9 drive.In fact,it’s a common fault that usually occurs.So I want to share the repair experience with you.
That is the info in the terminal when we powered off and on the drive.From the picture,it looks like a CELOG problem.Generally,this problem is caused by corrupted Log modules and can be easily and well solved by CE Log Repair of HD Doctor for Seagate.You can get the detail from this link.
After took a CELOG REPAIR,we could see such info in the terminal.Then we try N50,,22 and found that drive can’t get into level 50 properly.As far as I know,that is because there are many errors in this drive and just click the CELOG REPAIR button is not enough to solve this problem.However,it will cause the drive can’t go back to the level 50 after CELOG REPAIR.
So we decided to solve this problem by commands.
1st.Press Ctrl+R to load the cert table module.
2nd.input N4E,,22 and click Enter,press Ctrl+L to initialize the selfscan.
3rd.Input N50,,22 after the selfscan finished.
Power off and on the drive,the info get normal and the error message don’t exist this time.
Then go to the Sector View Tab and we found the sector can be accessed properly.Just connect the drive to the Data Compass to get back the data.
Posted in Data Recovery Story.
– July 29, 2009
