Accidental Used Diskpart - Clear Command. How To Revert

pedroc1999 said:

Im pretty dissapointed... it once again found my 3 but not my 4th along with about 5-7 other 'boot' partitions about 3mb big. What should i do! I had 4yrs worth of pictures on that drive!

your 3 partitions recovered succesfully? Do what I asked you to do in post 20

pedroc1999 said:

BTW it is a FAT32 Format...

1682648163

that is the first sector

If partitions are aligned at MB boundary it starting sector is multiple of 2048. 1 sector is 512 bytes, so 2048 sectors= 1 048 576 bytres=1MB

1682648163 isn't dividable by 2048!! So not aligned. I think partition 1 is also not aligned and starting before 1MB boundary so cleared by "diskpart clean" command. And many relevant information is at beginning of partition.

• How can WIN7 or PW know it's an NTFS partition?
• How does it know which blocks belong to a file if the mapping has been lost?

You can try recovery software, but most (maybe all?) can only recover/repair a partition (and you don't know where it was).

Why the heck did you do the "diskpart clean" command? And why didn't you make backups?

pedroc1999 said:

I was following a tutorial on how to make a bootable usb drive with win7 and only noticed i ran the command after it happened. There was no warning what so ever about it clearing my mbr. Is there any hope. Maybe a more advanced partition recovery that will look where the mbr should be for one?

MBR consist of

• Master Boot Code: Generic code that looks for an active partition. It jumps to bootcode on that partition. This code can easy be regenerated. But this is not a problem in your case.
• Partition table: Start sector of partition, number of sectors, partition type (for example NTFS).
• Disk signature: Sort of bar code ... it uniquely identifies the disk. If you swap two physical disks, win7 still knows where it is. But this is not a problem in your case.

Only real problem is that the MBR (first 512bytes on physical disk) has been overwritten with zero's. Recovery software knows how NTFS, FAT etc works and how the first few blocks of such partitions look like. If it finds one it can update partition table and it's fine.

But you zeroed more than first 512bytes! You zeroed first 1MB. In that area was the first part of 1st partition.

pedroc1999 said:

So basicly there is no start to my partition.... Only an end...

End position is also unknown yet. Most likely it's ending one sector before start of second partition. Start sector is most likely 63.