|
The behavior you are seeing—a 500 GB drive being detected as 3.86 GB (or sometimes 0 GB or a different, very small capacity)—is a classic symptom of a Seagate "LBA 0" or "Capacity Reset" issue, specifically common in the Barracuda 7200.12 family (like your ST3500418AS). This happens because the drive's firmware has entered an error state where it cannot correctly read the Translator (the table that maps logical sectors to physical locations on the platters). When this table fails to load, the drive often defaults to a "generic" or factory-default state, showing an incorrect, minimal capacity. Why this happens on your 7200.12 1. Translator Corruption: The drive's internal map is damaged. Even though the data is still on the platters, the drive doesn't know where to look for it. 2. Firmware Bug: The 7200.12 series is infamous for this specific firmware hang. 3. SA (Service Area) Read Error: The drive is likely failing to read the system modules that contain the "Max LBA" (Logical Block Addressing) information. How to handle this using MRT Since you are using the MRT Data Recovery Tool, you have a significant advantage. Do not reinitialize or format the drive in Disk Management, as that could overwrite the remaining configuration data. 1. Check the Terminal Log: Open the Seagate utility in MRT and look at the terminal output during power-on. Does it show the drive model and serial number correctly, or does it report a generic name (like ST_M13FQ or Seagate BSY)? 2. "Edit Capacity" / "Update Max LBA": MRT has specific functions in the Seagate menu to "Modify Capacity" or "Reset Translator." o Crucial: Before running these, ensure you have a full ROM backup. o If you can reach the F3 T> prompt, use the command to check the current reported capacity: i4,1,22. 3. Regenerate/Reload Translator: In the MRT Seagate utility, look for "Translator Regeneration." This process instructs the drive to scan the physical platters and rebuild the mapping table from scratch. o Warning: This process can take time. If the drive has bad heads, it will hang during the scan. A Note on Hardware The 7200.12 family is now quite old (2010-era). If the drive is showing an incorrect capacity, there is a high probability that the Read/Write heads are beginning to degrade. Proceed with caution: • If the data is critical: If the drive makes any clicking, ticking, or scratching sounds, turn it off immediately. A head stack with weak "fly height" will scratch the platters if you force it to scan and rebuild the translator. • Isolate the issue: Are you seeing any "Read Error" or "UNC" (Uncorrectable) errors in the MRT Data Explorer when you try to create a map of the drive?
|