VDI files not created (incorrect device number)
Smons opened this issue · comments
Hi,
I am currently trying to install BigSur in VirtualBox using your scripts.
I am stuck because the script won't create the VDI files because it tries to use /dev/disk1 which is wrong. The sparseimage images are actually mounted here:
- macOS-VM.sparseimage on disk10
- the APFS container inside disk10 on disk11
- macOS-VM.efi.sparseimage on disk12
Could it be a regex capturing only one digit?
Log file below.
To Reproduce
Steps to reproduce the behavior:
After the first failure, I deleted the .sparseimage files and relaunched the script so it could re-create them.
Additional context
OS: Catalina 10.15.7 (19H1030), 8GB RAM on iMac 21.5" late 2012
Log file for my latest attempt:
I deleted the .sparseimage files so the script would re-create them
Collecting system information...
[2022-04-14 12:29:22] Running checks...
[2022-04-14 12:29:22] .
[2022-04-14 12:29:22] Creating image '/Users/steff/VirtualBox VMs/macOS-VM.dmg' (takes a while, version 16.8.40, will need sudo)...
[2022-04-14 12:29:22] already exists.
[2022-04-14 12:29:22] Creating iso '/Users/steff/VirtualBox VMs/macOS-VM.iso.cdr'...
[2022-04-14 12:29:22] already exists.
[2022-04-14 12:29:22] Creating VM HDD '/Users/steff/VirtualBox VMs/macOS-VM.vdi' (takes a while)...
[2022-04-14 12:29:22] .
[2022-04-14 12:29:23] Creating /Users/steff/VirtualBox VMs/macOS-VM.sparseimage...
created: /Users/steff/VirtualBox VMs/macOS-VM.sparseimage
[2022-04-14 12:29:25] Converting virtual macOS disk: /dev/disk1
Converting from raw image file="/dev/disk1" to file="/Users/steff/VirtualBox VMs/macOS-VM.vdi"...
VBoxManage: error: Cannot open file "/dev/disk1": VERR_ACCESS_DENIED
Disk /dev/disk1 ejected
[2022-04-14 12:29:26] Adding APFS drivers to EFI in '/Users/steff/VirtualBox VMs/macOS-VM.efi.vdi'...
[2022-04-14 12:29:26] .
created: /Users/steff/VirtualBox VMs/macOS-VM.efi.sparseimage
Volume on disk1s1 failed to mount
Perhaps the operation is not appropriate (kDAReturnNotPermitted)
If you think the volume is supported but damaged, try the "readOnly" option
cp: directory /Volumes/EFI/EFI/drivers does not exist
./runMacOSVirtualbox.sh: line 228: /Volumes/EFI/startup.nsh: No such file or directory
disk1s1 was already unmounted
Converting from raw image file="/dev/disk1" to file="/Users/steff/VirtualBox VMs/macOS-VM.efi.vdi"...
VBoxManage: error: Cannot open file "/dev/disk1": VERR_ACCESS_DENIED
Disk /dev/disk1 ejected
[2022-04-14 12:29:28] Creating VM 'macOS-VM'...
[2022-04-14 12:29:29] already exists.
[2022-04-14 12:29:29] Adding APFS drivers to EFI in '/Users/steff/VirtualBox VMs/macOS-VM.efi.vdi'...
[2022-04-14 12:29:29] .
Volume on disk1s1 failed to mount
Perhaps the operation is not appropriate (kDAReturnNotPermitted)
If you think the volume is supported but damaged, try the "readOnly" option
cp: directory /Volumes/EFI/EFI/drivers does not exist
./runMacOSVirtualbox.sh: line 228: /Volumes/EFI/startup.nsh: No such file or directory
disk1s1 was already unmounted
Converting from raw image file="/dev/disk1" to file="/Users/steff/VirtualBox VMs/macOS-VM.efi.vdi"...
VBoxManage: error: Cannot open file "/dev/disk1": VERR_ACCESS_DENIED
Disk /dev/disk1 ejected
[2022-04-14 12:29:30] Starting VM 'macOS-VM'...
[2022-04-14 12:29:30] .
Waiting for VM "macOS-VM" to power on...
VM "macOS-VM" has been successfully started.
[2022-04-14 12:29:33] Press enter to stop the VM and to eject the installer medium (to avoid an installation loop for macOS < 10.16)...
[2022-04-14 12:29:33] .