TestDisk hangs at a particular cylinder
Posted: 15 Jun 2015, 16:38
Need help!
I have a 2TB Seagate HDD with two partitions: F and G. Somehow all the files in G disappeared suddenly and the drive shows as "Raw" in Windows 7. But F still works fine.
Then I turned to TestDisk, which can see this partition. But a quick search found nothing, only with the warning message: the filesystem may be damaged.
Then I ran a deeper search, and Testdisk seemed to find a few bad sectors after many hours with these lines (from my memory, so it may be inaccurate)
HFS + 11387 432 ...
But it then stalled at
Analyze cylinder 16387/132755: 12%
It got stuck in this status for several hours with 0 CPU utilization and did not respond to any key. Finally I gave up and killed the process.
I then restarted the tool and ran the deeper search again. This time it scanned through the previous cylinders fairly quickly. But it again got stuck at this particular cylinder with a new error message:
Read error at 16387/222/47 (lba=247785472)
So I'm wondering what the best step to take next.
Many thanks,
hfeng
I have a 2TB Seagate HDD with two partitions: F and G. Somehow all the files in G disappeared suddenly and the drive shows as "Raw" in Windows 7. But F still works fine.
Then I turned to TestDisk, which can see this partition. But a quick search found nothing, only with the warning message: the filesystem may be damaged.
Then I ran a deeper search, and Testdisk seemed to find a few bad sectors after many hours with these lines (from my memory, so it may be inaccurate)
HFS + 11387 432 ...
But it then stalled at
Analyze cylinder 16387/132755: 12%
It got stuck in this status for several hours with 0 CPU utilization and did not respond to any key. Finally I gave up and killed the process.
I then restarted the tool and ran the deeper search again. This time it scanned through the previous cylinders fairly quickly. But it again got stuck at this particular cylinder with a new error message:
Read error at 16387/222/47 (lba=247785472)
So I'm wondering what the best step to take next.
Many thanks,
hfeng