Handling a Crashed Startup Disk Gracefully

4 minute read
| News

Rants & Raves
Episode #272

Last Thursday morning I tapped the keyboard to awaken my Mac and nothing happened. So, I held down the power/eject key until I heard the comforting startup chime and soft whirring of fans.

My comfort was short-lived. When I tried to launch an app—any app—I got a message that the app was damaged and couldn’t be opened. I noticed that all of the previously-colorful icons in my Dock were replaced with gray question marks, telling me that the Dock couldn’t locate the apps.

Then I tried the usual tricks one tries…

I remained calm while performing the usual tricks and techniques you perform when your Mac goes wonky:

  • I rebooted. No help.
  • I rebooted again, just in case. Again, no help.
  • I tried zapping the NVRAM by restarting while pressing Command + Option + P + R. That didn’t help,
  • I tried a safe boot by restarting while pressing the Shift key. That didn’t help, either.
  • I booted from a clone of my startup disk (cloned the night before), and then used Carbon Copy Cloner to clone it back onto my (original, internal) startup disk.
  • But, that somehow made things worse. When I restarted the MacBook Pro, the Apple logo and progress bar appeared briefly, and then the screen went black and stayed that way.

The fans were still whirring, so I thought something might be going on behind the scenes. I waited an hour but nothing changed.

I assumed the operating system was hosed, so I booted into macOS Recovery mode by restarting while holding down Command + R. Then, I first ran Disk First Aid on the recalcitrant disk. When it passed the tests, I reinstalled High Sierra.

Holding my breath, I rebooted (for about the twentieth time), only to see the Apple logo (briefly), followed by the black screen of death. Again.

Then I got serious…

Then I got serious. I put my MacBook Air into Target Disk mode and connected it to the MacBook Pro via Thunderbolt, and restarted the MacBook Pro while holding down the Option key. I selected the MacBook Air (in Target Disk mode) as the startup disk for the MacBook Pro and ran my go-to third-party disk utilities — DiskWarrior and Drive Genius. Neither one found any issues with the SSD.

At this point I decided to erase the recalcitrant drive and start from scratch. So, I restarted into Recovery mode, used Disk Utility to erase the troubled drive, and installed High Sierra.

Bingo. It turns out that erasing the disk before installing High Sierra was the solution.

It took the better part of four hours before everything was back to normal. But, because I had good backups and stayed calm, I was back to work within a few hours without losing a drop of data.

It wasn’t fun, but in retrospect, it could have been a lot worse.

Epilog

On Sunday, it got a lot worse. I walked in to find my Mac as frozen as a popsicle. No mouse, no keyboard, nothing worked. I long-pressed the power key and hoped for the best.

What I got was the worst. Since a picture is worth a thousand words, these pictures will save you having to read a 3,000 word description of the errors I encountered Sunday afternoon and well into the evening.

In other words, my Mac no longer remembered me or my password and all attempts to reset the password failed. The disk was encrypted with FileVault, so I didn’t have a lot of hope. I’d have been happy to erase the disk again and restore from a backup or clone.

But, because the disk was encrypted, and in spite of my knowing the password (I’m sure I typed it properly most of the 50 or so times I tried), I couldn’t even erase it and start over. I tried starting it in Target mode and booting from the MacBook Air, but it remained stubbornly unable to recall my user account or FileVault passwords. Ergo, I still couldn’t use it or erase it. The one time I managed to get Disk Utility to try First Aid, I got an ominous error message.

GoogleFu failed to uncover a fix, so late Sunday night I threw in the towel and called Apple. My tech was great and in about 30 minutes we determined it would require in-store diagnostics to proceed any further.

The next available Genius Bar appointment at either Apple Store in Austin was Tuesday at 6PM.

Can you imagine being without your Mac for two days? It was unthinkable to me, so I was at the closer Apple store when it opened Monday morning at 10AM.

The first walk-in appointment was at 11:20AM.

Good news/bad news

Then, good news! I related my tale of woe to another excellent technician. He ran a few tests and determined that the problem was a swollen battery and it would cost only $200 to fix. I was relieved because Apple’s price for replacing the 1TB SSD was over $900!

Bad news: This store didn’t have the part in stock.

Good news: Austin’s other Apple store, about 30 minutes away, had the part.

Bad news: They had the part but they also had a 7-10 day backlog for in-house repairs.

Good news: They could expedite a depot repair and get it back to me by Wednesday. That’s today.  I picked it up and am restoring it as I type this on my MacBook Air.

I bought the MacBook Air for travel and testing, not to use as a daily driver. Between its tiny 11-inch screen, wimpy processor, inadequate RAM, and lack of graphics processing power, it’s been a challenge. But, for the most part, I’ve gotten by for three days with data from my backup disks and a backup Mac (i.e. my MacBook Air).

The one lesson I learned is that this kind of disaster — one severe enough to cause a day or two of lost work — can happen at any time. And because I have such an obsession with redundancy and backups, I didn’t lose a drop of data.

But, I did lose almost two days of work to troubleshooting and trying to make my MacBook Air do things it wasn’t designed to do.

In other words, I could probably achieve zero downtime if I bought a third Mac with roughly the same specs as my daily driver (the MacBook Pro).

I’m not sure it’s worth it or that I can justify the expense. That being said, I never thought much about buying a third Mac before, but I have been thinking about it a lot lately….

One last thing: The care I received from Apple was first-rate from start to finish. Everyone I worked with or talked to went out of their way to reassure me they were doing everything possible to get the issue resolved quickly..

I cannot imagine how horrible the experience would have been had my Mac been a Windows laptop from Best Buy.

6
Leave a Reply

Please Login to comment
5 Comment threads
1 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
6 Comment authors
vpndevjhorvaticCudaBoyThrasherBob LeVitus Recent comment authors

This site uses Akismet to reduce spam. Learn how your comment data is processed.

  Subscribe  
newest oldest most voted
Notify of
Member
jhorvatic

Ram would have caused the OS to fail to install as it is like having short term memory loss. It would load the OS install into ram but then forget what it loaded and the install would fail.

CudaBoy
Member
CudaBoy

From the symptoms I was voting for a bad RAM chip which would stop a successful boot no matter what you tried.
But please, a cheap shot on Windows when you have no proof this type of “swollen battery” problem has ever happened on a windows flaptop? C’mon! Apple clones pay a PREMIUM over equivalent and better ‘Doze units, you’d think Apple has figured out temperature technology or battery tech by now. SO, what caused the problem so none of the other Apple clones have to go through this??? Not good. 💽

vpndev
Member
vpndev

Cuda: a couple of things …
1. Li-ion batteries are Li-ion batteries. It’s perfectly reasonable to assume that all laptops have this issue, in the same way that all phones do. As you imply, the frequency varies with quality, but they’re all subject to the issue
2. The ding was not on Windows per se but on BestBuy and its service. From what I understand, that criticism is not misplaced.

Thrasher
Member
Thrasher

Great article. I enjoyed following your diagnostic skills as you tired to solve the problem. Glad to see Apple techs were knowledgeable and able to work things out for you.

geoduck
Member
geoduck

From the symptoms I would have assumed it was the drive. Glad it was only the battery.
But how could a swollen battery cause the drive to flip out like that?