Open PeterSuh-Q3 opened 4 days ago
PeterSuh-Q3
commented
4 days ago The singularity is that the size of this 27th build 24B2083 image should be larger than the previous version, but it is smaller.
The 24th build 24B83 image is being downloaded now, and it is larger at 13.5GB.
PeterSuh-Q3
commented
4 days ago I downloaded it directly from Apple.
softwareupdate --list-full-installers softwareupdate --fetch-full-installer --full-installer-version 15.1
The image I received this way was fine.
gregneagle
commented
4 days ago Sounds like you have a workaround for your needs. (I don't use createinstallmedia for anything here).
Curious if macOS installers downloaded via the MIST tool have similar issues. https://github.com/ninxsoft/Mist
grahampugh
commented
4 days ago Don't use 24B2083, that's the forked build for the new M4 Macs. Use 24B83.
gregneagle
commented
4 days ago So then also curious what the build was for the installer he got with softwareupdate --fetch-full-installer --full-installer-version 15.1. Betting it also was 24B83.
PeterSuh-Q3
commented
3 days ago It seems to be a known issue in the Apple community.
https://discussions.apple.com/thread/255849666?sortBy=rank
I contacted Apple directly.
I tried to proceed with the solution I found on Google, which was to grant "Full disk access" to Terminal, but it was successful half the time and failed half the time.
The two Macs I'm working on are using Sequoia 15.1.
On the first PC I'm writing this report on, the message was initially "Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle" "The bless of the installer disk failed."
and when I granted "Full disk access," the message changed to this again "Couldn't extract BaseSystem chunklist to path: /Volumes/Install macOS Sequoia/BaseSystem" "The bless of the installer disk failed."
On the 2nd PC it started from the last message above and after granting "full disk access" everything was resolved.
The situation on the 1st PC is still persisting. I think APPLE should answer why.
grahampugh
commented
3 days ago Looking in the posts in that Apple discussions list, it looks to me like all the people having the problem are using the incorrect version of 15.1 for the Mac they are trying to restore. Lots of people trying to restore on the new M4 mini using the regular installer, which won't work. But, as Greg says, if you use softwareupdate --fetch-full-installer you'll get the build appropriate for the device it runs on. Of course if you then make a bootable USB installer of that and try to use it on a device that needs the other fork, you'll have problems.
mist-cli has a --compatible option that will only show (or download) installers compatible with the device it's running on. My fork of installinstallmacos.py also checks compatibility and will show which installers are compatible with the device it's running on.
Hello.
I am creating a boot by selecting the Sequoia 15.1 27 image.
The dmg file is created without any problem when downloaded.
After copying .app to Application, I created a boot with the following script.
Other images (Big Sur ~ Sonoma) were created without any problem up to the MacOS installation boot.
Sequoia 24 and 27 images show the same 15.1 version. Should I use 24 instead of 27?