4TB disk, boot & backup boot sector bad, disksize wrong

Using TestDisk to repair the filesystem
Post Reply
Message
Author
PeterJ
Posts: 3
Joined: 30 Jun 2014, 17:19

4TB disk, boot & backup boot sector bad, disksize wrong

#1 Post by PeterJ » 30 Jun 2014, 17:31

Hi all

my 4TB Western Digital Mybook suddenly failed, could be a powersurge or whatever, but it just quit, all files gone, dick not reconizable in windows. The LED that usually blinks intermidiate during I/O stayed on permanently and the disk kept spinning rather than power don as it should after a short period of non-activity.

The harddisk is a TGB HGST, label says LBA 7.814.037.1568 Sectors CHS: 16383/16/63

Both bootsectors are reported as bad by TestDisk, and the disksize is reported as 1801 GB.
I did a scan and one attempt to rebuild the boot sector from the MFT, to no avail.

Can anyone advise me on how to proceed to save the files on the disk?
Thanks in advance for any comments on this issue.


This is the TestDisk log:



Thu Jun 26 08:32:34 2014
Command line: TestDisk

TestDisk 7.0-WIP, Data Recovery Utility, June 2014
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 4.8, MinGW 3.11
Compilation date: Jun 21 2014 09:12:33
ext2fs lib: none, ntfs lib: 10:0:0, reiserfs lib: none, ewf lib: 20120504
Failed to startup volume: Invalid argument.
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=120034123776
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=1801763774464
filewin32_getfilesize(\\.\PhysicalDrive2) GetFileSize err Incorrect function.


filewin32_setfilepointer(\\.\PhysicalDrive2) SetFilePointer err Incorrect function.


Warning: can't get size for \\.\PhysicalDrive2
filewin32_getfilesize(\\.\PhysicalDrive3) GetFileSize err Incorrect function.


filewin32_setfilepointer(\\.\PhysicalDrive3) SetFilePointer err Incorrect function.


Warning: can't get size for \\.\PhysicalDrive3
filewin32_getfilesize(\\.\PhysicalDrive4) GetFileSize err Incorrect function.


filewin32_setfilepointer(\\.\PhysicalDrive4) SetFilePointer err Incorrect function.


Warning: can't get size for \\.\PhysicalDrive4
filewin32_getfilesize(\\.\PhysicalDrive5) GetFileSize err Incorrect function.


filewin32_setfilepointer(\\.\PhysicalDrive5) SetFilePointer err Incorrect function.


Warning: can't get size for \\.\PhysicalDrive5
filewin32_getfilesize(\\.\PhysicalDrive6) GetFileSize err Incorrect function.


filewin32_setfilepointer(\\.\PhysicalDrive6) SetFilePointer err Incorrect function.


Warning: can't get size for \\.\PhysicalDrive6
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=119926685696
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=0
Warning: can't get size for \\.\D:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\E:)=0
Warning: can't get size for \\.\E:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\G:)=0
Warning: can't get size for \\.\G:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\H:)=0
Warning: can't get size for \\.\H:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\I:)=0
Warning: can't get size for \\.\I:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\O:)=1801760800768
Hard disk list
Disk \\.\PhysicalDrive0 - 120 GB / 111 GiB - CHS 15505 240 63, sector size=512
Disk \\.\PhysicalDrive1 - 1801 GB / 1678 GiB - CHS 219051 255 63, sector size=512
Drive C: - 119 GB / 111 GiB - CHS 15491 240 63, sector size=512
Drive O: - 1801 GB / 1678 GiB - CHS 219051 255 63, sector size=512

Partition table type default to None
Drive O: - 1801 GB / 1678 GiB
Partition table type: None

Interface Advanced
P Unknown 0 0 1 219051 154 47 3519064064
Change partition type:
P NTFS 0 0 1 219051 154 47 3519064064

P NTFS 0 0 1 219051 154 47 3519064064
Can't open filesystem. Filesystem seems damaged.

ntfs_boot_sector
P NTFS 0 0 1 219051 154 47 3519064064
filesystem size 1 1008085506613244435
sectors_per_cluster 0 221
mft_lcn 0 2962804005
mftmirr_lcn 0 86204290
clusters_per_mft_record 0 40
clusters_per_index_record 0 -1
Boot sector
Status: Bad

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.
rebuild_NTFS_BS
Failed to rebuild NTFS boot sector.

ntfs_boot_sector
P NTFS 0 0 1 219051 154 47 3519064064
filesystem size 1 1008085506613244435
sectors_per_cluster 0 221
mft_lcn 0 2962804005
mftmirr_lcn 0 86204290
clusters_per_mft_record 0 40
clusters_per_index_record 0 -1
Boot sector
Status: Bad

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.
rebuild_NTFS_BS
Failed to rebuild NTFS boot sector.

