If you don’t have an OS installed anymore, reboot on your OS X install disk built with DiskMaker X, open Terminal and type:.If you did not erase your Mac and its OS is still working fine, reboot on its hard drive, open System Preferences > Date and Time, uncheck Automatically set up date and time and set the date 13th of February 2016, then disconnect from network and reboot.There are three ways to avoid this problem : This is not a problem with DiskMaker X per se, but with the installers provided by Apple. It may have been corrupted or tampered with during downloading.”ĭue to an expiration of OS X App Store certificates, installers of OS X downloaded prior to February 14th of 2016 can’t be used to re-install OS X without encoutering this error. I encounter this message: “This copy of the Install OS X application can’t be verified. I will try to fix it in a future version (if I manage to get why this happens sometimes in some configurations… “This copy of the Install OS X application can’t be verified. If a folder (not a disk !) is named “Install macOS Sierra”, “Install OS X Yosemite”, or “Install OS X El Capitan”, delete the folder (you may need admin rights, thus type your admin name and password).in Finder, click on Go > Go to Folder menu.Basically, a false mount is a folder created with the same name as your Install drive, and that makes the Install disk adopt the same name with “1” at the end, i.e. This happens sometimes when creating the install disk because a false mount is created as some point. When creating the Install disk with DiskMaker X, I encounter this error message : “The disk could not be created because of an error: An error occured: -10006.” I plan to add a feature to check the size of the installer before trying to build an install disk in the not-too-distant future. The idea is to use an app that will force download of the full macOS install app. To be sure to download the full macOS installer, have a look here for macOS High Sierra or here for macOS Mojave. Check its size : if the installer is about 20 MB large, it’s a stub which can’t be used with DiskMaker X. Second, it may happen that your macOS Install app (either High Sierra or Mojave) is not complete. ”įirst, please update to DiskMaker X 7.0.1 or DiskMaker X 8.0.1. Finder got an error: Can’t set alias \”Install macOS High Sierra:Install macOS High Sierra.app\” to. When using DiskMaker X 7 for High Sierra, I encounter this error message : “The disk could not be created because of an error: An error occured: -10006. Beware that some of these versions must be purchased (basically, all macOS versions before 10.9). Where can I get a previous macOS Install app ?Ĭharles Edge nicely compiled the list of download links for previous versions of macOS installer apps. Parenthesis are difficult to deal with when integrating shell script code in AppleScript, so the best way to avoid this bug at this time is to just remove the parenthesis from the path of the app. Sh: -c: line 1: syntax error: unexpected end of file” numberīasically, there is something in the pathname of your macOS Install app that DiskMaker X does not like, and most of the time the issue is parenthesis because you renamed the app or included it in a folder that has the version or build number between parenthesis, i.e. I will try the Nuke-N-Pave with a 10.12.3 installer at some point, now that the machine is running the official release version of the OS.Syntax error near unexpected token `(‘ Or this error :Įrror “sh: -c: line 0: unexpected EOF while looking for matching `” Just to be safe I re-ran the 10.12.3 installer. When I rebooted the 2016MBP, everything was working fine including the TouchBar. I then let my 2015 MBP boot from the 2016 drive to complete the install and the setup assistant. What I ended up doing - and I am surprised that it worked - is I connected the 2016 MBP in target mode to my 2015 MBP and installed the latest version of Sierra. I wiped the entire drive while booted to Internet Recovery. However I still have no idea why the Internet recovery would fail. This time I only erased the partition as I'd heard that the Recovery Partition had something to do with the TouchBar OS, so I figured it best to not erase the entire drive.īecause the Recovery Partition was 10.12.4 and I was trying to install 10.12.3, may have been why it initially failed. When I decided to nuke-n-pave I just did what I always do boot my USB 10.2 installer, erase the drive and reinstall. OK, so I realized what MAY have been the problem.
0 Comments
Leave a Reply. |