eprigorodov / mkosxinstallusb Goto Github PK

In readme.md it would be nice having a list of required dependencies. They are:

• dmg2img
• multipath-tools
• hfsprogs
• rsync

Hi there,

I tried this with the El Capitan DMG downloaded from Apple. The file is named InstallMacOSX.dmg (not InstallESD.dmg, I have searched google for this file but the one offered by Internet Archive is just the same "InstallMacOSX.dmg" file I already have from Apple).

When I convert to .img and mount, I don't have a "BaseSystem.dmg" file in the mounted dir, just a InstallMacOSX.pkg".... what did I do wrong? I don't have access to a Mac running MacOS, so I can't get any "InstallESD.dmg" from a system folder.

The message occurs when making a bootable drive using Linux for Catalina. Any ideas?

List of files on the drive: filelist.txt

After remove, the result image is bootable?

This is just a suggestion.

In my case, I had used the USB stick for other stuff and was previously imaged with dd, so despite the stick being physically 8Gb, my Linux was only seeing it as a much smaller disk (2Gb). This caused issues later on when rsyncing the Packages folder onto the stick as it was running out of space!.

The solution for me was to do this to my stick before running the mkosxinstallusb script:

sudo dd if=/dev/zero of=/dev/sdb bs=1M status=progress
sudo sync

That made it be an 8Gb disk again.

Maybe mkosxinstallusb could incorporate this step before running sgdisk -o $stick_dev to make the process more robust for some corner cases. Something like this:

[...]
echo "\n# partitioning USB drive"
if [ -b "$stick_dev" ]
then
    for device in $(lsblk -lnp -o NAME "$stick_dev" | tac)
    do
        umount -l "$device" 2>/dev/null || true
    done
fi
dd if=/dev/zero of=$stick_dev bs=1M status=progress
sync
sgdisk -o $stick_dev
sgdisk -n 1:0:0 -t 1:AF00 -c 1:"disk image" -A 1:set:2 $stick_dev
sync
[...]

HOW TO REPRODUCE:

1. Reset the Mac SMC, by on boot up holding the keys Command (⌘), Option, P, and R.
2. With a MacOS USB try to install the system.

RESULT:
The installer complains that it's unable to continue due to missing packages.

SOLUTION:
In readme.md indicate the fix:
"If the installer is unable to find the packages, in the utility "Terminal" enter (using two digit fields): date [month][day][hour][minute][year]"

REFERENCES:
https://discussions.apple.com/thread/7251878

I know that the readme states:

High Sierra installers are not supported yet,

But do you know of a manual way of creating the bootable USB?

#4 contained some assumptions about the target device that make script fail when working with the USB drive (e.g. regexp that parses kpartx output).