Potential a hardisk Issue?
if you know where it's stop from safetech log you can do manual decrypt.
I think it's a HDD issue, but there is a chance that maybe the damaged sectors might just decrypt if I could do it again, such is the unpredicatible nature of mechanical issues.
The process stopped at 33%. Are you saying there is a log recorded somewhere when the removal is in progress? Remember this is SafeTech for v4 I'm using, not Wintech.
Would the local SB File system have recorded that it has removed SB up to 33%? Then maybe it would be worth repeating the Safetech removal process using Values from Disk, in the hope that the local SBFS knew where it had got to?