cgsecurity.org

Yes, initializing!
Initializing under windows will only write a 4 Byte signatur into your MBR (partition table).
Since W2k (win 2000) disks must be initailized, otherwise windows can't handle them.
So nothing will be changed to your data.
But after initializing windows will create a partition and format it.
You shouldn't do it and testdisk can search for partitions and recover it instead.
I assume that you've already recovered most of your data?
After initializing you can have another try to use crystaldiskinfo first, because it's possible that you've had a headcrash.
If initializing wouldn't work it would indicate that your MBR is not writeable anymore.
That's why I suggest to run crystaldiskinfo first, after having a try to initialize your disk.
Please let me know.

Fiona

Guess this is what you were talking about MBR not writable anymore?

You could consider to use the testdisk menu delete to delete your partition table.
It's intended to have a try to write to your partition table and if it works, you could solve the problem with read error (CRC - cyclic redundancy check)?
In any case, your partition table is already gone and would be another try to use testdisk to make it writable and to write your partition into your partition table.
If testdisdk would quit with read error also, then you would know that your sector is physically bad.
But before, you could run a diagnose using hd tune free and an error scan:
http://www.hdtune.com/download.html
All red marked blocks (if any appear) will contain bad sectors.
Then you should probably replace your disk.

Fiona

I ran error scan in HD Tune Pro overnight, somehow when I came home from work the program was closed?. However, I was able to get a screenshot at the very beginning (after 1.5hr)



At this rate, I don't suspect the HD will be in any desirable condition. Guess will just need to get another one. This one will find the recycle bin in the very near future.

Thank you very much Fiona. It has been very lucky to have your help along side.