Resolving the M1 Mac Partition Lock: How I Bypassed Error -69877 Using Terminal

Introduction:The Stuck Apple Silicon SSD Challenge

Every day in the tech lab brings a fresh batch of devices, but certain cases really give a hardware and software forensics specialist the perfect chance to put their brain to the test. Last night, exactly one of those cases landed on my desk—an Apple M1 MacBook.

The customer had been trying to install an operating system on their own. But because the installation crashed midway—likely due to an unsupported OS build—they tried to force-erase the SSD directly from Disk Utility. That’s exactly when everything went sideways. The screen kept throwing a stubborn pop-up:

"Error: -69877 - The volume on disk0 couldn't be unmounted because it is in use by process 0 (kernel)"

When the customer handed the MacBook over to me, it was essentially in a soft-brick loop. 

Technical Analysis: Diagnosing the "Orphaned Free Space" on M1

My first move was to boot into Recovery Mode, fire up the Terminal, and run "diskutil list". As soon as the partition map populated the screen, the core architectural mess became glaringly obvious. Out of the main 251 GB internal drive, nearly 245 GB of the data volume had vanished entirely, leaving behind nothing but raw free space. In the tech world, we call this "Orphaned Free Space."

Why Does the M1 Kernel Lock the Disk Utility Wipes?

Because the OS installation had failed halfway through, the primary APFS container scheme was completely shattered. Apple's M1 Silicon architecture features incredibly tight security, meaning the moment the core file system goes haywire, the backend kernel (process 0) locks down the drive to protect the hardware. It goes into a strict write-locked state, refusing to unmount or format through standard graphical utilities. 

The Solution: Bypassing the Kernel Lock via Target Terminal Command

On an Intel Mac, clearing a disk lock like this is relatively straightforward. But on Apple Silicon, you can't just force your way in; you have to outsmart the architecture. I went straight to the root level via Terminal and pushed this exact command:

diskutil addPartition /dev/disk0s1 APFS MacintoshHD 0

The moment I hit Enter, the magic happened. The Terminal executed the task flawlessly, outputting step-by-step:

* Started partitioning on disk0
* Modifying partition map
* Mounting disk
* Finished partitioning on disk0

It ran completely clean, without a single error. 

Why Forcing Apple_APFS_ISC Breaks the Deadlock

Here is the technical reality of why this worked: by targeting disk0s1—which is Apple's dedicated Apple_APFS_ISC system container—and forcing it to allocate a new APFS container, it completely bypassed the kernel's active deadlock. The command instantly restructured the stranded 245 GB of orphaned free space back into an official, recognized APFS volume, forcing the drive to mount properly.

Conclusion: A Clean macOS Installation and Final Verdict

With the kernel lock broken, I jumped back into Disk Utility. It instantly allowed a clean, error-free wipe of the entire drive. From there, I initiated the macOS installation, and the progress bar filled up smoothly without any further interruptions.

For anyone servicing Apple Silicon storage, here is the ultimate takeaway: a locked M1 drive doesn't mean dead hardware. When the standard UI locks you out, hitting the root level with the right targeted Terminal commands can bypass the kernel restrictions and restore the storage layout back to factory perfection.