Partition Read Error
Posted: 10 Jun 2021, 18:56
Hello,
I have some troubles with my external HDD (500 GB), which did not start anymore and windows always wanted to initialize it.
Therefore i read through many topics and I used Testdisk:
I did the following steps:
Chose the Disc - [Intel ] - Analyse:
No partition was found and message "Partion Sector Doesn't have the endmark 0xAA55" was displayed.
So I performed a quick search and after 1 s my partition was found. I changed it from * to "p" and pressed "write".
After a restart the windows-explorer showed me the HDD again and everything seemed to be fine:
But now I can't open/or copy any data from there and it alway takes some seconds to open a folder or to open a folder is not even possible ("the request could not be performed because of an i/o device error")
When I use TestDisk now and use "Analyse" it shows me: "Partition Read error" (I again used chose [Intel] here even though it suggests "none"?)
Did I do something wrong? What can I do next?
Unforntunately the log-file was already overwritten.
Thanks for your help!
I have some troubles with my external HDD (500 GB), which did not start anymore and windows always wanted to initialize it.
Therefore i read through many topics and I used Testdisk:
I did the following steps:
Chose the Disc - [Intel ] - Analyse:
No partition was found and message "Partion Sector Doesn't have the endmark 0xAA55" was displayed.
So I performed a quick search and after 1 s my partition was found. I changed it from * to "p" and pressed "write".
After a restart the windows-explorer showed me the HDD again and everything seemed to be fine:
But now I can't open/or copy any data from there and it alway takes some seconds to open a folder or to open a folder is not even possible ("the request could not be performed because of an i/o device error")
When I use TestDisk now and use "Analyse" it shows me: "Partition Read error" (I again used chose [Intel] here even though it suggests "none"?)
Did I do something wrong? What can I do next?
Unforntunately the log-file was already overwritten.
Thanks for your help!