Hello. I leaved yesterday PhotoRec recovering one type of files, it was counting them and writing to disk as usually. I turned on "brute force" type recovery this time. Today I see no progress, neither estimated and lapsed time, just "Stop" button on the screen. The recovering disk LED is flashing, but I don't see any progress.
My question is, does PhotoRec still doing something useful and should I wait more, or what is happening? I attached the screenshot of console window.
Update: the free space on the target disk is shrinking.
Did PhotoRec stuck?
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Did PhotoRec stuck?
Disable "brute force".
Your disk is too big.
Your disk is too big.
Re: Did PhotoRec stuck?
Thank you.
Well, yes – the recovering disk has 2 TB, and disk where I write recovered files has only 1 TB. But I am looking only for .doc files, to be precise, for one file. I tried it on default option before and unfortunately I didn't found it, so I am trying what I can.
This is external USB HDD drive. The disk has broken NTFS table, probably not unmounted in Windows when writing the file. Well, the guy that gave me disk said he opened the file in Word (the file has 1.2 MB before and that was correct), there was no content in Word, then he closed it doing no save, then the file size in directory appeared to be zero. So, I'm looking for any way to recover it. BTW, DMDE didn't recover the file (says also 0 B).
Well, yes – the recovering disk has 2 TB, and disk where I write recovered files has only 1 TB. But I am looking only for .doc files, to be precise, for one file. I tried it on default option before and unfortunately I didn't found it, so I am trying what I can.
This is external USB HDD drive. The disk has broken NTFS table, probably not unmounted in Windows when writing the file. Well, the guy that gave me disk said he opened the file in Word (the file has 1.2 MB before and that was correct), there was no content in Word, then he closed it doing no save, then the file size in directory appeared to be zero. So, I'm looking for any way to recover it. BTW, DMDE didn't recover the file (says also 0 B).
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Did PhotoRec stuck?
By the way, are you from Russia?
If Photorec does not find a matching fingerprint, brute force won't help you.
Stating just a size of 1.2 MB as only description of a word file deserves to be punished with failure anyway.
Such a job requires a detailed description - pants down! - like for a bank robber to enable any form of success.
If Photorec does not find a matching fingerprint, brute force won't help you.
Stating just a size of 1.2 MB as only description of a word file deserves to be punished with failure anyway.
Such a job requires a detailed description - pants down! - like for a bank robber to enable any form of success.
Re: Did PhotoRec stuck?
No, I'm from Poland.
Well, I know some keywords. I tried to search within text on Windows Explorer and opened them in Word as well, and all those was not that files.
I guess the disk owner had to remove the disk without "safety removing" when writing that file, and when plugged it again some new data have to land there unfortunately. I guess doing chkdsk /f now is bad idea.
Well, I know some keywords. I tried to search within text on Windows Explorer and opened them in Word as well, and all those was not that files.
I guess the disk owner had to remove the disk without "safety removing" when writing that file, and when plugged it again some new data have to land there unfortunately. I guess doing chkdsk /f now is bad idea.
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Did PhotoRec stuck?
I got curious because of the missing articles in your sentences...
I don't know how Microsoft Word is coding charakters in the doc-format. It maybe Unicode perhaps. If you hit keywords of the word document you might just have discovered one interior cluster. If the first cluster is missing you won't be able to open the remains.
Well, I know some keywords. I tried to search within text on Windows Explorer and opened them in Word as well, and all those was not that files.
If you duplicate your drive as described in the manual you don't have to fear chkdsk /f. Once done, checkdsk /f can't be reversed.I guess the disk owner had to remove the disk without "safety removing" when writing that file, and when plugged it again some new data have to land there unfortunately. I guess doing chkdsk /f now is bad idea.
Re: Did PhotoRec stuck?
Well, I know my English is messy a lot, I often try to check twice what I type, but I was in a little hurry. Sorry for that.recuperation wrote: ↑20 Aug 2021, 15:54I got curious because of the missing articles in your sentences...
There was no time for that, also I had no spare 2TB+ drive then. I was warned on Windows to fix the disk but I didn't do that, and on Linux I disabled auto-mounting feature as well.recuperation wrote: ↑20 Aug 2021, 15:54 If you duplicate your drive as described in the manual you don't have to fear chkdsk /f. Once done, checkdsk /f can't be reversed.
Anyway, all signs points the data was overwritten due the error in filetable. I gave up. Thank You for your help.