Accidently Write MBR Code to WD Essential 2TB

How to use TestDisk to recover lost partition
Post Reply
Message
Author
attraction88
Posts: 4
Joined: 17 Sep 2013, 12:33

Accidently Write MBR Code to WD Essential 2TB

#1 Post by attraction88 » 17 Sep 2013, 12:53

Hi,

i need a little help here as im lost
I have an external Western Digital 2TB hard disk for storing backup files. After my external enclosure fails which screw up my partitions, i took out the hard disk and mount it on a 3rd party enclosure. I accidentally write MBR using Test disk on a Window XP. After Rebooting, each tme i plug into my Window XP, it automatically restarts the window. So, i used another computer wihich is Window 7, which it can detect. Now, the computer detects as 7 partitions, 3 which is unallocated, and 4 is fine, but still cant appear on my computer.

I have run the analyze for quick scan and deeper scan, but nothing came out.

all i wanted in to recover some photo that i have collected over the years. i tried to run PhotoRec, and so far all the files has unknows file extensions.

Sponsored links

attraction88
Posts: 4
Joined: 17 Sep 2013, 12:33

Re: Accidently Write MBR Code to WD Essential 2TB

#2 Post by attraction88 » 17 Sep 2013, 16:32

Attached is the pictures that i have taken after the scan.
Attachments
IMG_1099.JPG
this is the screen after the deeper search
IMG_1099.JPG (202.84 KiB) Viewed 1542 times
IMG_1098.JPG
partitions found after the scan
IMG_1098.JPG (231.65 KiB) Viewed 1542 times

User avatar
cgrenier
Site Admin
Posts: 3458
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Accidently Write MBR Code to WD Essential 2TB

#3 Post by cgrenier » 19 Sep 2013, 07:54

If the actual partition table content triggers a bug in Windows, you can run TestDisk and choose Delete. Don't select the wrong disk!
What is the result after Deeper Scan ?

attraction88
Posts: 4
Joined: 17 Sep 2013, 12:33

Re: Accidently Write MBR Code to WD Essential 2TB

#4 Post by attraction88 » 20 Sep 2013, 03:26

This is the results of the quick scan and deeper scan. Can you please help to identify what seems to be the problem here.



Sun Feb 12 19:11:59 2006
Command line: TestDisk

TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Windows 7 (7601) SP1
Compiler: GCC 4.7, Cygwin 1007.17
Compilation date: 2013-07-30T14:08:52
ext2fs lib: 1.42.2, 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)=80026361856
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(/dev/sdb)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive0)=80026361856
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\PhysicalDrive1)=2000398934016
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\C:)=31347179520
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\D:)=48562020864
filewin32_getfilesize(\\.\E:) GetFileSize err Incorrect function.

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

Warning: can't get size for \\.\E:
disk_get_size_win32 IOCTL_DISK_GET_LENGTH_INFO(\\.\F:)=104857600
Hard disk list
Disk /dev/sda - 80 GB / 74 GiB - CHS 9729 255 63, sector size=512 - Hitachi HTS541680J9SA00, S/N:2020202020204253323234304753414a57374531, FW:SB2OC7BP
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63, sector size=512 - WDC WD20 EARS-00MVWB0, S/N:152D20337A0C

Partition table type (auto): Intel
Disk /dev/sdb - 2000 GB / 1863 GiB - WDC WD20 EARS-00MVWB0
Partition table type: Intel

Analyse Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63
Geometry from i386 MBR: head=255 sector=63
check_part_i386 1 type A8: no test
check_part_i386 2 type EC: no test
check_part_i386 3 type 2C: no test
Current partition structure:
1 P Darwin UFS 35774 39 56 53413 34 48 283370213
2 P Sys=EC 102092 162 2 155337 80 10 855375768
3 P Sys=2C 171272 248 50 264358 175 30 1495421972
No partition is bootable

