Due to a power outage at the datacenter this server is hosted at we 'lost' a partition.
Using testdisk I am able to see the partition and list the files, but I had some concerns before 'pulling the trigger' so to speak.
Here is what testdisk shows initially:
Code: Select all
TestDisk 7.0-WIP, Data Recovery Utility, January 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
Disk /dev/sda - 898 GB / 836 GiB - CHS 1036956 47 36
Current partition structure:
Partition Start End Size in sectors
1 P Dell Utility 0 1 28 47 22 9 80262
Warning: Bad ending sector (CHS and LBA don't match)
2 * HPFS - NTFS 48 19 21 3766 36 8 6291456
3 P HPFS - NTFS 3766 36 9 177288 46 36 293599612
4 E extended LBA 53344 39 5 1036954 43 28 1664268288
Space conflict between the following two partitions
3 P HPFS - NTFS 3766 36 9 177288 46 36 293599612
4 E extended LBA 53344 39 5 1036954 43 28 1664268288
test_logical:
Partition sector doesn't have the endmark 0xAA55
*=Primary bootable P=Primary L=Logical E=Extended D=Deleted
>[Quick Search] [ Backup ]
Attempting to do a quick search produces the following screen:
Code: Select all
TestDisk 7.0-WIP, Data Recovery Utility, January 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
Disk /dev/sda - 898 GB / 836 GiB - CHS 1036956 47 36
Warning: the current number of heads per cylinder is 47
but the correct value may be 255.
You can use the Geometry menu to change this value.
It's something to try if
- some partitions are not found by TestDisk
- or the partition table can not be written because partitions overlaps.
Code: Select all
Disk /dev/sda - 898 GB / 836 GiB - CHS 1036956 47 36
Partition Start End Size in sectors
>D FAT16 >32M 0 1 28 47 22 9 80262 [DellUtility]
D HPFS - NTFS 48 19 21 3766 36 8 6291456
D HPFS - NTFS 3766 36 9 177289 46 12 293601280
D HPFS - NTFS 177289 46 13 1036953 33 32 1454551040
Partition 1: Primary (dell utility)
Partition 2: Bootable
Partition 3: Primary
Partition 4: Extended
Inside of windows diskmgmt.msc reports this:
Partition 1: OEM partition (primary?)
Partition 2: Primary (recovery)
Partition 3: Bootable (windows)
Partition 4: "free space", outlined in green, looks like an extended partition
I would assume that the partitions should be all primary except the 3rd partition, which should be primary/bootable.
But if that is the case why does the initial testdisk output have the 2nd (recovery) partition as bootable and the 3rd (windows) partition simply as primary?
Trying to resolve this problem remotely, would be a very long drive to the datacenter. Any help or insight would be very appreciated.