Today,i repaired a 7200.9 drive on Teamviewer from our client.The drive keeps busy in the HD doctor.The client told me that the drive never fall down and there is no clicking sound when power on it,but it can’t be detected in the BIOS.From these description,we could know that the pcb and head should be ok.That’s must be a firmware problem for this drive.
Then we go to the cmd mode and get these info in the terminal.Obviously,the drive is in f-level now and there is something wrong with the Application Code.
That means we got problem in reading the track that stored this module.Maybe there are some physical bad sectors on this track.
The way to repair this problem is trying to load the app module into the buffer,and then the drive can read it normally from the memory but not the track.
First we should find a donor drive with same model number,firmware version and same first 3 digitals of the SN.Then backup the 7# app module in order to boot the drive.
Second turn to the Load Management Tab and select the family of the drive manually.
The third step is turning to the Other Opearion Tab and click the button “drive to F”.
After it finished,turn to the Boot Management Tab and select where you stored the donor firmware in the left panel.Then click CE Log Repair to load the app module.This procedure will take you about 1 or 2 minutes.So please don’t cut off the power during this period.
Check the data after it finished.Since the data can be accessed,you can remove the data cable from the HD doctor console and connect it to the Data Compass with power on.Then you can get back all the data by DCEXP.
0 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.