Recover data from an accidental diskpart / clean command

Looks good i'm pretty sure that extended should be there like that. Choose to write it then post pic.

jumanji said:

hmmmm............... This thread came to my atttention just a few minutes ago. I tried to cry "HALT" but before I can do that it seems to have moved faster to a point of no return.

If you have not given a Write Command yet, don't. If you haven't rebooted, Don't. Just quit TestDisk

Oh, He has rebooted I believe.

jumanji said:

@rvcjew, now you can proceed with what you wanted to do. and see whether the data can be recovered.

When I started reading this thread I realised a mistake has been done. The mistake is as I saw it:

His 3TB drive seems to be a GPT drive. The 129MB partition shown by Partition Wizard is the Microsoft System Reserved Partition.

When the OP ran TestDisk he should have chosen [EFI GPT] and not [Intel]

Then perhaps everything would have gone right.

Now I don't know. Carry on with your processing and let us see where we land. If data is recovered I may have to give you ten reps.:)

Oh god, your right I thought the intel incorporated the GPT (I saw mac, and linux and I guess had a brain fart, I still think we have a chance though). Well cross your fingers. We'll have to just wait for there reply.

jumanji said:

rvcjew said:

Oh god, your right I thought the intel incorporated the GPT (I saw mac, and linux and I guess had a brain fart, I still think we have a chance though). Well cross your fingers. We'll have to just wait for there reply.

Yep, I do think the situation can be retrieved with a little bit of additional exercise. But for the present continue with your processing - but no more write command on any count. Only Copy command.. We have lots of unknowns when trying Data Recovery, and I won't be surprised if data can be recovered even with this fault. That is why I said if it is recovered, I have to give you ten reps :)

But I can assure the OP that nothing is really lost and he need not lose hope - not yet.If at all what could have been written is a wrong partition table in sector 0. We can easily write zeros to the whole sector 0, or delete only the wrong partition table written into sector 0 and bring the Disk back to the pre TestDisk run state and then start TestDisk all over again.

That certainty, makes me feel better and i'm sure the OP as well, thank you for the excellent advice and information to help this process in the future. I figured there was a way to revert the table but did not know what it would be.