From da0e98d435a5a0a27077886deca76cfc8492470f Mon Sep 17 00:00:00 2001 From: Hector Martin Date: Oct 13 2024 14:26:26 +0000 Subject: troubleshooting.adoc: Add note on a weird corner case --- diff --git a/modules/ROOT/pages/troubleshooting.adoc b/modules/ROOT/pages/troubleshooting.adoc index b702282..c791933 100644 --- a/modules/ROOT/pages/troubleshooting.adoc +++ b/modules/ROOT/pages/troubleshooting.adoc @@ -67,6 +67,8 @@ It is also possible for a system firmware upgrade to trigger an incompatibility The process for both of the above situations is the same. First, follow the steps in <> to boot into recoveryOS (preferred) or macOS, and open a Terminal. Ensure you are connected to the internet, and then run the {variant-name} installer again, using the instructions in the xref:installation.adoc[Installation] page (or the steps available on https://asahilinux.org[asahilinux.org]). Once the installer starts, one of the available options should be to `Repair an incomplete installation` (`p`) or `Upgrade m1n1 on an existing OS` (`m`). Choose the appropriate option and follow the instructions to upgrade or reinstall m1n1 stage 1. +If you need to reinstall m1n1 stage 1 or otherwise reset the Boot Policy but the installer does not prompt with either of the above two options, you can run `bputil -f` and then select the UUID corresponding to the installation that you wish to repair (this will be displayed when you start up the installer, in the partition list). Follow the prompts to reset your Boot Policy, which will erase the m1n1 bootloader and place the installation into the "incomplete" state. Once this is complete, you may follow the steps above again to launch the installer and select the "Repair" option, which should now be available. We have heard some reports that this situation can occur after machines are sent to Apple for servicing. + == Recovering an unbootable machine [[machine-recovery]] If your machine is stuck displaying an exclamation mark icon (laptops and iMacs) or SOS LED blink pattern (desktops), you may need to perform a DFU Revive or Restore. To determine if this is necessary, first try to boot using both the current paired recoveryOS and the System recoveryOS.