

- #Change access to writeable using wxhexeditor iso#
- #Change access to writeable using wxhexeditor windows#
Since they are 3TB, I believe they are not MBR drives and are GPT (GUID Partition Table).Both are 3TB in size and have the same exact geometry/attributes.The two drives are exactly the same make and model, Seagate BackupPlus 3TB.
#Change access to writeable using wxhexeditor windows#
I know there are Windows based disk cloning tools, but I don't have much experience with any of them and rather stick with a bootable USB based solution.Ĭould anyone recommend a method to clone the entrie 'damaged' drive to the 'spare' drive?Ĭould dd method work? (as in sudo dd if=/dev/sdc of=/dev/sdd) This might be a noob problem.ĬloneZilla only copies the 500MB 'partition', even if I ask it to do a sector by sector copy in Adanced Menu. I ran into a little trouble trying to clone the 'damaged' drive using CloneZilla. Post if you can find any of those, and where exactly (the first should be the first sector of the $MFT and the second the backup bootsector) you found them, if they are found (and they are valid), it is possible to rebuild the filesystem (of course anything that was in either the 73 or 500 Mb is anyway lost forever as it has been overwritten - cannot say if the thingy applies the whole 500 Mb or just the "written" sectors, i.e. go to last sector and go back some 20000 sectors), then start searching for text string "NTFS". Go very near (say 20000 sectors before) the end of the disk (i.e. Thanks in advance.I do know that I have done something really stupid and blame is all on me.īasically you want to get a disk editor and go around sector 786432*8=6291456 and start searching for the text string "FILE0".ĭepending on the amount of "hidden sectors" before (they used to be 63, but nowadays they are more likely to be 2048) you should find it between 6291456+456+2048, if the search flips sectors much beyond, stop it (it is possible than on a 3TB volume the $MFT is moved on a higher address, the 786432 is the "standard" from around 5/6 Gb up, but cannot say if it has a "limit" on such a large hard disk)

If the partition recovery is a lost cause, is there a way to recover the files and directories with their original intact names? My understanding is that NTFS writes a copy of partition at the end of the sector (or was it copy of MBR to the end?).Ĭonsidering that TestDisk is not finding this partition (or for that matter vloume/FS) how can I recreate a partition?Īlso, I think the files might be 'carved' or 'recovered', but this would imply I lose both the original file names as well as the directory structure. TestDisk doesn't find any partitions (both quick and deep scan). I will be using this clone for all recovery purposes and will leave the 'damaged' disk in a safe place. Using CloneZilla I have copied (bit-for-bit, or sector by sector) a clone of the 'damaged' drive to the 'spare' drive. I have access to another drive that is just like this (I bought two orginally) - that is, I have another spare 3TB Seagate BackupPlus that is empty.

My Linux and Win8 machines both see (but don't mount) the 500MB partition and show the rest as "unallocated" or "raw".

The content of IMG file were no more than 73MB, but it created a FAT32 partition of 500MB. The HDD was not modified and had the factory setting that is, it had one partition and was NTFS file. BTW, as you can read from SourceForge page, many others have made same mistake.
#Change access to writeable using wxhexeditor iso#
iso image) to my SD card using Win32diskimager (found here: )īy mistake I wrote the image to my external HDD (Seagate BackupPlus 3TB).
