Endpoint Encryption

 View Only
  • 1.  PGP Disk corruption

    Posted Dec 08, 2012 07:59 AM

    I have two PGP disks - Disk 1 and Disk 2

    Mount at F and G

    Today when I click Disk 1, it mounts Disk 2 and when I mount Disk 2 it also mounts Disk 2

    I've unmounted, remounted, rebooted, selected auto-mount and everything I can think of

    It would appear as though Disk 1 is corrupt - is there a tool to repair it?

    PGP Version is 10.2.1 (Build 4461) PGP SDK 4.2.1

     



  • 2.  RE: PGP Disk corruption

    Posted Dec 08, 2012 08:29 AM

    I've not heard of anything like this happening before.  It sounds like when you attempt to mount Disk 1, that the action is being applied to Disk 2, instead of Disk 1 actually having a problem.  I'm guessing that this is happening when trying to mount the virtual disks from the PGP Desktop GUI.  If so, I'd suggest you go to the File menu and select Scan for PGP Disks.

    I would also expect Disk 1 to mount correctly if you either double click on the pqd file for it, or right click on it and use the resulting PGP Desktop menu to mount it.



  • 3.  RE: PGP Disk corruption

    Posted Dec 08, 2012 09:49 AM

    Just want to make sure that the problem isn't that mounting either one results in mounting to the same drive letter?  The mounting point can easily be changed if this is the problem - just click on the Options button before entering your passphrase for the mount.



  • 4.  RE: PGP Disk corruption

    Posted Dec 08, 2012 01:20 PM

    Thanks for the comments

    I tried changing all of the mount options including mounting it to T drive etc

    When I try and access the data in T, I get access denied

    To make it even more confusing, even though both disks that mount are 'Disk 2' instead of 1 and 2, the data isn't identical and some folders are missing

    I also ran the scan for PGP disks and it found them both but it never actually fixed the issue



  • 5.  RE: PGP Disk corruption

    Posted Dec 08, 2012 03:20 PM

    I'm a Windows user - would try the Windows Error-checking on the virtual drive.