Bad sector on a Diskcryptor partition

[eyal20122013]

Hi,
I have a an encrypted Diskcryptor partition. I had problems with few files - when reading them, the hdd worked in a loop. First I decided to copy some files which did not have problem, as a measure of backing those file, one of them is file A. Those were backed up to another HDD. Then I deleted the problematic files. Trying file A today in the new HDD works fine, but has the loop problem when read from the original file. This led me to checking the drive for bad sectors. Apparently there seems to be few bad sectors in that HDD, probably in that encrypted partition.
1. Can a Discryptor partition deal with a bad sector, i.e, if checkdisk marks that sector as bad, can Discryptor flag that sector as bad and stop using it ?
2. If I delete a file from a Discryptor partition, does it move the other files ? I ask this because file A was working correctly until I deleted the problematic files, then file A was causing the hdd loop thing, which makes me think Discryptor moved that file on one of those bad sectors.
I don’t think it is a virus from a superficial scan, but will make a deeper scan later on.

 

[13thmonkey]

I'd decrypt it all, and then recreate the volume. You do have a backup don't you?

 

[eyal20122013]

I have a little bit outdated backup, but I can manage.
I do, however, want to understand what exactly is the problem. It seems to me too much of a trouble to fully format and recreate a volume when a bad sector pops up.

From reading in forums I understand that chkdsk doesn't mark a bad sector as bad as long as there is data on it. is there a command which can mark bad sectors as bad ignoring the data on them (that way, I think, it also doen't get to hdd loop while scanning for bad sectors) ?

 

[eyal20122013]

Thanks 13thmonkey,
I was going to apply your recommendation, but decided to check the HDD for physical test, before doing all this hard work.
My HDD is WD red 3TB, so I used WD Data lifeguard diagnostic (through DOS), did an extended test and it resulted with a code "0225", which is to replace the HDD.

 

[13thmonkey]

never do tests until the data is as safe as it can be... the test could make it worse. But now you know. Should be a warranty job on a red?