Hello,
I recovered files from my external hard drive but all files are in TXT format.
It`s on windows 10 and I used Photorec version 7.1, I used the default settings of photorec
The disc analized is a corrupt disk in NTFS format
I tried a document identifier but it can't read them as jpg, pdf, docx, etc.
There will be some photorec configuration option to make the files readable? or what can i do to solve this problem.
Thank you!
Photorec Recovered files without correct extensions
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
-
recuperation
- Posts: 2737
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Photorec Recovered files without correct extensions
Use the latest Testdisk package, which is 7.2-WIP.
"corrupt disk" is an insufficient description.The disc analized is a corrupt disk in NTFS format
Due to the lack of case description I can't give you a special hint. If you do not know which information might play a role, here is a questionnaire I once compiled:I tried a document identifier but it can't read them as jpg, pdf, docx, etc.
There will be some photorec configuration option to make the files readable? or what can i do to solve this problem.
0. Please provide your Testdisk logfile.
1.Which operating systems can be booted from your computer where the incident happened?
List them all!
2. Which version of Testdisk do you use?
3.Do you prevent/reduce write access to the failed drive/file system?
[Yes/no]
4. If yes, how is that done?
[ ] I removed the failed drive and connected it to another computer (not linux) as an external drive => risky
[ ] I am using a live linux from a USB stick on the machine with the broken drive => good
[ ] I am booting a linux system on a different system and connect the drive externally once the linux finished booting => good
5. Is the broken drive a drive where an operating system resides on or is it a data drive?
6. What technology is your disk (HDD, SDD, USB stick, Compact Flash card, SD card,...)?
7. What is the size of your disk?
8. Who is the maker of your failed drive?
9. What is the model?
10. Is the drive something you bought "naked" one or does it come with a housing and a connector for a computer (p.e. like "WD My Passort")?
11. If possible, provide a logfile from smartmontools!
Instructions:
viewtopic.php?f=5&t=10910
12. What has been the partitioning scheme used on the failed drive (MBR (old partition table style), GPT, Superfloppy)
13. How many partitions have been on the broken drive, what was their size, what was their file system?
14. Is your drive visible in your operating system (Windows: Disk management, Linux use lsblk command, get information using hdparm command)
15. Is the partition scheme containing your partitions still visible?
14. Describe the supposed event when your system went from "OK" to "broken"!
15. Is your disk showing signs of failures such as
-clicking noises
-permanent reboot (spindel speed up followed by a stop)
-no spindel speed up
?
16. Do you use encryption, if yes, which one?
17. If you use encryption, what is the scope?
[ ] full drive
[ ] partition
[ ] file container
[ ] single files