search_part()
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63
BAD_RS LBA=1780175524 13210907
file_pread(5,3,buffer,1780175524(378160/38/27)) lseek err Invalid argument
file_pread(5,1,buffer,1780175524(378160/38/27)) lseek err Invalid argument
check_FAT: can't read FAT boot sector
check_part_i386 failed for partition type 06
FAT16 >32M 378160 38 27 574591 220 17 3155675472
This partition ends after the disk limits. (start=1780175524, size=3155675472, end=640883699, disk end=3907029168)
file_pread(5,2,buffer,3907031040(243201/110/46)) lseek err Invalid argument
file_pread(5,1,buffer,3907031040(243201/110/46)) lseek err Invalid argument
file_pread(5,1,buffer,3907031039(243201/110/45)) lseek err Invalid argument
file_pread(5,14,buffer,3907031041(243201/110/47)) lseek err Invalid argument
file_pread(5,3,buffer,3907031055(243201/110/61)) lseek err Invalid argument
file_pread(5,3,buffer,3907031102(243201/111/45)) lseek err Invalid argument
file_pread(5,8,buffer,3907031118(243201/111/61)) lseek err Invalid argument
file_pread(5,11,buffer,3907031165(243201/112/45)) lseek err Invalid argument
file_pread(5,2,buffer,3907033087(243201/143/14)) lseek err Invalid argument
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (2000 GB / 1863 GiB) seems too small! (< 4726 GB / 4401 GiB)
The following partition can't be recovered:
FAT16 >32M 378160 38 27 574591 220 17 3155675472

Results

interface_write()

No partition found or selected for recovery

search_part()
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63
BAD_RS LBA=1780175524 13210907
file_pread(5,3,buffer,1780175524(378160/38/27)) lseek err Invalid argument
file_pread(5,1,buffer,1780175524(378160/38/27)) lseek err Invalid argument
check_FAT: can't read FAT boot sector
check_part_i386 failed for partition type 06
FAT16 >32M 378160 38 27 574591 220 17 3155675472
This partition ends after the disk limits. (start=1780175524, size=3155675472, end=640883699, disk end=3907029168)
file_pread(5,2,buffer,3907031040(243201/110/46)) lseek err Invalid argument
file_pread(5,1,buffer,3907031040(243201/110/46)) lseek err Invalid argument
file_pread(5,1,buffer,3907031039(243201/110/45)) lseek err Invalid argument
file_pread(5,14,buffer,3907031041(243201/110/47)) lseek err Invalid argument
file_pread(5,3,buffer,3907031055(243201/110/61)) lseek err Invalid argument
file_pread(5,3,buffer,3907031102(243201/111/45)) lseek err Invalid argument
file_pread(5,8,buffer,3907031118(243201/111/61)) lseek err Invalid argument
file_pread(5,11,buffer,3907031165(243201/112/45)) lseek err Invalid argument
file_pread(5,2,buffer,3907033087(243201/143/14)) lseek err Invalid argument
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63
Check the harddisk size: HD jumpers settings, BIOS detection...
The harddisk (2000 GB / 1863 GiB) seems too small! (< 4726 GB / 4401 GiB)
The following partition can't be recovered:
FAT16 >32M 378160 38 27 574591 220 17 3155675472

Results

interface_write()

No partition found or selected for recovery


These are the pictures after the scan
Attachments
Untitled2.jpg
after the quick scan and deeper scan, are are no partitions.
Untitled2.jpg (57.96 KiB) Viewed 1514 times
Untitled1.jpg
deeper scan
Untitled1.jpg (76.03 KiB) Viewed 1514 times
Untitled.jpg
first quick scan
Untitled.jpg (71.56 KiB) Viewed 1514 times

User avatar
cgrenier
Site Admin
Posts: 3458
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Accidently Write MBR Code to WD Essential 2TB

#5 Post by cgrenier » 25 Sep 2013, 18:02

What extensions do you got with PhotoRec ?

attraction88
Posts: 4
Joined: 17 Sep 2013, 12:33

Re: Accidently Write MBR Code to WD Essential 2TB

#6 Post by attraction88 » 28 Sep 2013, 10:33

Sorry, but what extension do you mean? Im kinda lost..

Thanks

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests