"An error occurred while preparing the installation. Try running this application again." while installing macOS Ventura
bcamargogui opened this issue · comments
OS related issued, please help us identify the issue by posting the output of this
uname -a
Linux gbc-HP-250-G8-Notebook-PC 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 9 15:34:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
; echo "${DISPLAY}"
:0
; echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs
1
; grep NAME /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
; df -h .
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p2 234G 84G 138G 38% /
; qemu-system-x86_64 --version
QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.15)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
; libvirtd --version
libvirtd (libvirt) 8.0.0
; free -mh
total used free shared buff/cache available
Mem: 15Gi 6,4Gi 491Mi 503Mi 8,5Gi 8,1Gi
Swap: 2,0Gi 250Mi 1,8Gi
; nproc
8
; egrep -c '(svm|vmx)' /proc/cpuinfo
16
; ls -lha /dev/kvm
crw-rw----+ 1 root kvm 10, 232 nov 14 15:39 /dev/kvm
; ls -lha /tmp/.X11-unix/
total 8,0K
drwxrwxrwt 2 root root 4,0K nov 14 15:19 .
drwxrwxrwt 21 root root 4,0K nov 14 16:38 ..
srwxrwxr-x 1 gbc gbc 0 nov 14 15:19 X0
srwxrwxr-x 1 gbc gbc 0 nov 14 15:19 X1
; ps aux | grep dockerd
root 2291 2.9 0.4 1980936 68368 ? Ssl 15:19 2:20 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
gbc 10408 0.0 0.0 9212 2560 pts/1 S+ 16:38 0:00 grep --color=auto dockerd
; docker ps | grep osx
b77de8f687e6 sickcodes/docker-osx:ventura "/bin/bash -c 'sudo …" 59 minutes ago Up 59 minutes 0.0.0.0:50922->10022/tcp, :::50922->10022/tcp vibrant_khayyam
; grep "docker\|kvm\|virt" /etc/group
kvm:x:109:gbc
docker:x:999:gbc
libvirt:x:139:gbc
libvirt-qemu:x:64055:libvirt-qemu
libvirt-dnsmasq:x:140:
Evidence
Several attempts, I'm having the same error message here. I was able to install the other images without any problems.
This might be the same issue as #511 .
Try opening the menu Window -> Installer Log, then set "Show errors only".
I'm having a similar issue here too.
- One thing I am noticing is this worked pretty seamlessly for me previously on an Intel CPU, but for this AMD Ryzen 7 PRO 7840U the issue came up (not sure yet if the two are related).
- Looking up the specs for the CPU
AVX2is supported.
It looks like the primary error in the screenshot below is from OSISHelper:
-[OSISHelper blessUpdateBundleAtPath: ... :] failed to copy /Volumes/MacSSD/macOS Install Data/UpdateBundle/AssetData/.boot/Firmware/System/Library/CoreServices/bootbase.efi`
I've tried this a few times and always get the same result (APFS and for macOS Extended Journaled). Plenty of disk space here as well.
I thought disk space the culprit, but now that I'm trying again, I'm still having an issue. Same as above. The file bootbase.efi exists at /System/Library/CoreServices/bootbase.efi
If I open a terminal, I get the following:
Hi, I am facing the same problems. While I have installed more than 10 virtual systems before. Before the current error, I installed the system a month ago. The configuration of the command has not changed, I have been writing them down and re-calling them.
Perhaps something changed in the Ventura installation file itself?
https://mrmacintosh.com/macos-ventura-13-full-installer-database-download-directly-from-apple/
11/07 install assistant has been updated with a new build of the system. Is there any way to change the build?
I'll bet that's what the issue is. I'm not sure I know well-enough about this to do so. Boy if I knew how, I would.
Try opening the menu Window -> Installer Log, then set "Show errors only".
JTLYK legacy patcher with opencore upgrading with monterey to latest version on sonoma in theory should work, some guy on the discord said it does, but personally I tried and havent been able to mount a virtual disk ("the usb installer")specifically to hold the mac installer with opencore. If you know how to this should be straight forward, and less complicated than trying to solve this issue. Apple seems like they have been on their toes when it comes to updating the installers
Let me know if you would like a more detailed explanation about my suggestion but I cannot help after you try to use open core as I am unsure how to mount it like i said.
And to be clear there are plenty of videos of people using opencore but on real devices not on VM, so if you do know how to do it using a docker container feel free to share a tutorial
Does anybody know if there's a way to put a different InstallAssistant.pkg into the image?
Monterey Docker VM has an issue for some reason with Wireshark #681 .
https://mrmacintosh.com/macos-ventura-13-full-installer-database-download-directly-from-apple/ 11/07 install assistant has been updated with a new build of the system. Is there any way to change the build?
@sickcodes hi, maybe you'll check it out?
Have the same problem. Issue is failed to copy ... bootbase.efi.
Tried already with docker on a SSD disk and also with a normal HD disk. Could it be possibly be an issue with the PC firmware (e.g: boot security ?) Have used this:
docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
-e GENERATE_UNIQUE=true
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist'
sickcodes/docker-osx:ventura
Any ideas?
The same issue exist also on Ventura. Always: failed to copy ...bootbase.efi.
Make sure you're doing an offline install using an image that matches your CPU architecture.
I was able to fix it by following these steps
https://discussions.apple.com/thread/8287410
and formatting the install disk as JHFS+ instead of APFS
@stonedDiscord diskutil cs did not recognize verb "createVolume",how to fix it ？
I was able to fix it by following these steps https://discussions.apple.com/thread/8287410 and formatting the install disk as JHFS+ instead of APFS
This didn't work for me. I got an error related to the disk not being formatted for APFS, and the installer couldn't download a package.