ntfs_boot_sector
P NTFS 0 0 1 219051 154 47 3519064064
filesystem size 1 1008085506613244435
sectors_per_cluster 0 221
mft_lcn 0 2962804005
mftmirr_lcn 0 86204290
clusters_per_mft_record 0 40
clusters_per_index_record 0 -1
Boot sector
Status: Bad

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.

Sponsored links

User avatar
Fiona
Posts: 2836
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: 4TB disk, boot & backup boot sector bad, disksize wrong

#2 Post by Fiona » 30 Jun 2014, 17:53

Did you use testdisk 64bit?
In case, can you test testdisk 32bit instead?
Please select Disk instead of Drive to get better results.

Fiona

PeterJ
Posts: 3
Joined: 30 Jun 2014, 17:19

Re: 4TB disk, boot & backup boot sector bad, disksize wrong

#3 Post by PeterJ » 01 Jul 2014, 04:46

Using Disk I get this info:

Disk \\.\PhysicalDrive1 - 1801 GB / 1678 GiB - CHS219051 255 63

The harddisk (1801 GB / 1678 GiB) sems too small! << 4244GG / 3952 GiB)
Check the harddisk size: HD jumpers settings, BIOS detection...

The following partition can't be recovered:
Partition Start End Size in sectors
> FAT12 355273 136 516028 60 52 2582524318

It's a 4TB disk with NTSF
Is it possible / advisable to rewrite the size info on the disk, such as number of sectors, stop-start?

User avatar
Fiona
Posts: 2836
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: 4TB disk, boot & backup boot sector bad, disksize wrong

#4 Post by Fiona » 01 Jul 2014, 06:30

Your disk size must be recognized correctly.
Otherwise you can't recover your partition.
How is your disk listed in your disk management console?
Changing any values under geometry like cylinder, heads sectors, testdisk would scan this area and quit it with read errors, because they're not physically available.
Until yet it isn't advisable to change or modify anything to your disk.

PC/Intel-MBR only supports partitions up to 2.2 TB.
Partition size bigger than 2.2 TB should be GPT.

You should diagnose your disk using Data Lifeguard Diagnostic from WD first.
I've seen some cases that the firmware of the disk hung and displayed the wrong size.
There are some tools available to set it back.
Example:
http://forum.cgsecurity.org/phpBB3/mism ... n-t32.html
Until yet, you shouldn't modify anything to your disk.
It could increase damage.
Check the WD-homepage for firmware updates?

Did you already check your enclosure too?
In some cases WD external disks have had a build in hardware encryption chip.
Info:
http://forum.cgsecurity.org/phpBB3/post ... pted#p1058

Fiona

PeterJ
Posts: 3
Joined: 30 Jun 2014, 17:19

Re: 4TB disk, boot & backup boot sector bad, disksize wrong

#5 Post by PeterJ » 03 Jul 2014, 20:41

Fiona,

thank you for your feedback so far.
The main problem seems to be an incorrect disk size.
My first aim is to make sure the disk is regognized as a 4TB disk.

I corrected the CHS values (they must be 16383 cylinders, 16 heads, 63 sectors) which I set with TestDisk. But then the reported disksize is still not correct.
But is it also possible to set the LBA? The label on the disk says 7.184.037.168

Regards, Peter

User avatar
Fiona
Posts: 2836
Joined: 18 Feb 2012, 17:19
Location: Ludwigsburg/Stuttgart - Germany

Re: 4TB disk, boot & backup boot sector bad, disksize wrong

#6 Post by Fiona » 04 Jul 2014, 08:35

The disk controller of your motherboard provides for example 48bit LBA that a disk size bigger than 137 GB is supported.
That's why the values on your disk differ to the values given from your BIOS and OS.
If TestDisk displays the CHS values as followed, the amount of your cylinders, 255 heads and 63 sectors, it would be absolute normal and has nothing to do with your disk size.
HDD's today often provide only the LBA- and not the CHS values anymore.
So there is nothing to do.
If you can exclude any other reason for your problem, you can have a look into this topic:
http://forum.cgsecurity.org/phpBB3/mism ... n-t32.html
In some cases diagnosis tools from the manufacturer have an option to set LBA back.
Similar called SetMAX.
Hdat2 offers 2 options.
Something similar like:
SetMax and delete HPA (Host Protected Area).
But before you do something like that, it's recommended to build in your disk internally or to test another enclosure.
Even if your disk is hardware encryptet.
The only intention is to diagnose your disk size and you should not write, change nor modify anything to your disk.
If your disk size would match, you'd know the your enclosure is the culprit.
Usage of firmware repairer can void warranty.
That's why be careful.

Fiona

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest