myspaghetti / macos-virtualbox

Push-button installer of macOS Catalina, Mojave, and High Sierra guests in Virtualbox on x86 CPUs for Windows, Linux, and macOS
GNU General Public License v2.0
13.48k stars 1.11k forks source link

"fs1 is not a correct mapping" #101

Closed Black00Z closed 4 years ago

Black00Z commented 4 years ago

Hello there and sorry for causing trouble again, using the newest version of the script got me stuck at the "mapping table". fs1 is not a correct mapping . Seems like the issue similar to #32 but there wasn't really a solution so I opened a new issue. I'm on Linux Mint, trying to boot Mojave. :)

Mapping_table

I am not 100% sure but this time as well it didn't prompted a license agreement. It still booted up though.

myspaghetti commented 4 years ago

No trouble, I want the script to work, and you're helping.

The latest version of the script (0.75.3) skips the license prompt.

Black00Z commented 4 years ago

I'm glad I can help in any kind of way. I'm on version 0.75.3 of the script.

myspaghetti commented 4 years ago

Looks like the installer failed to start. You should have seen this in the guest: VirtualBox_macOS_19_09_2019_14_31_15 Then the EFI APFS drivers are copied to the target VDI (which they were), and then the installer starts (which it didn't).

If you didn't see Preparing: 100% and Restarting... then the installer failed to copy the installation files to the target, or even partition the target by the looks of it.

Black00Z commented 4 years ago

I'm sorry but it never showed this window. I am trying to download everything the 3rd time and I will report back asap.

EDIT: I'm gonna update my VirtualBox again. The changelog looked promising. Seems like some major Linux Kernel problems as well as some MacOS things have been fixed.

Black00Z commented 4 years ago

Got High Sierra running. It opened the "Preparing.." windows and booted by itself!

But Mojave is still not woking. I think I will try it another time the next days. Thanks again for the help :)

myspaghetti commented 4 years ago

Because the checksums on the host were correct but the checksums on the guest were incorrect, it's very likely that the files got corrupted when transferred from the VISO to the VDI. I was able to make the installer fail but I'm unable to get the files on the VDI to be corrupt. You can start another issue or reopen this issue if you can provide a method to reproduce the issue. I'm closing this issue until new information is available.

myspaghetti commented 4 years ago

You might also want to post on issue 84 - "starttoinstall" fails