Double check the date is now manually set (make a new folder and check its creation date) Manually set it and then reboot your system. Here we want the year for Sierra to be last year (2016). Are you using Apples Time server or manually setting it? You'll get the error like this if the date is incorrect (month & year). You'll need to check your date setting within Prefs. So if you try installing an older OS release when a newer one is out you need to back wind the date to the year the OS was introduced If it fails again you can be pretty rest assured at this point that it's hardware based, but if it persists across different hardware even on a secondary temp user, it could be an issue with your OS.Apple is being very sneaky!! To help push people to the newer OS's they have a time bomb in the OS installer. So it sounds like either the ports on the Mac you're using to build the Bootable Drive are fried/having issues, or the drive you're using to build these images should be trashed and a new one purchased.īefore swapping any hardware though, create a new user and try building the Bootable Drive on that user. The error that you're seeing on the Terminal method is a "Couldn't Unmount Disk" error, which is usually due to corrupted/broken hardware or the Drive is being listed as "busy" in the OS. Using this method and making sure that I have the freshest installs never yields an error for me, and I can use the Terminal method if this one doesn't, as the Terminal method is very solid.
I also recommend using the fastest speed drive you can (if on 2016 or later machines, get a USB-C Flash Drive).
He makes installer builders that allow for the install of Later OS'es on older hardware through a series of patches, but it works just fine and bypasses a couple of the cert checks when you build the installer.Īlways make sure that before you do a bunch of boot imaging you have the newest version (or freshly downloaded version) of the OS Installer, and also make sure that you're using 16GB Flash Drives or Larger for the bootable image. If you really want a GUI based one that actually does work, check out dosdude1's OS Patcher software. I've found that the Terminal mode is most reliable, but it doesn't end up making everything look nice. It's unreliable, and doesn't fully complete. First, I suggest stopping using DiskMakerX.
0 kommentar(er)
