Once again apologies for being away for so long but there is a reason. My Mac has recently had the mother of all crashes. Such a bad one by my experience that it’s worthy of a post here on Tailwind.
It all started with a ‘Software Update’ from Apple and ended in a hard disk failure and a brand new hard disk.
As usual, diligently, I kept my system up-to-date by downloading the recommended packages that perked up in my automated ‘Software Update’ application. Now, I trust Apple, so I’d expect certain things to just work. In fact ‘just works’ is a brand differentiator for Apple across all their touch-points, retail outlets, OS, hardware, service design and even Apple Care in my eyes. They often surprise me with “Oh that’s clever. That works.” Surprise and delight some call it.
/fanboy
Anyway there I am, system updated, all is tickety boo until I next shut my system down which was at the request of an air hostess enroute to Schipol Airport in the Netherlands.
I was on my way to our Amsterdam office (Lost Boys) to give a presentation of our best work from the London office and of course, I was working on it on the way. Who doesn’t?
Once the flight was up I wanted to start working again but it wouldn’t restart. It would boot-up seemingly well only to stall and hang just after loggin-in, teasingly showing me my desktop but with no icons or dock.
I spent the remaining 40 minutes on the flight starting, restarting and waiting patiently only to find my beautiful air hostess asking for me to turn it off again.
The story goes on with me trying to reboot in the security queue, at passport control and in the taxi.
Nothing.
I find myself sat in my hotel lobby using a unix command called FSCK or something..?
When a Mac user ends up in this territory, you know it’s going pear-shaped fast.
Eventually I get into our Amsterdam office and hand it over to Erwin in Tech Support who is licking his lips at the challenge, but simultaneously and knowingly shaking his head.
I go downstairs, meet my Dutch colleagues and have some interesting discussions about our work and later meet up with Erwin who’s managed to resurrect my HDD enough for me to rescue some data using some dark ninja unix skills.
He’s smiling. Challenge met. But has advice for me.
So what happened?
Well, Erwin said to me whenever you download these updates do two things:
- Back everything up
- Verify your disk permissions
The latest Mac OSX update killed my system due to poor process design. It should, as part of the install ask the user to first verify their permissions and make sure they’ve backed everything up.
While we all know everyone will ignore the second piece of advice the first is not obvious to most (me). Apparently there is potential to install updates over the top of an OS with improper permissions, this can send the machine into a tailspin and put you in a whole world of pain.
Luckily, and very smugly, I had recently started using Apple’s Back-Up software that comes bundled with a .Mac subscription, so I didn’t actually lose that much. The pictures of my family, those files from yesteryear and of course all my movies and music were safe.
Yay! Gooooooo Back-Up.
But come on Apple, why on earth doesn’t the update software process ask users to perform certain tasks or in the case of permissions, make sure that they do it. I could have lost everything.
I couldn’t believe that I was back in OS 8.x territory trying to zap PRAM, use Safe Mode, enter system commands and all that. It’s not bee something that I’ve had to do since upgrading to OSX as OSX has been a solid platform with very little going wrong.
Someone will probably reply and say that the two incidents are not connected (HD failure and the updates killing my system), but I really think that they are.
Who’s at fault? Me for not knowing to verify? Apple for poor process design? Or the air hostess who made me turn my laptop off?
My money’s on the hostess. She had that look in her eye.
Continue reading ‘The Day Mac OSX Died’