Issue with 10.6.5 upgrade and PGP WDE?

Mike,
I can not find anything that looks like Boot OSX. At this point when I go to Terminal, part of the screen image is now a gray triangle and the spinning wheel of death is not helping. The thing is locked and I can only power off. I am really at quite a loss as to what to attempt. Is it possible that the 10.6.5 update just removed the boot part of the code?
The reason I left the pc world was to not have to do things like this. It is all very disappointing.
Should I just rebuild the whole thing?

Jeffrey -

I would strongly avoid rebuilding unless you have tried everything.

There is a new Knowledgebase article from PGP on this issue. You can find it here: https://pgp.custhelp.com/app/answers/detail/a_id/2288

"Synopsis

Alert: Mac OS X PGP WDE customers should not apply the recent Mac OS X 10.6.5 update. Compatibility issues may prevent the system from successfully booting.

In the interim, customers can accomplish the upgrade safely if the PGP Whole Disk Encrypted system system is first decrypted, then apply the MAC OS X 10.6.5 update and then re-encrypt. We will provide a detailed update how to upgrade a PGP Whole Disk Encrypted system to Mac OS X 10.6.5 as soon as a solution has been identified.

Details

For customers who have already upgraded to 10.6.5 with PGP WDE encryption in place and thus stuck in an unbootable state, we recommend booting from the PGP Recovery CD. The PGP Recovery CD image can be downloaded from the attachment section below.


Update: You will also need to download the script "PGPwdeEFIUpdate.sh". This script makes a needed backup of the correct version of the boot.efi file, which is used should you ever choose to decrypt your WDE-encrypted startup disk. Note that this script will also set the currently running startup disk as the default for future system restarts.

If you have previously followed steps 1-3 in this recovery guide but have not yet run steps 4-7 it is critical that you do so.

Procedure:

1. Boot the system using the PGP Recovery CD.

2. When prompted, authenticate with your passphrase. DO NOT press D to decrypt. Press any key (e.g. spacebar) to boot into Mac OS X normally.

3. Once logged into Mac OS X, PGP Desktop will automatically fix the boot issue and you should no longer need the recovery CD.

4. Download the script "PGPwdeEFIUpdate.sh" to your desktop

5. Open terminal and navigate to your desktop directory by typing "cd ~/Desktop" and pressing enter.

6. Type in the command "chmod 755 PGPwdeEFIUpdate.sh" and press enter.

7. Type in the command "sudo./PGPwdeEFIUpdate.sh" and press enter.


*Caution: DO NOT press D to fully decrypt your disk after booting from the recovery CD. Doing so will result in your Mac OS X system using an older version of bootloader prior to the 10.6.5 update. If you need to decrypt your boot disk, please wait for further instructions from PGP on the correct procedures.*


The Files are located here:

PGPbootISO.cdr = https://pgp.custhelp.com/ci/fattach/get/68439/1289499789
PGPwdeEFIUpdate.sh = https://pgp.custhelp.com/ci/fattach/get/68458/1289527267 "

I had this issue and ended up spending hours decrypting a couple hundred gigs of data. Now have to re-encrypt under 10.6.5. Awesome.

Quick question about the fix about copying pgpboot.efi: maybe I'm betraying my ignorance of exactly how WDE works, but I automatically assumed that I wouldn't be able to do something like that because the whole disk was still encrypted and unreadable as far as Terminal on the OS X CD was concerned. How does that work?

Arg. I just switched from Windows so my MacOS/Unix knowledge is almost zero and I cut and pasted the steps 6 and 7 to avoid mistakes.

chmod seems to have worked. "ls -l" showed:
-rwxr-xr-x@ 1 myuser staff 1094 Nov 12 08:18 PGPwdeEFIUpdate.sh

but "sudo./PGPwdeEFIUpdate.sh" gave an error message
sudo./PGPwdeEFIUpdate.sh: No such file or directory

I assumed a space is missing after sudo, but "sudo ./PGPwdeEFIUpdate.sh" gave another error:
sudo: unable to execute ./PGPwdeEFIUpdate.sh: No such file or directory

I tried as I'd do in a DOS prompt: "sudo PGPwdeEFIUpdate.sh" - but that didn't work either:
sudo: PGPwdeEFIUpdate.sh: command not found

