- Sep 21, 2017
- 48
- 0
- 10,540
had a spare drive kicking around, told it should contain backup footage
plug drive it immediatly "windows needs to format this drive to use it!" erm no
got into disc management because I want to see if it has partitions, click something away... oops guess I just told windows it could initialize the drive :T dang it!
anyway in an attempt to recover (anything) I ran quick scan with testdisk on the whole drive as ntfs which found no deleted partitions, then again as ntfs deep scan again found no deleted partitions, I run a testdisk scan as "no partition" found nothing.
I did a 5 hour scan of the whole drive with getdataback ntfs told it to recover raw files it again found nothing "this volume blah blah did not contain an ntfs partition" and just finished a several hour scan with photorec which usually in worst case scenario will dump a bunch of junk files like gabled text files but again has dumped nothing.
1/initialization should simply make a new partition table and not actually trash any of the underling files/filesystem right ?
2/can initialization of a drive in disk mangement mess up file this much? I always thought you had to zero the entire drive to make nothing recoverable?
3/I seem to recall having some drives we didn't use, given the results is possible that by accident initialized an actual empty drive? any way to find out?
also any other suggestions?
plug drive it immediatly "windows needs to format this drive to use it!" erm no
got into disc management because I want to see if it has partitions, click something away... oops guess I just told windows it could initialize the drive :T dang it!
anyway in an attempt to recover (anything) I ran quick scan with testdisk on the whole drive as ntfs which found no deleted partitions, then again as ntfs deep scan again found no deleted partitions, I run a testdisk scan as "no partition" found nothing.
I did a 5 hour scan of the whole drive with getdataback ntfs told it to recover raw files it again found nothing "this volume blah blah did not contain an ntfs partition" and just finished a several hour scan with photorec which usually in worst case scenario will dump a bunch of junk files like gabled text files but again has dumped nothing.
1/initialization should simply make a new partition table and not actually trash any of the underling files/filesystem right ?
2/can initialization of a drive in disk mangement mess up file this much? I always thought you had to zero the entire drive to make nothing recoverable?
3/I seem to recall having some drives we didn't use, given the results is possible that by accident initialized an actual empty drive? any way to find out?
also any other suggestions?
Facebook
Twitter
Instagram