4) When prompted, I entered my Apple ID information that was used to purchase and download OS X 10.7 Lion and allowed the OS X upgrade to proceed to completion. I then had a fresh version of OS X 10.7 Lion installed on my Mac. Wait until the processing is done and when the processing is finished, restart your Mac. (If this method didn’t work for you, we recommend you to re-install Mac OS X using the second method below.) Second Method – Re-install Mac OS X. Power off your Macbook or iMac completely. The installation was successful without any issue, and the Mac Mini is working perfectly fine until mid-October. All update was done. In October, I attempted to install MacOS Catalina through 'macOS Catalina Patcher' but no success (by both upgrade and clean install). I did not partition my new drive, I erased and formatted in MAC OS Extended (Journaled) only. I still could not get the original disk that came with the macbook Air to install. Thanks for the key to eject the disk. The Snow Leopard 10.6 disk installed properly, I've just completed the Time Machine restore and I think everything is good. 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.
- Mac Os X Could Not Be Installed On Your Computer No Packages Were Eligible
- Mac Os X Lion Could Not Be Installed Because The Disk Is Damaged
- Mac Os X Could Not Be Installed Video
- Mac Os X Could Not Be Installed As A
- Mac Os X Could Not Be Installed On Your Computer
- Mac Os X Could Not Be Installed
Here in Belgium schools are locked down due to #coronavirus. With the school of my two oldest kids now switching to remote teaching, I took the time to set up my old MacBook Pro (model late 2008) for my two oldest kids to use. That didn’t go without any hiccups though: the OS X installer refused to install …
The MacBook I had shelved a long time ago was still running OS X Mavericks. As that version was quite showing its age – and didn’t seem to support 2FA for use with my Apple ID – I decided to upgrade it to El Capitan, of which I still had the installer app lying around. I opened up the installer, it prepared some things, and nicely asked to reboot. Upon reboot the installer was ready to install, but when actually starting it greeted me with this error message:
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.
Uhoh! Restarting the MacBook, as suggested, did nothing: the installer kept showing that same error message. Trying to change the startup disk to get back into Mavericks (by pressing
⌥+R upon starting the machine) also didn’t help, as I could only launch the installer and a recovery partition. Yes, the machine was actually stuck in a loop where it would only launch the installer and the installer wouldn’t install.
With a Google Search Coupon in hand I found that the installer refuses service because the certificate it was signed with (some time back in 2015, when El Capitan was released) got expired by now.
Thankfully one can easily circumvent this expiration by simply changing the date of your system. You can do this before starting the installer, or through a Terminal if the installer is already loaded (as it was in my case).
- In the OS X Installer, choose Utilities > Terminal.
date 020101012016and press Enter.
- Quit Terminal and reboot to retry the installation.
💡 In this particular Terminal you’re running as
root, so no need for
sudo here 😉
Here the date is being set to Feb 1st, 2016. You might need to tweak the date a bit depending on when you downloaded the installer originally (as it might be signed with a different certificate). Be sure to set it no earlier than the release date of the OS X version you’re trying to install.
💡 The syntax for the
date command is a bit counterintuitive. Choosing your own date will require some puzzling from your end:
Mac Os X Could Not Be Installed On Your Computer No Packages Were Eligible
Later versions of OS X, such as High Sierra, have become a bit smarter: they give you the warning upfront – when first launching the
Installer.app – instead of after having prepared your disk for installation.
~Did this help you out? Like what you see?
Thank me with a coffee.
I don't do this for profit but a small one-time donation would surely put a smile on my face. Thanks!
To stay in the loop you can follow @bramus or follow @bramusblog on Twitter.I've recently posted some more tips on using Cassandra on Mac OSX: Cassandra on Mac
If you don't already have homebrew then install it from here.
Then it as simple as:
brew install cassandra
This doesn't install the python driver for the cqlsh command line tool. To do this install it first install python if you haven't got it already:
brew install python
This should have also installed pip - the python package manager - so you can then install the cql python module:
pip install cql
Now try and start cqlsh
You might get this:
Python CQL driver not installed, or not on PYTHONPATH.
You might try 'easy_install cql'.
Mac Os X Lion Could Not Be Installed Because The Disk Is DamagedOne second didn't I just install the cql module?
This could be because the Python in your path is the Mac OS X version. Not the version you installed with home brew that has cql. I fixed this by adding /usr/local/bin to the start of my PATH as that is where the brew Python executable lives:
Unless you've started cassandra the next time you try cqlsh you'll get:
Connection error: Could not connect to localhost:9160
Now if you do a brew info on cassandra:
brew info cassandra
To have launchd start cassandra at login:
ln -sfv /usr/local/opt/cassandra/*.plist ~/Library/LaunchAgents
Then to load cassandra now:
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.cassandra.plist
Unless you are going to use cassandra a lot I wouldn't set it to load on startup as it does use a reasonable amount of memory. Instead to just start it off:
launchctl load /usr/local/opt/cassandra/homebrew.mxcl.cassandra.plist
Finally cqlsh should connect to cassandra:
Connected to Test Cluster at localhost:9160.
Mac Os X Could Not Be Installed Video[cqlsh 3.0.2 Cassandra 1.2.5 CQL spec 3.0.0 Thrift protocol 19.36.0]
Use HELP for help.
Or if you prefer the older cassandra-cli interface to cassandra:
Connected to: 'Test Cluster' on 127.0.0.1/9160
Welcome to Cassandra CLI version 1.2.5
Mac Os X Could Not Be Installed As AType 'help;' or '?' for help.
Type 'quit;' or 'exit;' to quit.