we have here a strange problem over here. Our current problem is now the same with two different HDD´s from two different laptops – we simply cannot decrypt any data from these disks. Both suddenly stopped working and the users could not logon anymore ( Error Message: Safeboot is Corrupted ).
The procedure of removing safeboot and/or forcing safetech to decrypt data is clear so far. We also still have instructions and manuals from our training. One of the HDD´s I could clone, so accessing data on it should work.
We tried it also with a healthy pc with safeboot on it. It worked perfectly (as described in our manual ), but with the “corrupted safeboot”-pc´s we had no luck.
Here is, how we tried it:
1. Create Configuration File from Server
2. Boot Safetech from Floppy / also tried with Wintech CD
3. Enter the Code of the day
4. Authenticate from Database ( read the Configuration file and choose the machine name )
5. Select the disc and workspace algorithm ( FIPS AES )
6. Open Workspace
7. Select the first Sector from the boot-partition ( in most cases it’s Sector 63 )
The decryption for this sector is not working, so I know that we do not need to force the decryption of the whole drive ( It´s not possible just to remove Safeboot, because it says that Safeboot is Corrupted ). Anyway, we do not know, what we are doing wrong, so please help us if you can.
Thanks in advance and best regards
DanielNachricht geändert durch dan_tom_soe on 09.09.10 04:21:51 CDT
What information it is showing when you click
Disk > Disk information in Wintech ??
Are you sure about ecrpytion you are using (AES256) ?
Disk Information (error=e002000a)
Crypt list: Region Count: 0
He is showing two partitions - that´s correct.
The second HDD is better. There I can see also the encryption code ( 12 ). Today I had really luck with this disk. I could authenticate from SBFS one time and he accepted my logon. But also in that case I could not decrypt sector 63. It´s always the same.
I also tried to change the SATA Mode to AHCI ( from Compatibility ), but same result. To be honest, I´m not sure, if the SATA Mode is really relevant in that case.
And yes, I am sure, because all PC´s in our company are encrypted with AES FIPS. I also tried the other algorithms, without any luck.Nachricht geändert durch dan_tom_soe on 09.09.10 06:13:34 CDT
Which version of EEPC do you have installed?
Do you still see Master Partition Table properly? Does encrypted disk partition start at sector 63? What is client OS?
To determine if sector is encrypted or not, you must see it in clear (after decrypting workspace or without decrypting). Otherwise you don't know and cannot make next step.
Hi, we are using Version 5, 1, 6, 0
I can see the informations for the Partition. On the first disc, ist starts at sector 63, at the other HDD at sector 11143188.
Client OS is XP.
In our manual I could see, how sector 63 is looking like. On the right side a text should appear ( A disk read error occured... and so on ). Then it´s decrypted. In my case the signs change but no readable text appears. Is there any other sector like this first I could try? Does anybody of you know?
I made a screenshot of the disk information of the second disk. Again I could authenticate via SBFS and you can see the result of decrypting sector 11143188 in the background.
Uploaded with ImageShack.usNachricht geändert durch dan_tom_soe on 09.09.10 07:18:47 CDT
Is decryption was in progress ? it is showing in Disk info ..
What is the status of encryption it is showing on EEM machine's Properties ?
are you able to see the Data in A43 Managemetn utility in Wintech after authentication ?Message was edited by: Ram Dudani on 9/9/10 7:30:36 AM CDT
In the properties it says that the machine is fully encrypted. This disk was encrypted 1 year ago or more, and it suddenly stopped working. I tried to remove Safeboot after my first successful logon today, but it did not respond, so I restarted the PC. Hmm..... seems that i made a big mistake. :-(((
But what is the A43 Management utility? I cannot see anything with A43 in the menu ?!
That is a strange sector number to start partition for Win XP.
What else is installed on that PC? Any non-standard utilities or partitioning scheme?
Keep in mind that EEPC is not compatible with some rapid recovery applications.