Hello..
I have been looking around the web for a forum that might be of help to me. I decided to stop here first only because I have used HDDGuru products in the past, so I am presuming the forum would contain knowledgeable people.
I am in a bit of a problem with a HDD. It is completely my fault. This is not a question of drive failure, only human failure.
I have a Seagate 1TB FreeAgent external Drive which I intended to use as backup. I only purchased it 3 weeks ago, so it should be pretty healthy. Anyway, because I had so many other random 3.5" drives lying around, near failing, I ended up putting everything of value on this Seagate, and then, of course realized I had defeated the purposes of a "back-up" drive, and now needed to backup my drive that was to be my backup drive.
Of course, I never got around to doing this for the ensuing 2-3 weeks after purchase of the drive and transfer of my files.
I can tell you a good deal of information about this catastrophe, and what I am seeking is some sound advice. I know there are so many methods and applications which claim to do miraculous things, but I really have not touched it since this problem occurred yesterday.
OK, here we go:
Before my disaster, this was what my Seagate drive looked like when I ran fdisk -l
Code:
Device Boot Start End Blocks Id System
/dev/sdb1 1 93062 747520483+ 7 HPFS/NTFS
/dev/sdb2 93063 121601 229239517+ 83 Linux
Without discussing how or why I made this mistake (trust me, I have beaten myself up way to much already), the following actions were taken by me on this drive which caused its damage:
1. Believing it was a USB pendrive (!!), I first formatted it as follows
mkfs.vfat (only the first 1500MB)
mkfs.ext3 (the remainder of the drive, so approximately 995+ GB were formatted as ext3.
2. Then, still not realizing I was tampering with my main storage drive, and having some problems with copying files to the "pendrive" (which was my Seagate), I started a dcfldd wipe on it. But my intelligence finally resumed as I noticed that the dd command was proceeding beyond 4000MB, and I knew something was amiss. I immediately stopped the dd command.
Since then I ran testdisk, which did find the NTFS partition, and then Photorec, which allowed me to recover 100,000+ files without directory structure or names. I stopped that process midway through because that was going to be of no use to me.
To aid in anyone's diagnosis or suggestion, after running Testdisk, here was the result:
Code:
Disk /dev/sdb - 1000 GB / 931 GiB - CHS 121602 255 63
Partition Start End Size in sectors
D HPFS - NTFS 0 1 1 121600 254 63 1953520002
D HPFS - NTFS 0 1 8 82862 254 63 1331194025
D HPFS - NTFS 0 1 15 93061 254 63 1495040953
D Linux 82863 0 1 121600 254 63 622325970 [Linux_Backup]
D Linux 93062 0 1 121600 254 63 458479035 [Linux_Backup]
Structure: Ok. Use Up/Down Arrow keys to select partition.
Use Left/Right Arrow keys to CHANGE partition characteristics:
*=Primary bootable P=Primary L=Logical E=Extended D=Deleted
Keys A: add partition, L: load backup, T: change type, P: list files,
Enter: to continue
NTFS found using backup sector!, 1000 GB / 931 GiB
So... I am here seeking any other assistance I might find. The main partition of value is the NTFS partition. I am currently in Linux, but will use any OS necessary to recover these files even if I only get 80% of them, I really need the directory structure and names of said files.
I purchased two one (1)-Terabyte external drives today to make this job easier, as I know I will need the space.
I realize that by wiping the first 4GB I have destroyed the MBR and the file table... but I also know that NTFS is unique in the way it has meta-data throughout the filesystem.
ANYONE....who could please offer some words, advice, tricks, hacks, magical spells, or incantations (I am open to anything), I would be greatly -- immensely -- appreciative.
Please let me know.... I am near a panic attack as it is.. I know this is my fault, and that only makes it worse.
Thanks,
Paul
