 |
| Advertisement |
Data Recovery from Seagate 7200.11 with LBA=0 problem
Data Recovery from Seagate 7200.11 with LBA=0 problem
In 7200.11 series, LBA=0 is a common problem, for most cases, we could click “Repair LBA=0” button to fix this problem. But sometimes this button does not work. In this case I will show you the reason and another solution.
General solution:
Now we got a special case, the customer said that the drive could be ready status but LBA=0, when he tried to fix this problem by our program, it shows “completed” but the problem still remains, as the following pictures:
(The drive could be ready status but LBA=0)
Then we choose to click “Repair LBA=0” button, a moment later, it shows “completed”. But notice the status; it was not “Ready” but shows “Error”:
Then we tried to click the HDD parameter column, if the problem has been solved, we could have the access to the right LBA value. But in this case, the problem still exists:
The reason:
Generally speaking, the LBA=0 problem was caused by the verify code error. The verify code exists in all firmware modules and the main reason which cause the LBA=0 problem is verify code error in P/G list, or SMART table.
In our program, the “Repair LBA=0” is working to fix the verify error by reading the firmware modules from disk cache first, then check the verify codes and fix them, so if the module has some problems which make it impossible to read the firmware successfully, the repair function is invalid, just like the above mentioned case.
Alternative solution:
There is another solution which needs not to read the firmware but fix the verify code directly.
First, launch the CMD mode and press [Ctrl + Z] on the keyboard to get a “F3 T>” prompt.
Part One
Now, if your BIOS recognize disk but there is 0 LBA, all you need is to hit this command:
F3 T>m0,2,2,0,0,0,0,22 then press [Enter]
IMPORTANT, don’t turn HDD power off, wait about 30 sec to 2 minutes until it finished!!!
Then you may see something like this.
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8 Max retries Wr = 00, Max Rd retries = 00, Max T-ECC Level = 14, Max certify Rewrite retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful – Elapsed Time 0 mins 05 secs User Partition Successful Format – Elapsed Time 0 mins 05 secs
Switch the HDD power OFF and turn it ON (power reset), users should have the drive back to normal status.
Part Two
If your HDD 7200.11 can’t be recognized by the computer BIOS, moreover, in the CMD mode, no matter what command you used, there is the same feedback:
LED:000000CC FAddr:0025BF67
Ctrl + Z
F3 T>
LED:000000CC FAddr:0025BF67
Your drive is always busy!
Power off the HDD, unscrews the PCB; connect the stand-alone PCB to the console as if it was an entire hard drive; power on the PCB and launch the CMD mode:
Press [Ctrl + Z] on the keyboard to get a “F3 T>” prompt.
Enter “/2” under the “F3 T>” prompt, this will change the “F3 T>” prompt to be “F3 2>” prompt;
F3 2>
Enter “Z” under the “F3 2>” prompt
F3 2>Z
Spin Down Complete
Elapsed Time 0.138 sec
F3 2>
Now you can put the PCB back on the HPA container.
Enter “U” under the “F3 2>” prompt
F3 2>U
Spin Up Complete
Elapsed Time 7.242 sec
F3 2>
Enter “/1” under the “F3 2>” prompt
F3 2>/1
This change the prompt from “F3 2>” to “F3 1>”
Enter “N1” under the “F3 1>” prompt
F3 1>N1
This will perform an erase towards the HDD S.M.A.R.T.
Then press [Ctrl + Z] on the keyboard to go back to the “F3 T>” prompt
Enter “i4,1,22” under the “F3 T>” prompt
F3 T>i4,1,22
This will perform an erase towards the G-list.
Switch the HDD power OFF and turn it ON (power reset), users should have the drive back to normal status.
So we get into CMD mode and type the command as the first case above:
But a moment later, it showed this error info:
For this error condition, it may be caused by firmware module damage or bad sectors on the SA!
So we try to erase the SMART and G-list first:
Both the erase commands can be carried out successfully, and then we tried to use another command which is more “powerful”:
Unfortunately, error info still existed:
Now we know the problem was bad sectors on SA. In this condition, the drive could not be resolved at this time. But in all 7200.11 LBA=0 problem, more than 60% we could repair just by click “repair LBA=0” button, the other 30% could be fixed by the m0,2,2,,,,,22 command and the powerful m0,6,22,,,,,22 command. Only less than 10% are caused by bad sectors on SA which can’t be fixed at the moment.
In 7200.11 series, LBA=0 is a common problem, for most cases, we could click “Repair LBA=0” button to fix this problem. But sometimes this button does not work. In this case I will show you the reason and another solution.
General solution:
Now we got a special case, the customer said that the drive could be ready status but LBA=0, when he tried to fix this problem by our program, it shows “completed” but the problem still remains, as the following pictures:
(The drive could be ready status but LBA=0)
Then we choose to click “Repair LBA=0” button, a moment later, it shows “completed”. But notice the status; it was not “Ready” but shows “Error”:
Then we tried to click the HDD parameter column, if the problem has been solved, we could have the access to the right LBA value. But in this case, the problem still exists:
The reason:
Generally speaking, the LBA=0 problem was caused by the verify code error. The verify code exists in all firmware modules and the main reason which cause the LBA=0 problem is verify code error in P/G list, or SMART table.
In our program, the “Repair LBA=0” is working to fix the verify error by reading the firmware modules from disk cache first, then check the verify codes and fix them, so if the module has some problems which make it impossible to read the firmware successfully, the repair function is invalid, just like the above mentioned case.
Alternative solution:
There is another solution which needs not to read the firmware but fix the verify code directly.
First, launch the CMD mode and press [Ctrl + Z] on the keyboard to get a “F3 T>” prompt.
Part One
Now, if your BIOS recognize disk but there is 0 LBA, all you need is to hit this command:
F3 T>m0,2,2,0,0,0,0,22 then press [Enter]
IMPORTANT, don’t turn HDD power off, wait about 30 sec to 2 minutes until it finished!!!
Then you may see something like this.
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8 Max retries Wr = 00, Max Rd retries = 00, Max T-ECC Level = 14, Max certify Rewrite retries = 00C8
User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful – Elapsed Time 0 mins 05 secs User Partition Successful Format – Elapsed Time 0 mins 05 secs
Switch the HDD power OFF and turn it ON (power reset), users should have the drive back to normal status.
Part Two
If your HDD 7200.11 can’t be recognized by the computer BIOS, moreover, in the CMD mode, no matter what command you used, there is the same feedback:
LED:000000CC FAddr:0025BF67
Ctrl + Z
F3 T>
LED:000000CC FAddr:0025BF67
Your drive is always busy!
Power off the HDD, unscrews the PCB; connect the stand-alone PCB to the console as if it was an entire hard drive; power on the PCB and launch the CMD mode:
Press [Ctrl + Z] on the keyboard to get a “F3 T>” prompt.
Enter “/2” under the “F3 T>” prompt, this will change the “F3 T>” prompt to be “F3 2>” prompt;
F3 2>
Enter “Z” under the “F3 2>” prompt
F3 2>Z
Spin Down Complete
Elapsed Time 0.138 sec
F3 2>
Now you can put the PCB back on the HPA container.
Enter “U” under the “F3 2>” prompt
F3 2>U
Spin Up Complete
Elapsed Time 7.242 sec
F3 2>
Enter “/1” under the “F3 2>” prompt
F3 2>/1
This change the prompt from “F3 2>” to “F3 1>”
Enter “N1” under the “F3 1>” prompt
F3 1>N1
This will perform an erase towards the HDD S.M.A.R.T.
Then press [Ctrl + Z] on the keyboard to go back to the “F3 T>” prompt
Enter “i4,1,22” under the “F3 T>” prompt
F3 T>i4,1,22
This will perform an erase towards the G-list.
Switch the HDD power OFF and turn it ON (power reset), users should have the drive back to normal status.
So we get into CMD mode and type the command as the first case above:
But a moment later, it showed this error info:
For this error condition, it may be caused by firmware module damage or bad sectors on the SA!
So we try to erase the SMART and G-list first:
Both the erase commands can be carried out successfully, and then we tried to use another command which is more “powerful”:
Unfortunately, error info still existed:
Now we know the problem was bad sectors on SA. In this condition, the drive could not be resolved at this time. But in all 7200.11 LBA=0 problem, more than 60% we could repair just by click “repair LBA=0” button, the other 30% could be fixed by the m0,2,2,,,,,22 command and the powerful m0,6,22,,,,,22 command. Only less than 10% are caused by bad sectors on SA which can’t be fixed at the moment.
Comments are closed.
0 comments: