Monterey 12.2 bootable SD with createinstallmedia results in hang with prohibitory symbol

[eugenios]

Hi everyone,
I usually don't update macOS from SystemPreferences; I download the whole installer, create a SD bootable media by using the command /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia..., booting from the SD and the lunch the installation from there.

Never had an issue until I tried this with Monterey 12.2, which instead during booting process appears the prohibitory symbol.

iMac 19,1

anyone else?

eugenio

 

[BrianBaughn]

That's an uncommon method…so I don't know. Where did you get the macOS installation app you used?

Also, I'm wondering what's your reasoning behind this method?

 

[eugenios]

That's an uncommon method…so I don't know. Where did you get the macOS installation app you used?

Also, I'm wondering what's your reasoning behind this method?

Hi,
This method one from far in the past due to failed update installations (I don' recall which OSX version) and from then I always performed an installation from a full installer, booting from another media than the one I'm going to install to.

 

[white7561]

Hi,
This method one from far in the past due to failed update installations (I don' recall which OSX version) and from then I always performed an installation from a full installer, booting from another media than the one I'm going to install to.

I also always install using a full installer . To make sure it replaces every system files Incase there are corrupted files. Cause they do happen. Also to make sure the USB installer for Emergency works fine .

I did mine (12.2) using a USB which works fine on my M1 Mac. Make sure your media is GPT and not MBR

 

[chabig]

I also always install using a full installer . To make sure it replaces every system files Incase there are corrupted files.

There is no reason to try to update from an external installer. You're creating more work for yourself, for no benefit. It's no longer possible for the system to contain any corrupted files, because the system is verified, sealed, and is on a read-only volume. If your Mac, running Big Sur or Monterey with Secure Boot enabled, boots normally, then its System volume is in perfect condition.

How macOS is more reliable, and doesn’t need reinstalling

How APFS, the boot volume group, hashes, and Secure Boot all combine to guarantee the integrity of your system, and save you trouble and work.

eclecticlight.co

 

[white7561]

There is no reason to try to update from an external installer. You're creating more work for yourself, for no benefit. It's no longer possible for the system to contain any corrupted files, because the system is verified, sealed, and is on a read-only volume. The seal is verified at boot and if it fails, the system won't boot.

Well don't they seal the system after the delta updates? Which means if there are corrupted changes inside. It wouldn't matter if it's sealed or not right? It would still boot.

Although it's not really more work for me since i always make a bootable installer just in case. So by upgrading using it I got the benefit of testing if it works fine or not. Better safe than sorry. IMO

 

[DeltaMac]

I don't think that I would do a macOS install from an SD card -- too unreliable, in my experience. A USB flash drive is what I would recommend.

 

[chabig]

Well don't they seal the system after the delta updates? Which means if there are corrupted changes inside. It wouldn't matter if it's sealed or not right? It would still boot.

No. After each update, the system volume is guaranteed to be bit for bit identical to that prescribed by Apple. This is explained in the linked article.

 

[white7561]

No. After each update, the system volume is guaranteed to be bit for bit identical to that prescribed by Apple. This is explained in the linked article.

Well nice then. I am using Reduced Security tho to run kexts. AFAIK it does something that allows it to downgrade. Don't know if it still compares the full system hash against the Apple server but yeah.

In the end it's not really more work for me as I said because I do make a recovery installer in case of emergency. And by doing this I'm basically testing the installer to make sure it works fine

 

[Fishrrman]

Don't use an SD card.
Use a USB flashdrive instead, 16gb or larger.

I would also suggest that you try either of these free apps to create the bootable USB drive:
- Install Disk Creator
- Diskmaker X

But then, the advice that chabig offers in reply 5 is what I'd try.

 

[eugenios]

Basically I don't trust Apple anymore.
From a version to the following I often find simple things not supposed to be updated that don't work anymore, so since macOS has become so complicated the fact that something is broken is very plausible.
Like in this case for example the issue is how the "Recovery System" installed on external media (SD Card) is not working it's a clue that they don't have their stuff in control.