Now I've reached the end of my knowledge.

Any suggestion? (not sure to what extend I'm looking forward to upgrade to Lion)

I've burnt the recovery CD, following the instructions at https://pgp.custhelp.com/app/answers/detail/a_id/2288

My 2007 MacBook Pro apparently refuses to boot from the CD though. If I hold down the Option key as I turn the computer on I get the boot drive menu showing options for "Macintosh HD" with a hard drive icon, and "EFI Boot" with a CDROM icon. I click on the latter, and get the usual Apple logo with spinning 'wait' symbol below. After a while however I get a 'No Entry' sign in lieu of the Apple logo, and the machine just sits there uselessly. I know that my CD/DVD drive is fine, as it was replace less than a month ago by an Apple-authorised repairer.

What do I do now???

Thank you in advance for any advice.

Dear Bydandie
I followed the following PGP support link to login the OS X 10.5.6 post update crash,
https://pgp.custhelp.com/app/answers/detail/a_id/2288
Login was successful with the help of PGP Recovery CD. steps 1 to 6 were completed. But step 7 sudo ./PGPwdeEFIUpdate.sh and press enter results in 'no such file or directory' post authentication by admin password. How to run the script in the desired manner so that solution is followed as per above documentation.
Atleast no I have started booting post update OSX 10.5.6 on PGPWDE.
Thanks for your help!
Rajesh Lodha

some problem here,
sudo ./PGPwdeEFIUpdate.sh and press enter results in 'no such file or directory'

If you save the script directly from the website to your disk, the character encoding is wrong, or the elf magic number is incorrect.

To solve this:
- click on the script and let it open in the browser.
- select the text of the script and save it to disk using a simple editor.
- change the permission using chmod command and run the script.

Also, unmount any external drives or iDisks, since this gives a wrong boot selection when running the script tries to figure out which drive is the boot drive (read: sloppy programming).

@rdegraaf - Thanks! Copied and pasted from browser instead of downloading and it worked.

So the last todo is finding an alternative to WDE before Lion arrives.

After getting to CoreServices and executing cp pgpboot.efi boot.efi I was able to boot normally. I then immediately ran PGP and decrypted my disk. (This was Thursday before PGP issued their "do NOT decrypt" recommendation if you'd already upgraded to 10.6.5) I figured I couldn't leave things this way as I clearly had overwritten the boot.efi file that the 10.6.5 updater changed FOR A REASON. So, once decryption was run I then downloaded the combo updater for 10.6.5 (I originally had updated through software update) and applied it. Then after that update finished and rebooted (once or twice I think) I used the machine for awhile and it seemed normal. I then reran PGP and encrypted the drive. Anyone think of any reason I shouldn't now be just fine and essentially in the same position I would have been if I'd decrypted the drive before ever touching 10.6.5?

I can't think of anything. Before all of the news on this was floating around, I decided the best course of action was to decrypt the drive from my Windows partition since I didn't know to do what topmike posted here. That left some residual partition screwy-ness, so I ended up using Disk Utility to fix EFI booting (my thread with all that is here), and all seems to be well.

About my earlier post: just so I can understand this, how is it we're able to work with that file in CoreServices if the entire hard drive is still encrypted and presumably unreadable?

Bump.

I down loaded the pgpboot.iso.cdr, used disk utility to burn it to cd. Put it into my laptop. restarted the laptop holding down the alt key. Up comes the harddrive symbol and an image of a cd disk called EFI Boot. Clicked on the arrow and for a moment a folder shows up with a ? mark on it. Then the apple symbol and the spinning deal shows up. The cd/dvd drive stops. Then the computer sticks there.
Decided I must have misunderstood the directions. Burnt new disk with the pgpboot.dmg Exact same response.
What shall I try next?

I have discovered that I can now use my laptop as an external hard drive to my iMac in target disk mode. I can take the information off of it if I have to. I still can not find any thing useful to an amateur in terminal. Is there anything I can do with the pgpboot.iso.cdr from this angle?

I am becoming a little bitter toward these pgp people. On their website they say this mess is Apples fault. I guess I would agree as Apple must of hired them to do this project. I have spent way too much time trying to recover from this.