cgsecurity.org

I have an Iomega hard drive with the Lock feature. Unlocking it makes the drive visible. It unlocks but is no longer visible to File Explorer and states the drive needs to be formatted. Disk Management 'sees' it, but shows no data on it. I did try the chkdsk /f H: in the Command box, but get a reply that the file system cannot be detected, so that does not work.

I had never heard of TestDisk, but saw a review on it and instructions how to use it on this site: https://www.handyrecovery.com/testdisk-review/. It even had pics to help!

I ran it and it told me this:

It stated it had found something like 37,000 files. The results were posted in 517 folders named recup_dir.x. When I began checking the folders, I found that folder recup_dir.84 all the way through folder recup_dir.517 all had the very same images, all of them being only 3 images repeated endlessly in all those folders, 434 folders counting the first folder- 84.

The images are laid out in rows of 6 images; say in Folder 84, they are a, b, c, d, e, f. Images d, e, and f, are repeats of images a, b, and c. Then 3 folders later, Folder 87, they are laid out in the same order. Folder 85 starts with image b and Folder 86 starts with image c. It is the very same in all 434 Folders!!

How is this possible?

Why does TestDisk repeat images like that?

I can overhaul a rotary engine, but I have no idea how the same 3 images can be repeated something like 72,000 plus times each in 517 folders!! Especially when at the first it said it had found around 37,000 files!!

The basic 3 images are kept, but the rest of all those folders and all those duplicate images are going out for sure!

Does PhotoRec work the same way?? Would it do a better job of find the photos and videos?

viewtopic.php?p=37406#p37406

If you continue ignoring my answers I have to assume that communication with you is not possible .

The TestDisk package contains Testdisk, Photorec and other software.

You are posting links to some third party web site describing Testdisk and you pretend having run Testdisk. You did not. I told you. Doesn't that should ring a bell? You are ignoring it.

Just try assembling a rotary engine ignoring torque figures from the manufacturer manual and the order of torquing. Good luck!

Stuff to read:
https://www.cgsecurity.org/wiki/TestDisk

Cross-read the manual. It contains documentation for Testdisk and Photorec:

https://www.cgsecurity.org/testdisk.pdf

Try everything again. Cross-read the forum to learn how to document a case. Make screenshots and upload them to this site.
Apart from your complaints there is virtually no case description.

I can't foresee your specific situation. If you are too lazy documenting it, I am too lazy to respond.

I'm not too lazy to respond. It's just that I don't know how to navigate this board properly. I've read the documentation. And I followed the directions from the site I mentioned and ran Testdisk. I also deleted the folders with the repeated files. Right now I'd like to try PhotoRec but am wondering if the result would be the same. I also figured a way to get screenshots, so if I do try PhotoRec I can get screenshots along the way. Please remember I'm 87 so a lot of this is new to me.

BTW, the rotary engine ran like a top. I also had a friend cut the center of the Thermal Reactor out so it would run better and cooler.

I don't know if posting the link to another website is allowed or not. If so, I apologize. But I can assure you i am not lying! I detailed the results I got and named the folders according to what TestDisk gave me, something like 433- 434 folders with the same 3 basic images repeated in all those folders. How would I get that result if I didn't even run TestDisk? I have probably violated a lot of the rules here. I apologize! Please don't keep scolding me. All i want at this point is to know if PhotoRec will give the same results that TestDisk gave me. Please---

Testdisk does not create folders that are labeled "recup_dir.xxx".
And again, you did not even bother reading the documentation, for instance reading Testdisk.pdf.
Furthermore there is no case documentation of yours.
I assume you are trying to troll me.

There is extensive documentation on this website on every aspect of Testdisk and Photorec. Cross-reading, keyword searching can provide results faster than reading the documentation like a newspaper.

Why are you refusing to read and check what I told you?
How come that you completely ignore it when I tell you that you did not run Testdisk?

WOW! I've been accused of lying, pretending to run TestDisk, not documenting, trying to troll you. I've never been treated like this on a board. All I know is that I got the folders I described. I didn't run any other program. Whatever WAS running, it did recover files in the other folders with that name. I did read the documentation and thought I was doing everything right. I'm sorry I bothered any of you. This is crazy. I did get some info that helps in this last go-round, and I'm thankful for that. You don't need to bother any more. I'm out of here.
thank you anyway.

I hesitated to ever come back here after all the uproar informing me TestDisk did not create folders with names like recup_dir.xxx when that was exactly what happened. I'm going to try to upload some screenshots of what PhotoRec did, etc., then get out of here before I get in trouble again. I can't explain why those folders were named like they were. Was it because that Iomega drive was set up differently? I don't know. All I know is that both TestDisk and PhotoRec were very similar in their output. The BIG difference was that PhotoRec did not post all those extra folders that had something like 433 folders, all repeating the same 3 files over and over and over. I documented that earlier in these posts. I also found that PhotoRec found the same first 8 folders that TestDisk did, which contained lessons from my daughter's biology class. Basically from that point on it repeated what TestDisk found. Remember, Testdisk posted 517 folders. I deleted the extra 433 folders that contained the same 3 images repeated endlessly, and moved my daughter's lesson files into a separate folders, which were in the first 8 folders. I do have a pic of the remaining folders, recup_dir.9 - recup_dir.83. I'll try to post that. I couldn't get all the folders in the pic from Photo_Rec, but have most. That posted a total of 101 folders, a lot more efficient in finding images that TestDisk in my experience. I have a pic of the beginning of PhotoRec as it's getting ready to scan the Iomega drive and one (before and after with arrow) at the end where it shows what the names of the folders are going to be. Sorry, but it shows the folders will be named as I have already pointed out. Now to try to post the images, then get out of here.
I can only post 3 images so I'll just post the pic of the TestDisk folders, PhotoRec with the arrow and most of the folders it created. I could probably find out why I can only post 3 pics if I stopped and asked but I have no desire to even be here.

Thank you for providing a proof that you did run Photorec:


Based on the additional information contained in your picture you are running the outdated and unsupported version 7.1.
Use version 7.2-WIP. This is not betaware but the result of continuous small improvements and bugfixes.
It could very well be that the version of Photorec contained in the 7.2-WIP package won't run into an endless loop.

Use this page for download:

https://www.cgsecurity.org/wiki/TestDisk_Download

If you rerun testdisk_win.exe out of your Testdisk download package, do not forget to use the logfile feature and to post your logfile.

I am looking forward to learning how you can force Testdisk to produce Photorec-like "recup"-directories as you pretended. Please document how to do that!

Thank you.