A fail to decrypt system partition

Discussion in 'encryption problems' started by bezymov, Aug 31, 2015.

  1. bezymov

    bezymov Registered Member

    Aug 31, 2015
    My fully encrypted with True Crypt 500Gb system drive was crashed. In the result, windows can't download (status 0xc00000e9 when loading OS), probably about 30 Mb are damaged in bads.
    I checked volumes from the other OS, they were presented and were able to be mounted. However, the content of volume C (not important information) seemed like could be seen from external OS when mounted. Volume D behaved more or less healthy.
    Then I loaded my TC Rescue Disk and chose "Permanently decrypt system partition/drive." The process took about 90 hours and was especially slow on sectors around 387995-311000Mb System asked whether to "skip bad sectors?) I said "Yes".
    When the process of decryption finished, I received a repeating message "Read error" in sector 62. I switched off the computer (no other options available).
    When downloaded from external OS, TC sees the volumes, but can't decrypt it ("the process of encryption of the partition/drive has not been completed. it must be completed first"). When loaded from TC Rescue Disk and chosen "Permanently decrypt system partition/drive," system starts decryption exactly from 387995Mb where first bads were found.
    Any chances to decrypt the volume again, or it's better to restore Boot loader? Any other advices how to deal with these volumes?

    Thank you in advance
  2. amarildojr

    amarildojr Registered Member

    Aug 8, 2013
    Could you use a S.M.A.R.T. tool to check how healty your drive is? Because it seems to me that these "bad sectors" actually meat bad sectors, and if you continue trying to read/write them then your drive's health will just get worse.

    You must make sure that, if there are bad sectors, that their number don't exceed the reserved area number (the area with spare good sectors, the drive marks the current bad sectors and remap them to this area).
  3. Keatah

    Keatah Registered Member

    Jan 13, 2011
    You must also determine why they are bad, otherwise the problem will get worse.
  4. bezymov

    bezymov Registered Member

    Aug 31, 2015
    amarildojr and Keatah,

    Thank you a lot for your replies.

    It seems like the problem goes out of TC itself, and becomes a question of the physical state of the driver.
    I didn't perform additional operations with a drive last days. But found that S.M.A.R.T. behaves very interesting.
    When I turn the computer on it shows the next result (I didn't capture all values, but about the rest S.M.A.R.T. status is "healthy"):

    Then I turn a bit of check without any writing in victoria, just 20 sectors somewhere between 300 and 400, and shows the next result (seems like the driver is completely off).

    Do you think I still have a chance to repair anything from it? (reading goes well only in a remote sectors, like those probably located on logical drive D (out of two - c and D).