Apple's macOS 27 beta changed how the boot picker recognizes valid OS volumes, leaving Asahi Linux partitions invisible and unbootable on Apple Silicon. The data is intact, but the Asahi team is warning users to hold off on the upgrade until a fix arrives.
Apple's macOS 27 made its debut at WWDC this week and shipped almost immediately as a public beta. For most Mac owners, the headline story is what the release means for aging Intel hardware. For the much smaller community running Linux on Apple Silicon, the news is more immediate and more disruptive: install the beta, and your Linux installation simply stops showing up.
The Asahi Linux team, which maintains the leading port of Linux to Apple's M-series chips, says macOS 27 "changed how the boot picker and Startup Disk application detect valid OS boot volumes." The practical result is that an existing Asahi partition no longer appears as a bootable option. The operating system is still installed, the data is still on the disk, but the firmware-level tooling Apple uses to present boot choices no longer recognizes it.
![]()
What actually changed
To understand why this matters, it helps to know how Asahi coexists with macOS in the first place. Apple Silicon Macs do not use a conventional BIOS or a standard UEFI setup that lets you install whatever you like. Booting an alternative operating system depends on Apple's own boot picker and the way macOS labels and validates boot volumes. Asahi installs alongside macOS rather than replacing it, and it relies on that boot picker treating its partition as a legitimate startup target.
When macOS 27 altered the logic that decides which volumes count as "valid OS boot volumes," the Asahi partition fell outside the new criteria. It is not deleted, corrupted, or wiped. It is invisible to the mechanism that would otherwise let you select it at startup. That distinction is important: this is a detection problem, not a data-loss problem.
The team's guidance
The advice from the Asahi developers is direct. Do not upgrade to macOS 27 until the issue is resolved. If you want to try the beta anyway, the team says you must keep a working fallback in place first. Their recommended approaches are to install a secondary copy of macOS 26 before touching the beta, or to install macOS 27 itself on a separate volume so that a known-good stable macOS remains available.
The team has also updated the Asahi installer to refuse to run on macOS 27 for the time being, closing off a path that would otherwise leave new users stranded. And they have set a firm boundary on support: "we will not support users who have installed the macOS 27 beta without ensuring at least one stable version of macOS is installed." That is a reasonable line to draw. Beta operating systems are unfinished by definition, and running one without a tested recovery path is a choice that carries its own consequences.
For anyone who already upgraded and watched their Linux install vanish, the reassurance is worth repeating. The Asahi team wrote: "If you have already upgraded to the beta and noticed that your Asahi partition has disappeared, do not stress. Your Asahi partition is still there, and you have not lost any data."
Accident or intent
The obvious question is whether Apple deliberately moved to block alternative operating systems on its hardware. The Asahi team is not treating it that way. Because macOS 27 is still in beta, the change is plausibly an unintended side effect of reworking the boot volume validation rather than a targeted effort to lock out Linux. Beta cycles routinely surface this kind of regression, which is exactly what the testing period is meant to catch. The team has filed a bug report with Apple, the standard route for getting a beta-stage regression addressed before the final release ships.
That optimism is grounded in history. Asahi has spent years reverse-engineering Apple Silicon and has generally managed to adapt as macOS evolved. A boot picker change that breaks detection is the sort of thing that can often be worked around once the new behavior is understood, either through a fix on Apple's side or an adjustment in how Asahi presents its partition.
Where Asahi stands
This lands during a rough stretch for the project. Asahi has weathered a leadership shake-up and the departure of several prominent developers, including the loss of its GPU specialist and an earlier exit by the project lead following disputes over Rust in the Linux kernel. Those changes raised real questions about momentum.
Even so, the project keeps shipping. It released Fedora Asahi Remix 44 in April and remains the most complete option for running Linux on Apple hardware. You can follow the project's progress and installation guidance at the official Asahi Linux site, and the source and tooling live on the Asahi Linux GitHub organization.
The takeaway for current users is simple and practical. If you depend on Asahi Linux, treat macOS 27 as off-limits until the team confirms a fix, and never install a beta operating system without a tested fallback already in place. This is a bump in the road for the project, not a dead end, and the most likely outcome is that boot detection gets sorted out before macOS 27 reaches general availability.
Comments
Please log in or register to join the discussion