Menu

Refind can't boot into MacOS after BigSur update

Jakbo Wolf
2021-08-19
2021-08-21
  • Jakbo Wolf

    Jakbo Wolf - 2021-08-19

    Hello there,

    i installed refind in order to dual boot linux ans macOS. My machine is a Mac mini 2018 (with t2 chip) updated to BigSur. Both the preboot and the "showtools firmware" option don't boot into macOS. I also tried to reset the nvram and to install refind again but with no results. Has anyone managed to boot into BigSur on a t2 mac with refind? Let me know!

     
  • joevt

    joevt - 2021-08-20

    Try RefindPlus to see if it has the same limitation?

    Maybe we need a feature to use BootNext method instead of direct StartImage for each scanned EFI option.

     
  • Jakbo Wolf

    Jakbo Wolf - 2021-08-20

    Hi,

    i was unaware of RefindPlus. I could try it out! Which configuration would i need to enable?

     
  • joevt

    joevt - 2021-08-20

    He has a Mac mini 2018. Does it require those apfs options?

     
  • dakanji

    dakanji - 2021-08-20

    sync_apfs only acts if there is an APFS volume to sync as determined at runtime. (Big Sur qualifies)
    supply_apfs only acts if there is a need for loading APFS drivers as determined at runtime.

    Either way, they will only be used as needed at runtime, so easier to just set them.

    Also others that might come across this thread later might have something different.
    Setting the two tokens will work for such and for the OP.

     
  • Jakbo Wolf

    Jakbo Wolf - 2021-08-20

    Ok, thanks! i will try it.

     
  • Jakbo Wolf

    Jakbo Wolf - 2021-08-20

    I installed RefindPlus and enabeld "sync_afps" and supply_afps" and refind now boots BigSur successfully! Thanks for the help!

     
    👍
    1
    • joevt

      joevt - 2021-08-21

      Can you boot BigSur without those two options?

       
      • Jakbo Wolf

        Jakbo Wolf - 2021-08-21

        Yes! Just disabled both asps options and it still boots successfully. Must be something else in RefindPlus that solves the problem for me.

         
        • dakanji

          dakanji - 2021-08-21
          Just disabled both options and it still boots successfully.
          

          Cool. Keep those two settings on regardless as they only kick in when needed which you might find useful in future.

          "sync_apfs" should already be, as it gives one properly labelled option for APFS volumes

          Must be something else in RefindPlus that solves the problem
          

          A ton of bug fixes have gone into RefindPlus with a lot of them coming after an audit by joevt. Aim is to ultimately feed stuff upstream into rEFInd if possible.

           

          Last edit: dakanji 2021-08-21
  • joevt

    joevt - 2021-08-21

    Ok, I read the config.conf info for sync_apfs. Maybe a better name would be group_apfs or consolidate_apfs or filter_apfs because it removes some redundant apfs options or options that might not work. sync_apfs implies that apfs can be out of sync which doesn't make sence for what it does.

    I don't think sync_apfs and supply_apfs would affect the OP's issue. He did say he tried the Preboot option which is the option that sync_apfs would expose to the user. But maybe some other change in RefindPlus might work.

     
  • dakanji

    dakanji - 2021-08-21
    I don't think sync_apfs and supply_apfs would affect the OP's issue
    

    Yeah. Explained earlier that setting those two were not purely for the OP's specific setup; with the point made that they kick in only as needed.

    Actually, but for philosophical reasons of wanting RefindPlus items to be actively enabled and to be otherwise essentially equivalent to rEFInd in terms of features, those two would have been backend defaults that are not user configurable.

    sync_apfs implies that APFS can be out of sync
    

    Having two options for booting the same thing, with one that will always fail depending on Mac OS version, does mean something is out of sync. This is moot though, as it will become a backend default once the implementation is fed into rEFInd as hoped ... or perhaps once the APFS data volume can be reliably detected, regardless the assigned name.

     

    Last edit: dakanji 2021-08-21
    • joevt

      joevt - 2021-08-21

      I think we're talking symantics here. Being out of sync implies there's a way to make it in sync so that it will work. But it will always fail. It's not syncing that is required here. It's more like filtering (removing the option that won't work in the case of Big Sur and later, or is redundant in the case of Catalina and earlier). I agree it's a moot point (but maybe there's a case for not doing the filtering for redundant options that can work).

       
  • dakanji

    dakanji - 2021-08-21

    It is semantics indeed.

    In terms of the key issue, the point is that even with versions that will work, you still get two entries and have to filter the PreBoot volume out. With this on, you get just one which is far better IMO.

    Additionally, even with older versions of Mac OS, you need to use the PreBoot volume if you have Filevault on.

    All of those considerations are out with this set. You get one boot option that works in all instances.
    You don't get two options to boot Catalina, one of which will fail if you have Filevault on, in the Apple Picker.

    BTW, this mapping to Preboot is what OpenCore and Clover do as well ... it is not an optional in those. It is just the way it should be and the only reason it is optional in RefindPlus is purely philosophical as mentioned.

    It might be best to take further discussion on RefindPlus internals to our other channel though.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.