Os X Could Not Be Installed No Packages

OS X could not be installed on your computer. No packages were eligible for install. Contact the software manufacturer for assistance. Quit the installer to restart your computer and try again. The attempt to install data.table failed due to a problem compiling the package from source. Before trying to fix that, though, you might try installing the binary (already compiled) version that's available — it's not that much older than the source version. To try this, run: install.packages('data.table', type = 'binary').

; Date: Sun Oct 16 2016

Tags: Mac OS X

A key step for upgrading the disk on a MacBook Pro is to install a new operating system on the new drive, and then use Migration Assistant to copy over the old data. Depending on how you went about the work, installing Mac OS X on the new system may give you a message: OS X could not be installed on your computer. No packages were eligible for install.

This is what it looks like in the installer. Upon seeing this I went 'HUH?' because the installation was from a thumb drive I'd used many times to install Mac OS X (El Capitan) successfully.

The above image came from an attempt to install El Capitan. I just got the following message, macOS could not be installed on your computer, while trying to install macOS High Sierra.

In both cases there was the same cause. In the El Capitan case, as I say in the next paragraph, the hardware clock had reset to zero because it did not have a battery pack. In the High Sierra case, I had performed a hardware reset of the computer in an attempt to fix a bootup problem. I had found advice to disconnect the battery, the power supply, then hold down the power key for a few moments. In both cases the hardware clock had been reset to zero, and macOS refused to boot.

After some yahoogling (duckduckgoing) I came across a simple solution. This particular computer had been running with no battery, and therefore the hardware clock was reset to zero, and Mac OS X had a test against that condition.

We've discussed elsewhere the process to install Mac OS X onto a computer, and transfer information from an old drive. It's during that process when the above message appears. A couple steps prior is where you can take action to correct the problem.

At this step, click on Terminal ...

Os X Could Not Be Installed No Packages

Then change the operating system date.

When running this particular Terminal session, you are ROOT meaning you can change anything on the computer. Normally we type 'date' at the command line just to find out the current day/month/year/time. But, the date command can be used to change the time registered in the system clock.

As I said above, for this particular computer the system clock had been reset to zero because the battery pack had been changed. In fact, the computer had run without a battery for many months because the old battery had gone bad.

As you see on the screen, the date had been January 1, 2001. I then changed the system date to the current time as of the writing of this posting.

To understand the second command, go to a terminal window and type 'man date'.

In the synopsis section you'll see this as an option for the 'date' command:

That's a little obtuse, but further down the manpage is this key:

In other words, the date code for this purpose is month-day-hour-minutes-year ... hence, that's what I entered and it changed the system date to match.

Afterward I closed the Terminal window and was able to successfully install Mac OS X on the computer.

Please enable JavaScript to view the comments powered by Disqus.

When you’re booting your Mac from the recovery partition and are planning to reinstall OS X, you might be met by the following message:

An error occurred while preparing the installation. Try running again

Now, if you haven’t used your Mac for a while, the error might be caused by an incorrect system date setting. You can check this by going to utilities and opening the terminal. Once in the terminal enter the following command and hit return/enter:

The result of this command will be the date that the system currently has been set to. For some reason, it might have been reset to 2001, in which case we need to set it to the right date. To do this, we enter a new command. This command will be entered as follows:

Every bracket should be replaced with a two-digit number based on UTC time. Below you see what the command should be for your current time and date – . To avoid trouble with timezones, we will use UTC time instead (). Which means, you can just enter it exactly like this:

Enter the command and hit return. You can then check if it was set correctly by running the first command again. If the date was wrong, it was likely that which caused the error, and after you quit the terminal it should be able to install OS X just fine.

Buying a Tesla? Use my referral link at the purchase of your new Model 3, S or X and get 1500km / 1000mi of free supercharging!Get free supercharging

Related

Os X Could Not Be Installed No Packages

Tesla Summon Emergency Stop

TL;DR While using Summon via the app, pressing any button on the key fob will stop the car faster due to less latency. The Summon feature that comes with AutoPilot equipped Tesla's is pretty great when you need to park in a tight stop. It allows the car to park itself…

Os x could not be installed no packages were eligible

Tibber – the Electric power company for the future

Mac Os Cannot Be Installed

Electric power companies, in general, are pretty much the same. Tibber however, is unlike any electricity company I had seen before. They try to utilise the data we get from smart devices, which they also sell, to save electricity, money and the environment, as well as improving comfort. It’s a…

Tesla Autopilot 2.0 vs. 1.0 – status

How Do You Fix No Packages Were Eligible For Install

There is a question that a lot of Tesla owners are asking these days, is Autopilot 2.0 as good as 1.0 yet? At this point the two generations are pretty much equal as far as Autosteer goes – even though some other features are still lacking. Look below for what…