
# USE THE DATA YOU WROTE DOWN FROM “gpt -r show disk0”. # Make a new one to start with some fresh values. # Get rid of the GPT on the disk we are recovering. From here we are doing tables, not disks / data.

We are replacing / destroying a table here, but not the data. I rewrote this once with the correct Apple Index 2 data but did not create a new table (leaving the rest of the broken bits broken). Each field is supremely important.Ĭontents: C12A7328-F81F-11D2-BA4B-00A0C93EC93BĬontents: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF The critical fields here are Start, Size, Index, and Contents. That is probably disk0.Ĭopy the following readout in your terminal for all entries bigger than “32”. Write down ALL of the above information for the disk you are after. I also found /dev/disk2 → /dev/disk14 to be tiny partitions- don’t worry about those. The graphical disk utility is useless because the disk / partition we want is unreachable(so it will say everything is great).įor me, I see disk0s2 is 180.6 gb. Restart the computer into internet recovery. Get the computer with a text editor open. I actually waited 2.5 hours twice on separate attempts before I cleared these.įollow these Apple links to perform these operations: How to recover a garbled GPT table for Mac OSX:Ĭlearing these actually made accessing internet recovery (how we get to a stand-in OS with a terminal) dozens of times faster. But, in the meantime, I still wanted to try again…. She was interested in this problem, and we scheduled a larger block of time. I scheduled an Apple support session with a phone rep, which after around 45 minutes of actually productive troubleshooting ideas (none helping though) was forwarded to a senior supervisor. They declared this machine bricked and offered to wipe it. I brought the machine to the local university repair.

What it did show was (wait for it) Clover bootloader of all things, with a single windows boot camp icon (nothing in there either). My 2015 computer’s next move was to reboot- only to find essentially no partitions of memory… at all. The crash results? Toasted GPT tables all around. This is a fairly mundane operation that I do now and again, and is a ongoing fight to keep at least a few gigs of space free for actual work on precious 250gb Mac SSD. My computer recently crashed very, very hard, while I was removing an small empty alternative OS partition I no longer needed.
