I ran Testdisk for the first time on my 500 GB internal hard disk which was not mounting on linux , but all partitions were clearly visible in GPARTED and test disk and I could see all my files also in all those partitions using Test Disk by pressing the 'P" key. Once having confirmed all the partitions and files were correct, I entered the write operation of Test Disk to populate the partition table. But after rebooting the system, now my partitions are not coming in GPARTED. even Test Disk is throwing innumerable read errors and taking ages to complete, whereas in the first run, it took few minutes. Has the write ooperation corrupted my disk? How to recover the files and folders now?
Has write operation of Test disk corrupted the files and folders in that partition?
TestDisk write operation damaged my disk
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: 3026
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: TestDisk write operation damaged my disk
If your partitions were visible in GParted there was no reason to rewrite the partition table.MPSEEMA wrote: 26 Mar 2022, 11:30 I ran Testdisk for the first time on my 500 GB internal hard disk which was not mounting on linux , but all partitions were clearly visible in GPARTED and test disk and I could see all my files also in all those partitions using Test Disk by pressing the 'P" key. Once having confirmed all the partitions and files were correct, I entered the write operation of Test Disk to populate the partition table.
It seems that your drive is about to die. A write operation only overwrites approximately one sector per incorrectly selected partition when being in MBR mode.
But after rebooting the system, now my partitions are not coming in GPARTED. even Test Disk is throwing innumerable read errors and taking ages to complete, whereas in the first run, it took few minutes. Has the write ooperation corrupted my disk?
You can try to duplicate the drive as described in the manual or consult a professional recovery service.
How to recover the files and folders now?
No.Has write operation of Test disk corrupted the files and folders in that partition?
Re: TestDisk write operation damaged my disk
You should check the SMART status of the drive to see if it's ok on the hardware side.
If SMART indicates any problems then be very careful as any further operations could make things worse and it should go to a lab.
If SMART shows no problems than it's likely a software problem and you should do some file recovery.
The write operations that Testdisk does only involve a small amount of data and do not format so the files should still be on there and hopefully retrievable.
If SMART indicates any problems then be very careful as any further operations could make things worse and it should go to a lab.
If SMART shows no problems than it's likely a software problem and you should do some file recovery.
The write operations that Testdisk does only involve a small amount of data and do not format so the files should still be on there and hopefully retrievable.