Can't Boot into Asahi

Hello!
I haven’t booted into Asahi in a while, after I updated to some version of macOS 14 (not 14.5, little bit later than that probably, and am in macOS 15 now), I was unable to boot into Asahi for some reason. When I boot into it, my laptop just restarts and goes back into macOS.

Here’s the curl alx output:


I’m guessing I press p and repair?

Please let me know what additional information I should provide.

Thanks!

1 Like

yes, repair the installation. This is unfortuantely an issue which occurs sometimes: Troubleshooting :: Fedora Docs

It’s not clear what kind of information would be useful at this stage. Thanks for reporting.

2 Likes

Thanks, repairing worked, thankfully!

1 Like

I’m not sure if the same issue or just similar, so I’ll include it here rather than clutter the main list of threads. (If it turns out to be a separate issue, I’ll create one then.)

After installing macOS Sequoia on a separate volume, I find that Asahi Linux won’t boot on my MBP. I’ll attach an image showing the console output I see.

(I’m afraid it’s all Greek to me.)

I’m completely at a loss. What should I do? Please help.

Thank you.

That looks like one of your partitions is missing or corrupted. You could try entering the maintenance console and then running blkid and cat /etc/fstab to get some information on the state of things.

Thanks @marcan. I

Attached is an image showing the output of blkid (whoever he is) and cat /etc/fstab.

Any thoughts? Do you have a Rosetta stone to decipher this stuff?

Looks like your Linux root/home filesystem partition is completely gone, so whatever you did in macOS removed it…

You’ll have to wipe the remaining Linux partitions (follow our guide) and reinstall.

Goodness. All I did was install macOS Sequoia. I should’ve known it would behave like an utter beast, demolishing anything in its path. Fee-Fy-Fo-Fum.

(Apple is releasing utter garbage these days. This boot stuff is nothing. You should see the new Reminders app.)

Back to this problem, here’s the chronology: I had Monterey co-existing happily with Fedora. Then I created a new volume on which I installed Sequoia. It trampled over Asahi Linux.

So, @marcan, looking ahead to installing Asahi Linux again, will the Asahi Linux installer respect my existing boot volumes? (Monterey and Sequoia?)

Huge thanks.

The installer does not care about any macOS installs you have, other than to offer you to resize any relevant containers (if you installed both macOS instances into separate volumes on the same default container, as seems to be the case, there will be no difference).

You might want to post the output of diskutil list on macOS so we can better see exactly what state your disk is in.

Aside: I’m confused about how you had macOS Monterey. The minimum required version for installing Fedora Asahi has been 13.5 Ventura since months before the official release.

Thanks, @marcan. Clarification: The factory OS on this MBP is Monterey. I created a separate volume and installed Ventura or Sonoma – I can’t recall which. From there I installed Fedora.
I later upgraded Ventura/Sonoma to Sequoia. That’s when the anvil dropped out of the sky.

This is the output from that diskutil list command:

/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: Apple_APFS_ISC Container disk1 524.3 MB disk0s1
2: Apple_APFS Container disk4 370.8 GB disk0s2
3: Apple_APFS Container disk2 2.5 GB disk0s3
4: EFI EFI - FEDOR 524.3 MB disk0s4
5: Linux Filesystem 1.1 GB disk0s5
(free space) 119.5 GB -
6: Apple_APFS_Recovery Container disk3 5.4 GB disk0s6

/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.5 GB disk2
Physical Store disk0s3
1: APFS Volume Fedora - Data 802.8 KB disk2s1
2: APFS Volume Fedora 1.1 MB disk2s2
3: APFS Volume Preboot 198.5 MB disk2s3
4: APFS Volume Recovery 809.2 MB disk2s4

/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +370.8 GB disk4
Physical Store disk0s2
1: APFS Volume Monterey HD 15.4 GB disk4s1
2: APFS Volume Preboot 7.4 GB disk4s2
3: APFS Volume Recovery 1.8 GB disk4s3
4: APFS Volume Monterey Personal Data 101.7 GB disk4s5
5: APFS Volume VM 20.5 KB disk4s6
6: APFS Volume Sequoia - Personal Data 41.6 GB disk4s7
7: APFS Volume Sequoia 10.7 GB disk4s8
8: APFS Snapshot com.apple.os.update-… 10.7 GB disk4s8s1

Kind regards,

Yeah, that “(free space)” is where your Linux root partition used to be, unfortunately. I have no idea how that happened (I’ve updated many machines to Sequoia myself without issue).

Luck of the draw perhaps. Thanks for giving this your time @marcan. Last question before I attempt to reinstall Asahi Linux – is it possible to use a dynamic volume (like macOS) or must the linux volume be a fixed size?

Many thanks.

Never mind – the interweb has confirmed that it needs to be a fixed volume. Right ho.

The question you want to ask is whether Linux can share an APFS volume with macOS, and the answer is no because there is no upstream APFS support in Linux and using barely tested downstream APFS implementations as your main root filesystem would be quite crazy right now. Maybe some day though.

Linux does have dynamic volumes (btrfs) just like APFS on macOS and in fact we use them to split the root and home filesystems (similar to macOS). You just can’t share space between macOS and Linux because they use different filesystems.