Page 1 of 1

Another drive bites the dust?

Posted: 20 Oct 2014, 01:01
by ribrob
Hi there,

I've been trying to recover an external WD 3TB drive (without about 400GB of data on it) without success.

The drive was working fine and then suddenly when plugged in it would power down within a minute.

I ended up removing the disk from it's enclosure and sticking it in a caddy to get at the files.

Whilst the disk spins up again, the damage the disk no longer reads.

I'm pretty sure it was a FAT32 disk (rather than reformatted for Mac - it was being used in OS X Mavericks).

When it's plugged into either OS X or Windows now, the OS in question just wants to initialise it.

I've left if being scanned by TestDisk for a good few days on normal and then advanced scan, but no joy so far.

Please see the disk scan log below (Disk \\.\PhysicalDrive1 - 3000 GB / 2794 GiB).

Ten years of music, family photos and retro gaming collection at risk, which ironically i was gathering into one place to back up to the cloud to avoid exactly this happening.

I'm entirely out of my depth here - anyone got any tips on what i can do?

Rob



Mon Oct 13 22:18:13 2014
Command line: TestDisk

TestDisk 7.0-WIP, Data Recovery Utility, October 2014
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows WorkStation 6.2.9200
Compiler: GCC 4.7, Cygwin 1007.25
Compilation date: 2014-10-05T21:22:25
ext2fs lib: 1.42.8, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: 20120504
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sda)=68719476736
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=3000592982016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=68719476736
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=3000592982016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=68350377984
filewin32_getfilesize(\\.\D:) GetFileSize err Incorrect function.

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

Warning: can't get size for \\.\D:
Hard disk list
Disk /dev/sda - 68 GB / 64 GiB - CHS 8354 255 63, sector size=512 - Windows 8.1-0 SSD, S/N:E93PM5R8PJ9MSB3FQJQX, FW:F.31VK24
Disk /dev/sdb - 3000 GB / 2794 GiB - CHS 45600 255 63, sector size=4096 - WDC WD30 EZRS-00J99B0, S/N:FEDCBA9876543210, FW:80.0
Disk \\.\PhysicalDrive1 - 3000 GB / 2794 GiB - CHS 45600 255 63, sector size=4096 - WDC WD30 EZRS-00J99B0, S/N:FEDCBA9876543210, FW:80.0

Partition table type default to EFI GPT
Disk \\.\PhysicalDrive1 - 3000 GB / 2794 GiB - WDC WD30 EZRS-00J99B0
Partition table type: EFI GPT

Analyse Disk \\.\PhysicalDrive1 - 3000 GB / 2794 GiB - CHS 45600 255 63
Bad GPT partition, invalid signature.
Trying alternate GPT
Bad GPT partition, invalid signature.
Current partition structure:
Bad GPT partition, invalid signature.
Trying alternate GPT
Bad GPT partition, invalid signature.

search_part()
Disk \\.\PhysicalDrive1 - 3000 GB / 2794 GiB - CHS 45600 255 63

LVM magic value at 36794/34/35
file_win32_pread(324,2,buffer,732566645(45600/41/63)) read err: read after end of file
file_win32_pread(324,2,buffer,732566645(45600/41/63)) read err: read after end of file

Results

interface_write()

No partition found or selected for recovery

search_part()
Disk \\.\PhysicalDrive1 - 3000 GB / 2794 GiB - CHS 45600 255 63
Search for partition aborted

Results
Can't open backup.log file: No such file or directory
interface_load

interface_write()

No partition found or selected for recovery
simulate write!
Partition table type default to EFI GPT
Disk \\.\PhysicalDrive1 - 3000 GB / 2794 GiB - WDC WD30 EZRS-00J99B0
Partition table type: EFI GPT

Interface Advanced
Bad GPT partition, invalid signature.
Trying alternate GPT
Bad GPT partition, invalid signature.

Interface Advanced
Bad GPT partition, invalid signature.
Trying alternate GPT
Bad GPT partition, invalid signature.

TestDisk exited normally.

Re: Another drive bites the dust?

Posted: 20 Oct 2014, 17:07
by cgrenier
The log file shows no partition table and no partition found... That's not very good. If you can afford it, you may want to contact a data recovery company. Otherwise you may try PhotoRec to recover your data but there will be a lot to sort!