Preserved restore bundle in preboot is missing

[Vrownie]

Hi, I ran into this error trying to install Asahi Linux using the alx.sh script:

Setting the new OS as the default boot volume...
Bootability failed Error Domain=BYErrorDomain Code=112 "Preserved restore bundle in preboot is missing" UserInfo={BYErrorHint=VolumeInvalid, NSLocalizedDescription=Preserved restore bundle in preboot is missing}
Failed to run bless. Press enter to try again.

I am running macOS Tahoe 26.2 with a M1 Pro Macbook Pro.

Appreciate your help! Thank you.

[codingvivi]

getting the same error on an M1 Max mbp. same macOS version...

[codingvivi]

i fixed it by

1. reviving my mac from dfu mode (using a second mac, a usb c cable and apple configurator)
2. removing all of the partitions created for the installation
3. rerunning the installer with curl https://fedora-asahi-remix.org/install | sh (note that curl https://fedora-asahi-remix.org/install | sh will try to install 0.7.8 vs 0.7.7 with curl https://alx.sh | sh . idk if that made a difference after step 1 & 2, but before it did NOT)

i am not sure why this worked. research and a bit of gemini prompting made it seem like the issue was that the issue lies in a missmatch between your current OS version and your OS restore version but i cant confirm rn.

do you have access to a second mac to revive via apple configurator?

and if no is there a missmatch between your versions when you run the installer and it prints your system info? if there is i think there are ways to reinstall macos without losing all of your data. doing so from offline recovery didnt seem to solve problem but ive read that doing it from online recovery or via the cli should update the files in question. i havent tried either out tho youd need to check yourself

[Vrownie]

i fixed it by

1. reviving my mac from dfu mode (using a second mac, a usb c cable and apple configurator)
2. removing all of the partitions created for the installation
3. rerunning the installer with curl https://fedora-asahi-remix.org/install | sh (note that curl https://fedora-asahi-remix.org/install | sh will try to install 0.7.8 vs 0.7.7 with curl https://alx.sh | sh . idk if that made a difference after step 1 & 2, but before it did NOT)

i am not sure why this worked. research and a bit of gemini prompting made it seem like the issue was that the issue lies in a missmatch between your current OS version and your OS restore version but i cant confirm rn.

do you have access to a second mac to revive via apple configurator?

and if no is there a missmatch between your versions when you run the installer and it prints your system info? if there is i think there are ways to reinstall macos without losing all of your data. doing so from offline recovery didnt seem to solve problem but ive read that doing it from online recovery or via the cli should update the files in question. i havent tried either out tho youd need to check yourself

Hi codingvivi, I'm glad to hear you got it to work. I have access to another m1 machine at the moment but want to make sure that this method would be safe for my main MacOS install (since it is my daily driver). I'm not too familiar with this DFU process so would appreciate your pointer. Thanks!

[Vrownie]

Also seems like #405 could be a possible duplicate.

[thom-cameron]

I had the same issue on my macOS Tahoe Macbook Air.

I was able to work around it by downloading the installer script at https://alx.sh and making it target an older version of the install script.

I just changed the PKG_VER="$(curl --no-progress-meter -L "$VERSION_FLAG")" line to PKG_VER="v0.7.6".

Hope this helps the people currently struggling with the issue if not the debugging efforts from the maintainers.

[inubass]

Tried both workarounds mentioned by @thom-cameron and @codingvivi to no avail.
M1 pro 13 on Tahoe.
Tried it a few times, removed the created partitions, the whole dance.

[codingvivi]

Tried both workarounds mentioned by @thom-cameron and @codingvivi to no avail. M1 pro 13 on Tahoe. Tried it a few times, removed the created partitions, the whole dance.

@inubass I assume you tried running a reinstall as well right...Did you delete cached time machine backups before doing your partition? I remmeber doing that for storage reasons, but if there really is some version missmatch between current system and restore stuff, maybe that will help...

@Vrownie those are two things you could try if you're uncomfortable DFUing (and haven't done so yet), delete locally cached time machine backups and then see if a full reinstall fixes the error for you. A reinstall after booting into recovery didn't do anything for me, I was about to reinstall via the terminal (I think using softwareupdate, just see if you can get it to print --help to see how) next, before I decided to try DFU.

If you wanna go for DFU revive I think you should be fine, but be sure to back up your device with time machine beforehand and do NOT cancel or abort any of the steps, ESPECIALLY after it downloaded the stuff it needs to get started. I think I read that Apple Silicon is unbrickable, but don't just take my word for it please.

If you get an error message at the end of the revive process about how it failed and you have to do a full wipe to use your mac again, try booting and logging in anyway. I did so and my system was completely fine, thats actually when i was able to install.

I'm sure you come across this walkthrough but just in case you haven't, here it is. Sorry my reply is coming so late and not more helpful but I've been super busy

[inubass]

Thanks for the response! But I have no time machine backups.
I only own one mac, so would rather try to avoid having to go through DFU ^^.
Deleted every partition possible, no timemachine snapshots. Same issue.
Please let me know if there's any information or log I can provide to help troubleshoot this issue.

Thanks!

(I can see the asahi linux disk shown in the startup disk options on the settings, but I'll leave it like that until braver souls figure out the issue)

[mskiptr]

Just FYI, here's yet another case where using https://fedora-asahi-remix.org/install instead of https://alx.sh seems to have made this go away.

[maximilian-neu]

Running into the same issue with macOS Tahoe 26.2 on M1 Air.

[maximilian-neu]

Running into the same issue with macOS Tahoe 26.2 on M1 Air.

I ended up going through DFU and used https://fedora-asahi-remix.org/install instead, which resolved the issue. I suspect the MacOS recovery partition version not exactly matching my OS version might have been the culprit.

[weber-moritz]

Hi!
I had the same issue. MacBook Pro M1
after a lot of testing around we just wiped and completely reinstalled mac os with a second mac (using the DFU mode and the Apple Configurator). We installed the newest version of MacOS (26.2 right now) and this also reset the recovery mode, thus solving the version mismatch.
Before this i had just wiped the mac in verson 12 (Monterey).

Problems i had:
The Error 112 after just installing the video codecs, when the installer want to set Linux as the default boot option.

What i tried:
I tried to change the version like @thom-cameron said without luck, error 112.
I also tried the other installer like @codingvivi suggested, without luck as well, same error 112.
I also tried to repair the installation, same error.
I also tried booting into Linux anyways but step 2 could not start as it said something along the lines of: "cant get local policy of Volume".

What solved the Problem:
Putting the M1 in DFU mode and connecting it to another mac, then using the apple configurator in "recover" mode to update to the newerst mac os Version 26.2

I hope this might help someone. Strange bug. In general the installation was crazy easy once it worked and i was confused if i had done something wrong or skipped something.
Thanks to everyone for their work.
I really did not like using macOs for the few minutes i had to. At least its unix like so the terminal felt familiar :D