Got a Desktop engineer report that 33% into a SafeTech removal (v4.2.15) the following error is seen:
Error writting HDD (rc=5b030000)
Can anything be done? Would repeating the removal process be risky, seeing as 33% of the sectors are now presumably decrypted? Or is the removal process intelligent enough to identify only the currently encrypted sectors to resume removal?
Failing that, I can manually decrypt a sector range using SafeTech but how do I know where it got to before?
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?