2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

[rthpjm]

Attached is the file, i had the same error. I tried the command just as you had it and it said the "-d was an invalid option". Deduced that I just needed the "-i off" to turn off the indexing. When I did that, it said indexing disabled, so I figured that's what we were looking for.

When I tried to go right into the code ./createpikeinstallmedia /Volumes/Untitled\ 1, it didn't take the first time around, so I reformatted, replaced the El Cap app in my applications to start fresh. So I started from the beginning of the code, starting with the sudo -s. No dice...

As for the Macintosh HD, that was a partition that I created. I just installed an SSD and it's titled Macintosh SSD, this contains all of the important stuff. Could something in the script be looking for "Macintiosh HD" and be a source of the error? I'm guessing not, just typing out loud.

USB info is also attached. Had to modify the code slightly as the -all didn't work.

Okay,

I just installed Snow Leopard, and tried on my machine. I get the same error. It looks like you need to be at Lion (or better) for Apple's createinstallmedia tool to work. It must utilise function calls that don't exist prior to Lion...
So yes, you will need to upgrade to Lion (or better) first....
[doublepost=1478132520][/doublepost]

I have a Mac pro 1,1 with a successful installation of El Capitan running for a few months. I must apologize for my ignorance but i let an update over write my boot files(I think). My previous operating system is not booting either. It boots into a disk utility and of course I have no knowledge of any of this and don't have time machine set up or any kind of back ups and the only thing I can really do is go to my terminal window, which is how installed elcapitan the first time. I thought I could just go to the same script that I did before for the pike files but I can't get past the first sudo command either because I can't remember the proper user name or that it's not working. Can I use a Mac book pro to replace or delete files to let it boot again. ? I'm sry for such a dumb problem

Did you use my pikify tool set?
If you did, then you should be able to boot into the Recovery partition.

• Restart
• When you hear the chime, hold down Apple-R
• Release when you see the Apple logo

It will usually boot and show what looks like the start of the install process.
Go directly to the Utilities menu, and select Terminal

I am going to assume your main Mac OS X partition is called Macintosh HD, if it is called something else, amend the commands below to suit.

Type into the (Recovery partition) Terminal

cp /com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/System/Library/CoreServices
cp /com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/usr/standalone/i386

Now quit the terminal (cmd-Q)

