Solved Accidental Used Diskpart - Clear Command. How To Revert

[Pedroc1999]

It is still at 35% im locked out of the main windows

 

[Kaktussoft]

It is still at 35% im locked out of the main windows

I understand.. tell me later.

But is it the FIRST (so on left side) partition on physical disk that you try to recover??
Did you create it with EASUS partition manager bootable disk, or from win7 installed program?

 

[Pedroc1999]

Yes it is the first and also the primary one (i think) the partitions were made with the win7 installed program

 

[Kaktussoft]

Yes it is the first and also the primary one (i think) the partitions were made with the win7 installed program

Primary or logical isn't important (at least now). You can have maximal 4 primary partitions, or 3 primary partitions and 1 extended on that physical disk. The extended partition can contain a lot of logical partitions.

A partition MUST be ACTIVE only to make it the BOOT partition. And only a PRIMARY partition can be ACTIVE.

 

[derekimo]

Heres the Background Story -

I have a 1tb external hdd, which is partitioned into 4 parts, 1 main (about 750gb) 1 for ps3 (120gb) 1 for linux (4gb) and 1 for a 'shared area' between Win7 and linux. Everyone i have tried so far can only find the PS3, linux and the shared area. not the most important one aka Main one. I am running partition wizard full on every sector of the disk, it has found 4 3.01mb partitions labeled as 'boot'. It is at 14% (very slow)

Yes it is the first and also the primary one (i think) the partitions were made with the win7 installed program

Primary or logical isn't important (at least now). You can have maximal 4 primary partitions, or 3 primary partitions and 1 extended on that physical disk. The extended partition can contain a lot of logical partitions.

A partition MUST be ACTIVE only to make it the BOOT partition. And only a PRIMARY partition can be ACTIVE.

This is an external drive he's talking about.

 

[Kaktussoft]

Whole disk was formatted so no unallocated space? 3 partitions have been recovered. So lost partition in the space that's now unallocated. It can be recovered easily if "diskpart clean" didn't wipe part of it. "diskpart clean" only wipes the first 1MB of physical disk and that's where MBR and partition table is.

Normally in win7 partitions are aligned to 1MB boundaries.... so easy to recover. But I don't know how easus creates partitions! If I know where the other partitions start, I know if they are aligned properly. If not aligned properly.... most likely partition 1 is also misaligned and starting before 1MB boundary. So partly overwritten by "diskpart clean"

 

[Pedroc1999]

It was empty ish so hopefully not much if any damage if i do get it back

 

[Kaktussoft]

Did it already finish ... If not how many percent?

Please answer #20

 

[Pedroc1999]

It is at 63% and i cant answer post 20 because it hasnt finished and im locked out of the main windows

 

[Pedroc1999]

Currently At 92%

 

[Pedroc1999]

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!

 

[Kaktussoft]

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]

I only recovered 1 as the others i was going to delete anyway. Il do it now....

 

[Pedroc1999]

BTW it is a FAT32 Format...

1682648163

that is the first sector

 

[Kaktussoft]

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]

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?

 

[Kaktussoft]

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]

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

 

[Kaktussoft]

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.

 

[Pedroc1999]

so... what if i specify the search rang from 0 to the start of partition 2, would it find anything or just nothing