Hacker News new | ask | show | jobs
by nettdata 5015 days ago
Just revert back to the backup you took right before you did the upgrade.

You DID do a backup, didn't you? You HAVE tested that your backups are working, by doing a complete recovery with them, right?

Right? ;)

My personal philosophy is to be cutting edge on my personal/hobby gear (like the last gen MB Pro I keep for, ah, movies and such), but not to do ANY same-day updates on anything even remotely required for work. That shit stays behind the times but reliable for paying the bills.

After I've seen the upgrades working in the wild for a week or two, and I have verified that all the stuff I need actually works like I need it to, THEN I'll do the upgrade on my work box. After backing it up, of course. Hell, I even have a text file with search phrases and forum URLs for the software I need to have working to make it easy and ensure I don't miss anything.

Call me crazy, but I've learned that lesson the hard way.
1 comments
EchoAbstract 5015 days ago
This seems to be based on an upgrade to the EFI firmware, in addition to the 10.8.2 update. While I've got verified backups for the OS, I'm not in the habit of regularly backing up the EFI firmware, nor do I know how I would restore it on my MBP.

Anyone got advice for backing up firmware on laptops to allow for roll-backs on breaking changes?

link
nettdata 5015 days ago
I'm not sure there is a way for an end-user to revert to a previous version once a firmware update has been successfully applied.

If it wasn't successful, you could use the firmware restore CD that came with the box, or create the CD to do that, but again, that only works for failed upgrade attempts.

I've had to do this once in the past, and the easiest way I could find was to just take it to the local Apple Support shop and get them to do it. They did it for me while I waited, and it didn't cost me anything but time. YMMV.

But good point... I'm not in the habit of backing up firmware.

link
scraplab 5015 days ago
Just to confirm, this is only caused by 10.8.2, not the EFI firmware update. So you can rollback to a 10.8.1 backup and everything works fine.
link