File Share Encryption

 View Only
  • 1.  PGP WDE with SSD - Corruption, Garbage Collection?

    Posted Dec 05, 2013 02:26 PM

    I have a Crucial SSD drive, and I installed PGP WDE on the drive. The drive crashed hard after about 2 weeks of running very slow with PGP, and I had to do a chkdsk to be able to read the data on the drive. So, hooked up externally, PGP could unlock it but it came up with I/O errors when I would try to open the drive through My Computer. Running chkdsk /R finally allowed me to get access to my files, and then unencrypt the drive. Now it seems I can boot and the drive seems fine unencrypted.

    I called Crucial about this. They said they do not support software-based encryption of SSD drives, and large part due to the garbage collection process. IN fact, they just integrated support for Windows Bitlocker in the firmware of their newer drives, but no other encryption system. They said the chkdsk probably worked because it was finding files in the area marked for garbage collection, which may not have been cleaned up due to WDE processes. Thus, it became corrupted enough to prompt the crash.

    How does this sound to the PGP folks out there? Is it true that PGP WDE should not be enabled on SSD drives?

     

     

     



  • 2.  RE: PGP WDE with SSD - Corruption, Garbage Collection?

    Broadcom Employee
    Posted Dec 06, 2013 06:42 AM
    Hello spitty, Please have a look at this article: Symantec Drive Encryption of Solid State Drives - TECH203315 http://www.symantec.com/docs/TECH203315 As the manufacturer states they don't support software-based encryption of SSD, it seems to be their design decision. However, if you believe there is a bug in the software, then please contact the Technical Support, you can find the details here: http://www.symantec.com/support/contact_techsupp_static.jsp Thank you and regards, dcats


  • 3.  RE: PGP WDE with SSD - Corruption, Garbage Collection?

    Posted Dec 06, 2013 11:35 AM

    It works perfectly well on lots of SSD's.  The fact that they dont support it doesn't mean it won't work, they just haven't tested it / don't want the hassle of fielding calls about it.