1tb Caviar Black, unusable

I really shouldn’t have put this off for this long, but I just got a new 2tb HD and I really want to get this 1tb Caviar Black to work.

When I first bought it, it worked fine, I filled it with about 500gb and then it just stops working. The bios sees the drive and lists the incorrect size as 400kb, but whenever I try to access it it would tell me the drive needed to be formatted. Ok, I put a lot of valuable work files on there that I still needed so I tried using testdisk. It said the HD didn’t have a valid NTFS boot sector. I tried using testdisk to set it, but it still didn’t work. Here’s the log file:

"Tue Dec 21 20:38:04 2010
Command line: TestDisk

TestDisk 6.11.3, Data Recovery Utility, May 2009
Christophe GRENIER grenier@cgsecurity.org
http://www.cgsecurity.org
OS: Windows XP SP3
Compiler: GCC 4.3, Cygwin 1005.25 - May  6 2009 20:35:43
ext2fs lib: 1.41.4, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: 20080501
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=251000193024
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=320072933376
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdc)=320072933376
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdd)=1000203804160
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive0)=251000193024
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive1)=320072933376
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive2)=320072933376
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\PhysicalDrive3)=1000203804160
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\C:)=320062063104
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\D:)=251000160768
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\E:)=320062063104
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\.\F:)=1000202273280
filewin32_getfilesize(\.\G:) GetFileSize err Incorrect function.

filewin32_setfilepointer(\.\G:) SetFilePointer err Incorrect function.

Warning: can’t get size for \.\G:
file_pread(4,1,buffer,490235759(486344/15/63)) lseek err Invalid argument
file_pread(5,1,buffer,625153409(38913/254/63)) lseek err Invalid argument
file_pread(6,1,buffer,625153409(38913/254/63)) lseek err Invalid argument
file_pread(7,1,buffer,1953523151(1938018/15/63)) lseek err Invalid argument
Hard disk list
Disk /dev/sda - 251 GB / 233 GiB - CHS 486344 16 63, sector size=512 - Maxtor 6L250R0
Disk /dev/sdb - 320 GB / 298 GiB - CHS 38913 255 63, sector size=512 - MAXTOR STM3320620AS
Disk /dev/sdc - 320 GB / 298 GiB - CHS 38913 255 63, sector size=512 - MAXTOR STM3320620AS
Disk /dev/sdd - 1000 GB / 931 GiB - CHS 1938018 16 63, sector size=512 - WDC WD1001FAES-22W7A0

Partition table type (auto): Intel
Disk /dev/sdd - 1000 GB / 931 GiB - WDC WD1001FAES-22W7A0
Partition table type: Intel
New geometry
Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121602 255 63 sector_size=512
New options :
 Dump : No
 Cylinder boundary : Yes
 Allow partial last cylinder : No
 Expert mode : No

Interface Advanced
Geometry from i386 MBR: head=16 sector=63
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
get_geometry_from_list_part_aux head=255 nbr=1
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=32 nbr=2
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=128 nbr=2
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=1
 1 * HPFS - NTFS              0   1  1 121601   0 63 1953520065 [Marmot4]
     NTFS, 1000 GB / 931 GiB

ntfs_boot_sector
 1 * HPFS - NTFS              0   1  1 121601   0 63 1953520065 [Marmot4]
     NTFS, 1000 GB / 931 GiB
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
filesystem size           1953520002 1
sectors_per_cluster       8 0
mft_lcn                   786432 0
mftmirr_lcn               122095000 0
clusters_per_mft_record   -10 0
clusters_per_index_record 1 0
Boot sector
Status: OK

Backup boot sector
Status: Bad

Sectors are not identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
copy original boot sector over backup boot

ntfs_boot_sector
 1 * HPFS - NTFS              0   1  1 121601   0 63 1953520065 [Marmot4]
     NTFS, 1000 GB / 931 GiB
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
filesystem size           1953520002
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               122095000
clusters_per_mft_record   -10
clusters_per_index_record 1
Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.
repair_MFT
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
file_pread(7,4096,buffer,976760063(60800/127/63)) read err: Invalid request code
file_pread(7,1,buffer,976761435(60800/149/49)) read err: Invalid request code
Can’t read NTFS MFT mirror.
Can’t read NTFS MFT mirror.