You can run the Startup Disk selection from here (it's under the Apple menu), choose your normal volume, and click restart

 

[TLMuse]

W
Hello Tom,

From your description, in my experience there are 2 likely culprits.
Most likely: a failing hard disk
Next most likely: the PRAM battery is failing

I think I've ruled out both possible causes.

I replaced the PRAM batter with a brand new one. The old one measured 3.1V with a voltmeter, and well in the "Good" region with a battery tester that loads the battery according to size. After the replacement, the restart problem re-appeared.

I have two system partitions, on separate SSDs; the 2nd I keep in the Mac Pro for backups, and to enable restart in an emergency. Both drives have good SMART statuses. I powered down and powered up the Mac after removing each drive, and tried a restart with each of them. The restart problem persists regardless of which drive is in there. Safe boot (which runs first aid) does not remedy the problem with either drive. Unless both drives happen to be failing in the same manner at the same time, this seems to rule out a failing drive. BTW, these SSDs are from different manufacturers (Samsung & OWC).

Pressing the SMC reset switch inside doesn't help.

It seems the only thing that helps is removing power for an extended period of time (more than the 15 sec required for an SMC reset). As noted previously, leaving the Mac unplugged for an hour made it able to restart, although eventually (even within just a couple hours) the problem would reappear. Last night I tried unplugging it for 2 min (on the suggestion of a blog post claiming this is required for an SMC reset), and in fact it could restart successfully afterward. But I haven't repeated the experiment, so it may be a fluke.

Have you checked the Console app to review the system log? It may give you an idea why Safari is having trouble.

I didn't. I went ahead and removed the system drive, connected it to my RMBP, and re-installed 10.11.6 from the MAS installer. (I had previously tried re-installing from the recovery partition, but the Mac Pro would not allow a restart from either of my recovery partitions; I hadn't replaced their boot files so it's probably a moot point anyway.)

I installed all required updates from the MAS after booting on the RMBP. I ran your script to fix the recovery partition (thanks for that!). Then I manually installed a new boot file in /usr/standalone/i386.

When I first resurrected this Mac, I followed instructions to also install the new boot file in /System/Library/CoreServices. I was surprised to discover that, after the 10.11.6 reinstallation, there was no such folder on the system drive. I checked my most recent backup, and it's gone there, too. So I'm assuming this is not a problem, and that only the boot file in /usr/standalone/i386 needs to be replaced.

I moved the drive back to my Mac Pro. My first power-up started in the recovery partition, but I powered down and powered up again holding the Opt key, and the 2nd time it started fine in the new System partition, and I'm typing from it right now. Safari works, and all seems well for the moment.

I'm not sure what I'll do for the next security update, given my restart problem. I may move the drive to my RMBP for updates that require a restart. But I don't know if it will successfully boot there now that I've modified the boot file. Do you know?

PS: For the possible benefit of anyone with a similar Security Update problem: even after re-installing the OS, I couldn't get the update from the MAS. The store recognized it was needed, but would stall attempting the download (with a message saying "NaN GB..." was being downloaded, i.e., "Not a Number"). To get the download to work, I had to clear both the updates folder and the cache, following steps shown here:

https://www.cnet.com/news/tackle-a-hung-app-store-update-in-os-x/

 

[rthpjm]

When I first resurrected this Mac, I followed instructions to also install the new boot file in /System/Library/CoreServices. I was surprised to discover that, after the 10.11.6 reinstallation, there was no such folder on the system drive.

That doesn't sound right. There are lots of important files in /S/L/C (or did you mean there's no boot.efi file in that folder?)

 

[TLMuse]

That doesn't sound right. There are lots of important files in /S/L/C (or did you mean there's no boot.efi file in that folder?)

My bad! My system disk is named, well, "System", and when it was mounted on my RMBP, I looked at /Volumes/System/Library/CoreServices/ when I should have looked at /Volumes/System/System/Library/CoreServices/.

I just checked it on the disk I re-installed 10.11.6 on, and indeed CoreServices is there. There's also a boot.efi already there, with a creation date of this afternoon (when I first booted from it in the Mac Pro). It's identical (via "diff") with the one I installed in /usr/.../i386. Either it was left there from my original modification months ago (and touched today), or it was somehow automatically copied.

I'm still curious as to whether I'd be able to boot from this drive if I moved it to my RMBP, as an option for handling future restart-required updates. If you know, please respond. Thanks as usual for all your help!

 

[Mola55e5]

Okay,

I just installed Snow Leopard, and tried on my machine. I get the same error. It looks like you need to be at Lion (or better) for Apple's createinstallmedia tool to work. It must utilise function calls that don't exist prior to Lion...
So yes, you will need to upgrade to Lion (or better) first....
[doublepost=1478132520][/doublepost]
Did you use my pikify tool set?
If you did, then you should be able to boot into the Recovery partition.

• Restart
• When you hear the chime, hold down Apple-R
• Release when you see the Apple logo

It will usually boot and show what looks like the start of the install process.
Go directly to the Utilities menu, and select Terminal

I am going to assume your main Mac OS X partition is called Macintosh HD, if it is called something else, amend the commands below to suit.

Type into the (Recovery partition) Terminal

cp /com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/System/Library/CoreServices
cp /com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/usr/standalone/i386

Now quit the terminal (cmd-Q)

