Windows boot not found, then a second HDD is unallocated and wrong capacity.

Bogabbagabba

Honorable
Jun 14, 2013
2
0
10,510
So,
came home the other day and my computer said that it couldn't boot windows,
I then checked bios to make sure my ssd hadn't died but all my HDD were being detected. i tried to repair windows install to no avail. I just decided to reinstall windows 7. I then relised one of my two internal 2T seagate drives was not showing up. In disk manager is is showing that it is not Initialized and unallocated with a capacity of 128.GB.

If i reboot the pc with this HDD plugged in windows takes about 10 minutes to boot up. Also when I use seatools this also takes about 10 minutes to scan disk. I cant used test disk because of the incorrect capacity shown.
Has this drive kicked the bucket and all data lost?

thanks, :(
 
Does SeaTools report the correct model number and serial number?

If you are using SeaTools for DOS, try to restore the full native capacity of your drive.

Can you see the contents of sector 0 with a disc editor, eg DMDE or HxD?

HxD - Freeware Hex Editor and Disk Editor:
http://mh-nexus.de/en/hxd/

DMDE - DM Disk Editor and Data Recovery Software:
http://dmde.com/
 

Bogabbagabba

Honorable
Jun 14, 2013
2
0
10,510
Seatools DOS does not show any of my drives, but seatools windows shows my three drives
ST2000DM001-1CH164 << HDD that works
ST2000DM001 << Drive that is faulty
if you try to do a test on the drive it just freezes.

DMDE just show error after i select the drive,
Disk#0 sector 0 (try 2): WinError 1117. The request could not be performed because of an I/O device error.

, so I turned off AHCI, hard drive showed up same as seatools windows, and errored on short test, long test and set capacity to max native.

error Afa8cd4a
 
It appears that the drive has an internal error, possibly a damaged firmware module, or maybe a bad head.

Depending on your skill and on your determination, you could access the drive's serial diagnostic port using an RS232 TTL interface adapter (< $10). This will produce an error report that my identify the problem, but it may not help you actually fix it. You may be lucky, though. If you choose this path, don't write anything to the drive. Just observe the error report. Some console commands are data destructive, and they are case sensitive.

See the "Seagate 7200.11 BSY bug and 0 LBA fix" links at the end of this article:
http://www.users.on.net/~fzabkar/HDD/HDD_Capacity_FAQ.html

You MUST NOT issue the following command:

m0,2,2,0,0,0,0,22

The above command only applies to 7200.11 models.