ntfs_boot_sector
 1 * HPFS - NTFS              0   1  1 121601   0 63 1953520065 [Marmot4]
     NTFS, 1000 GB / 931 GiB
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
filesystem size           1953520002
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               122095000
clusters_per_mft_record   -10
clusters_per_index_record 1
Boot sector
Status: OK

Backup boot sector
Status: OK

Sectors are identical.

A valid NTFS Boot sector must be present in order to access
any data; even if the partition is not bootable.

Analyse Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121602 255 63
Geometry from i386 MBR: head=16 sector=63
NTFS at 0/1/1
Info: size boot_sector 1953520002, partition 1953520065
get_geometry_from_list_part_aux head=255 nbr=1
get_geometry_from_list_part_aux head=8 nbr=2
get_geometry_from_list_part_aux head=16 nbr=2
get_geometry_from_list_part_aux head=32 nbr=2
get_geometry_from_list_part_aux head=64 nbr=2
get_geometry_from_list_part_aux head=128 nbr=2
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=1
Current partition structure:
 1 * HPFS - NTFS              0   1  1 121601   0 63 1953520065 [Marmot4]
Ask the user for vista mode
Allow partial last cylinder : No
search_vista_part: 0

search_part()
Disk /dev/sdd - 1000 GB / 931 GiB - CHS 121602 255 63
NTFS at 0/1/1
filesystem size           1953520002
sectors_per_cluster       8
mft_lcn                   786432
mftmirr_lcn               122095000
clusters_per_mft_record   -10
clusters_per_index_record 1
     HPFS - NTFS              0   1  1 121600 254 63 1953520002 [Marmot4]
     NTFS, 1000 GB / 931 GiB
file_pread(7,8,buffer,1953523135(121601/48/47)) lseek err Invalid argument
file_pread(7,1,buffer,1953523135(121601/48/47)) lseek err Invalid argument
get_geometry_from_list_part_aux head=255 nbr=2
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2

Results
   * HPFS - NTFS              0   1  1 121600 254 63 1953520002 [Marmot4]
     NTFS, 1000 GB / 931 GiB

interface_write()
 1 * HPFS - NTFS              0   1  1 121600 254 63 1953520002 [Marmot4]
write!

write_mbr_i386: starting…
write_all_log_i386: starting…
No extended partition
You will have to reboot for the change to take effect.

TestDisk exited normally."

I don’t seem to have any luck with WD. The very first WD drive I bought about 8 years ago died within 2 days. I called up tech support and they told me my cpu was too fast and I’d have to underclock it which made me lose all respect for WD at the time. This drive was my second try at WD since everyone is praising them and well, this post is proof that I’m not having any luck it was very fast and silent when it did work though. I don’t know why I did it, but the new 2tb drive is a WD since that’s all Best Buy had on sale, I have three maxtor drives in here that have run fine for years, I hope the 2tb isn’t part of my typical WD disaster experience.

Was your 1TB drive ever attached to a Gigabyte motherboard with an Xpress Recovery BIOS? If so, then a bug in the BIOS may have truncated your drive, although the usual result is a 32MB capacity, not 400KB.

To restore the drive’s original factory capacity, try HDAT2 or HDD Capacity Restore Tool:

http://www.hdat2.com/
http://hddguru.com/software/2007.07.20-HDD-Capacity-Restore-Tool

See this thread for an explanation and solution:
http://forum.hddguru.com/lost-partition-hitachi-1gb-hdt721010sla360-t15662.html

Yes, the mobo it was on is a Gigabyte with the XPress recovery. I will try those programs and hopefully get my drive back.

My fear now is that I think I have the latest bios, so the same thing might happen to the new 2TB drive that will be the main Win7 drive. That’s not good at all. :confused:

I havene’t seen the bug for myself, but AIUI, once a backup copy of the BIOS has been written to the drive, the BIOS will not touch the drive again. Therefore you should be safe. In any case, I believe only the boot drive is affected.