You can run the Startup Disk selection from here (it's under the Apple menu), choose your normal volume, and click restart

 

[alexholiday]

Okay,

I just installed Snow Leopard, and tried on my machine. I get the same error. It looks like you need to be at Lion (or better) for Apple's createinstallmedia tool to work. It must utilise function calls that don't exist prior to Lion...
So yes, you will need to upgrade to Lion (or better) first....
[doublepost=1478132520][/doublepost]

Thank you very very much! I stepped up to Lion, and it worked flawlessly. I officially have El Capitan loaded, and it runs great.

Thanks again! Have a good day.

Alex

 

[Dc2006ster]

Thanks to all the very clever folks that have made it possible for Mac Pro 1.2/2.1 owners to enjoy the latest operating systems. I am in awe of your skills.

I have no idea what is happening but can follow instructions and I used rthpjym's fix to install El Capitan. Amazing.

I used an external SSD instead of a USB which I think made the process faster but I forgot to make the modification that produces a black boot screen. Is it possible to make this change after El Capitan is installed and running?

 

[TO5]

Just gonna jump in here.....

I am so thrilled! I don’t know where to begin! This Thread about 2006/2007 Mac Pro 1,1 - 2,1 ….is sooooooo informative about extending the life of a very capable machine! For being the techie in my household, I was getting left behind with my ever so reliable 10.6.8 Snowy on my Mac pro 1,1 still doing everything I asked it to do, except be compatible with my iPhone 6. Hence getting left behind in the iOS world…stopped at 8.4.1 iOS.

The accolades and acknowledgements, the recognitions and thank you’s could take so much time to each and everyone of you who has contributed in large or small to this effort,...this machine. I love Apple, but more importantly I love the people that use them, keep them going, collaborate with each other to solve problems that sometimes understandably happen with a company that has to move forward. Some times we don’t agree with how and why they do it, but maybe it’s to get us users to collaborate collectively and use our extremely powerful noodles!



Ok…my question is;



I just completed a successful 10.11.3 EC install following post #1390 to the T. And installed boot64.v3.mpkg……everything seems to be working great.



Will I benefit to do the 10.11.6 update? if so, what precautions do I need to take before seeking out this update? And the recommended procedure. Then I will be at the OS limit of this Mac Pro 1,1’s capabilities.

Sincerely,

Jeff O

 

[TO5]

Thanks to all the very clever folks that have made it possible for Mac Pro 1.2/2.1 owners to enjoy the latest operating systems. I am in awe of your skills.

I have no idea what is happening but can follow instructions and I used rthpjym's fix to install El Capitan. Amazing.

I used an external SSD instead of a USB which I think made the process faster but I forgot to make the modification that produces a black boot screen. Is it possible to make this change after El Capitan is installed and running?

I think you want post #1391

 

[rthpjm]

Thanks to all the very clever folks that have made it possible for Mac Pro 1.2/2.1 owners to enjoy the latest operating systems. I am in awe of your skills.

I have no idea what is happening but can follow instructions and I used rthpjym's fix to install El Capitan. Amazing.

I used an external SSD instead of a USB which I think made the process faster but I forgot to make the modification that produces a black boot screen. Is it possible to make this change after El Capitan is installed and running?

Sure, copy the black version over the in use version (with the name change).

You should be okay to do this directly, but you may need to turn off SIP (or use the Recovery partition to make the change whilst you're there anyway).

 

[gybek]

(*Pardon, if this may be asked earlier on/elsewhere, I'm quite exhausted after doing all the upgrades and trying to research as much as I can to gotten to me to this point, lol.)

So, I'll try to keep this as concise as possible, lol.
Installed El Cap on my 1, 1 on an SSD. I had the two other, original drives, used for the Boot/Install drive for El Cap, the other I had made into a Time Machine backup of El Cap. Everything was working fine, (turning it off and back on again a few times once I had the install up and running) however, I left it off for a few days and when I went to go install the airport card, (the one that's compatible) the OS seemed to be in a loop. (I feel there's zero correlation to the install of the airport card and this loop). I'm also hearing my optical drive clicking, and seems to not be able to re-start if selected to within Recover, (so hard re-boot, only). But, something happened and I can't figure out how to prevent it from happening again.

To summarize my troubleshooting:

1. El Cap wasn't mod'd other than from the original hack, (it was only ever hardwired to the internet when Lion was on it)
2. went into recovery os; nothing is wrong with disks
3. tried to use time machine backup of El Cap I made; no luck
4. tried to use the El Cap Boot Drive to reinstall, (stalls out)
5. eventually, I wiped the SSD and re-installed Lion
6. also, wiped the other two drives and got a fresh copy of El Cap from my friends access to the App store and have re-pikify'd it, this time it's on a flash drive, however.

So, pictured below is what processes were happening at boot and I am hoping the fresh hacked boot and fresh Lion will fix this, but, I am afraid this boot loop will happen again, and I really wish for that not to happen.
It's been exhausting, for me physically, doing all this on my own, (course, though with the forums help to guide me, so THANK YOU very much, guys! ^_^ ) However, I am now just hoping there's a simple fix someone can offer for me, lol.

 

[TO5]

Anybody?

Ok…my question is;



I just completed a successful 10.11.3 EC install following post #1390 to the T. And installed boot64.v3.mpkg……everything seems to be working great.



Will I benefit to do the 10.11.6 update? if so, what precautions do I need to take before seeking out this update? And the recommended procedure. Then I will be at the OS limit of this Mac Pro 1,1’s capabilities.

Sincerely,

Jeff O

 

[hwojtek]

If you read this thread further, you'd find that installing 10.11.6 (including Safari 10.0.1 etc) does no harm and enhances your El Cap experience to the maximum, provided you took care of your boot.efi files not being overwritten by the update.

 

[TO5]

If you read this thread further, you'd find that installing 10.11.6 (including Safari 10.0.1 etc) does no harm and enhances your El Cap experience to the maximum, provided you took care of your boot.efi files not being overwritten by the update.

Ah...yes...thanks so much for the confidence booster to go ahead with the updates. I disabled (SIP) and did them one at a time ( 11.4/11.5/to max at 10.11.6 !!!
Had a little Restart issue after each update...when it went to restart...it couldn't. HD just kept clicking every 10 seconds or so. So I just held the power button until it shut off. Waited a few...then tapped the power button to turn it back on with no problems. Did a restart from the new updated version to make sure all's good...then proceeded to next update. It's almost like the boot64.efi wasn't getting reincerted from a restart, but was from a complete shut down. Just a guess on my part.

I really can't thank ALL of you enough! But please know this, that you ALL have helped one more person at this endeavor because of YOUR hard work and determination I have succeeded at this too. Thank you very much!

Sincerely,
Jeff O

 

[Mola55e5]

Okay,

I just installed Snow Leopard, and tried on my machine. I get the same error. It looks like you need to be at Lion (or better) for Apple's createinstallmedia tool to work. It must utilise function calls that don't exist prior to Lion...
So yes, you will need to upgrade to Lion (or better) first....
[doublepost=1478132520][/doublepost]
Did you use my pikify tool set?
If you did, then you should be able to boot into the Recovery partition.

• Restart
• When you hear the chime, hold down Apple-R
• Release when you see the Apple logo

It will usually boot and show what looks like the start of the install process.
Go directly to the Utilities menu, and select Terminal

I am going to assume your main Mac OS X partition is called Macintosh HD, if it is called something else, amend the commands below to suit.

Type into the (Recovery partition) Terminal

cp /com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/System/Library/CoreServices
cp /com.apple.recovery.boot/boot.efi /Volumes/Macintosh\ HD/usr/standalone/i386

Now quit the terminal (cmd-Q)

You can run the Startup Disk selection from here (it's under the Apple menu), choose your normal volume, and click restart

 

[Mola55e5]

Using the commands with the SSD drive came up no such file or directory on both commands. And then I changed from ssd to OS X base system came up with something different and I restarted from my SSD And is still boots into OS X utilities. I've noticed that on the boot screen the bar fills up about 40% get stuck and then restarts twice and never feels that the entire way and then comes into the disk utili noticed that on the boot screen the bar fills up about 40% get stuck and then restarts twice and never feels that the entire way and then comes into the osx Utilities

 

[rthpjm]

Using the commands with the SSD drive came up no such file or directory on both commands. And then I changed from ssd to OS X base system came up with something different and I restarted from my SSD And is still boots into OS X utilities. I've noticed that on the boot screen the bar fills up about 40% get stuck and then restarts twice and never feels that the entire way and then comes into the disk utili noticed that on the boot screen the bar fills up about 40% get stuck and then restarts twice and never feels that the entire way and then comes into the osx Utilities

From your image...

It looks like you are not booted from the recovery partition. Please post the output from the following commands

ls -l /

diskutil info /

diskutil info /Volumes/Macintosh\ SSD

Also, please be careful when typing in the commands, the letter case is important. I noticed you had typed /volumes with a lowercase v, this is distinctly different from the required /Volumes with an uppercase V.

Your problem will most likely be fixed by copying a Pike boot.efi file into the two correct locations.
I had asked you to boot into the Recovery HD, if you can't do that, then you simply need to locate a copy of the Pike boot.efi file.
You may have downloaded a copy from Pike's GitHub site,
You may have downloaded my pikify tool set
You may have installed Boot64 or CapitanPikeFix (both of which have copies)
You may have a copy on the Recovery partition.

Find a Pike version of boot.efi and copy it to
/Volumes/Macintosh\ SSD/System/Library/CoreServices/boot.efi
/Volumes/Macintosh\ SSD/usr/standalone/i386/boot.efi

 

[hwojtek]

I disabled (SIP) and did them one at a time ( 11.4/11.5/to max at 10.11.6 !!!

No need for this, you can shoot straight to the current version without intermediate stages. Glad your Mac works for you.

 

[Mola55e5]

Recovery doesn't seem to be working. I'm about to go buy an apple keyboard to make sure I'm doing it right. I'm attaching results from the window u asked for.

 

[rthpjm]

Recovery doesn't seem to be working. I'm about to go buy an apple keyboard to make sure I'm doing it right. I'm attaching results from the window u asked for.

Thank you for those pictures. It appears that you are booted off a disk image (DMG), specifically a OS X Base System (BaseSystem.dmg), but I cannot figure out how/why from those pictures.

Can you check the size of the /System/Library/CoreServices/boot.efi file please...

du -h /System/Library/CoreServices/boot.efi

It should be just over 300Kb if it is a Pike boot.efi file

Then check the SSD boot.efi file size

du -h /Volumes/Macintosh\ SSD/System/Library/CoreServices/boot.efi

If this is around 600Kb, then it is an Apple version, you need to replace it (and probably the other location too)

cp -f /System/Library/CoreServices/boot.efi /Volumes/Macintosh\ SSD/System/Library/CoreServices/boot.efi
cp -f /System/Library/CoreServices/boot.efi /Volumes/Macintosh\ SSD/usr/standalone/i386/boot.efi

Find the Startup Disk Chooser, choose Macintosh SSD as the startup disk and restart

 

[Mola55e5]

It won't take the du command. Any ideas?

 

[TO5]

No need for this, you can shoot straight to the current version without intermediate stages. Glad your Mac works for you.

Thank YOU!

 

[rthpjm]

It won't take the du command. Any ideas?

Try using ls -lh instead of du -h
ell ess [space] minus ell hach

 

[Mola55e5]

Is -lh command worked and file size is exactly what you specified. But on the copy command I get an operation not permitted

 

[rthpjm]

Is -lh command worked and file size is exactly what you specified. But on the copy command I get an operation not permitted

chflags nouchg /Volumes/Macintosh\ HD/System/Library/CoreServices/boot.efi

Then retry the copy

The copy to /Volumes/Macintosh\ HD/usr/standalone/i386/boot.efi should work without further commands...