Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan
- Thread starter Mr. Zarniwoop
- Start date
-
- Tags
- mac pro 2006 mac pro 2007
- Sort by reaction score
Please note I had the boot loop and had to downgrade to previous installation.
I updated an El Capitan virtual machine on the Mac Pro and it works fine, so it is not related to SSE4 support (Sierra and High Sierra won't start in VMware Fusion on this machine).
I updated an El Capitan virtual machine on the Mac Pro and it works fine, so it is not related to SSE4 support (Sierra and High Sierra won't start in VMware Fusion on this machine).
Hi, same issue here. Yesterday against my better judgement I updated to 2018-001 my otherwise perfectly working Mac Pro 1.1 running El Capitan 10.11.6 installed with pikify. I was stuck in an endless boot loop, as long as the progress bar appeared the boot process interrupted and the Mac restarted. I also noticed that there was a red light from the back towards the top inside the case, I think where the power supply is.
Restoring to the last time machine backup got me back in business and the red light is now green. Strange thing is that the light was red already at startup before any OS was loaded.
Restoring to the last time machine backup got me back in business and the red light is now green. Strange thing is that the light was red already at startup before any OS was loaded.
I updated without checking like a bonehead and now I can't get my Lion portion to boot fully or from CD they both get started up and show a background image but that is it. No Dock or HDD show on the desktop. Waited about 8-10 mins on both and nothing else happened. Now walking away from it to clear my head and come back to it and hope it boots so I can restore yesterdays CCC. Thinking of PR and NV resets as I have no other ideas at this point. I will be sad if after 11.5 years my 1.1 is done.
How many HDs to you have in your Mac Pro? I'd try removing the El Capitan disk, and then install another OS on another disk. Once you're up and running, make sure you select the proper startup disk, put back your El Capitan disk in your Mac, erase, then clean install. That's basically what I'm about to do on mine, unless I can migrate my wife's home directory to the new installation and then CCC back to my SSD (so I may not have to erase the disk first)
Tried that and no change. :-/ I think apples update has bricked it for good this time. I will let it run over night and check it in the morning and hope something has appeared on the screen.
Oh wow that sucks!!! I hope I'll be able to at least boot from a usb installer!
I twice had a boot loop after security update 2018-001 and rather than use a backup method I started a new install of the pikified installer from my original bootable USB disk and selected the not working original el capitan hd as the target for the install. Unless you select clean install option this will keep your apps/data/user settings but will replace the base OS part only. You do not need to erase the disk first just re-run the pikified usb installer to the boot looped hd, which will recopy all modified boot / system files. After reinstall and bootup you will see the only update missing and waiting on your restored system will be 2018-001 as you probably successfully installed itunes/safari updates just before the boot loop. I hid the 2018-001 update until a smart guy fixes it (right hand mouse click the information url in the description). Fixed my 1.1 in about 30 minutes. Could work for your situation?
Its worth noting that holding down the option key during the boot loop should also enable you to select the Recovery HD that the security file update itself creates during el capitan 2018-001 update. Thats if you want to recover from a time machine archive on a backup disk etc.
Also worth noting that 2008-001 update does want to update your hardware as the mac pro double chimes before the first boot loop. This could brick some machines in theory if it goes wrong hence no boot options but it hasn't bricked my two machines so far.
Obviously this will only work if you can normally see boot screens.
Last edited:
Thanks for the info here, folks. I've hidden that new security update - it sounds as if it might not be needed for the Xeon 53xx processors anyway, so no loss. Updated Safari and iTunes manually, and hid the security update - no issues here so far after doing that.
Tried that and neither recovery from the El Cap or Lion disk worked. Pulled El Cap from the box and still just boots to the lion desktop picture and nothing else. Same when I option boot to the Lion CD Rom.
Also I don't have the USB install stick but I doubt it would boot to it. But can you point me to where I can find info on the pikefied usb install please and thank you.
Last edited:
To create a USB stick is easy if you can boot into a machine (10.6 or higher) as per the guide on Page 56. Minimum capacity of USB stick is 8Gb. Simply copy an original unmodified El Capitan 10.11.6 Install file into your applications folder then download pikify 3.1 folder on page 56. Unzip it. Navigate to it in the terminal app and run commands as shown on this thread
https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2-1-and-os-x-el-capitan.1890435/page-56
or the commands from memory
Step 1.
open terminal and run command to give root access.
sudo -s
[your password]
Step 2. type cd space and then drag unzipped pikify 3.1 folder onto terminal window to change to it that file folder location, click on window and press enter. You can type ls followed by enter to list folder contents. You should see createpikeinstallmedia in the current terminal folder.
Step 3. Run the command below replacing [InstallerVolumeName] with your USB drive name eg.. /Volumes/Kingston
./createpikeinstallmedia /Volumes/[InstallerVolumeName]
Step 4. Follow on screen terminal windows to modify your original installer in your application folder and to create a usb stick from it. It will take 20-30 minutes to create/copy the installer. It takes a long time to copy 8Gb files. You need allot of ram circa 12Gb +
You can buy pre-made pikify USB sticks for 32bit efi on ebay if you have no stick or backup OS to create from.
Last edited:
Same problem here. Endless boot loop with chime
However, I need help to restore :
My status is as follow :
- SSD 1 with 3 volumes : EFI, 10.11.6, Recovery HD
- SSD 2 with 2 volumes : EFI, 10.9.5
- HD with 2 volumes : EFI, Media files
- Time Capsule with backup pre-yesterday from SSD 1 /10.11
The SSD 1 won't boot, stuck in boot loop
The SSD 2 boots, and I can mount SSD 1 /10.11 ( I can see all updated files and also that boot.efi was not touched)
I can't enter time machine from SSD 2 ("impossible to connect") but I can mount the backup from sparsebundle as a virtual disk and access backuped files
I have an updated graphic card so I don't see the boot screen when I restart and can't sofar mount SSD 1 / recovery HD to launch restoring utility
I am wondering what are my options
Could I blindly type a sequence of keys after startup to mount SSD 1 / recovery HD ?
Is there any way to launch a restoration from SSD 2 ?
Any help appreciated .
Seems like the Intel Xeon 5100 ("Woodcrest") and 5300 ("Clovertown") are not on Intel's list of processors affected by the Meltdown bug:
https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr
We can probably safely skip this damn update.
https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr
We can probably safely skip this damn update.
Well, I was running my system from a cloned backup - and it crashes after about 15 minutes of usage. I re-imaged the original drive with a fresh El Capitan install. That drive must've gotten fried from the boot-cycling since it crashes after about 1 minute of usage. Running an old hard drive with Lion on it is stable.
Well, I just set the update to ignore in the app store too, as I said yesterday.
I've been running the newest Safari and iTunes with no problems since then.
It does seem that we are safe from the "meltdown" bug, but according to the release notes there were 4 other security patches other than the "meltdown" bug specifically for 10.11.6 in this update.
https://support.apple.com/en-us/HT208465
Sadly, we all probably knew this day was coming but, I think now we may be officially on our own.
Hopefully not, but the writing is definitely on the wall.
- Jay
I've been running the newest Safari and iTunes with no problems since then.
It does seem that we are safe from the "meltdown" bug, but according to the release notes there were 4 other security patches other than the "meltdown" bug specifically for 10.11.6 in this update.
https://support.apple.com/en-us/HT208465
Sadly, we all probably knew this day was coming but, I think now we may be officially on our own.
Hopefully not, but the writing is definitely on the wall.
- Jay
Ooh, just noticed the standalone updater has been posted.
https://support.apple.com/kb/DL1955?locale=en_US
Any brave souls out there want to dig in with Pacifist and see what's doing us in ?
I'm happy just setting it on ignore, but maybe somebody could figure out why we are getting donked on this one.
- Jay
https://support.apple.com/kb/DL1955?locale=en_US
Any brave souls out there want to dig in with Pacifist and see what's doing us in ?
I'm happy just setting it on ignore, but maybe somebody could figure out why we are getting donked on this one.
- Jay
I'm up and running again. Wheww!
I ended up with a clean install of El Capitan (10.11.6) on a spare HD. I did it directly on my Mac Pro 5,1 to make things easier (no need to make the "special version" of the installer to make it 2006-friendly).
1- I had to build a usb installer because Sierra wouldn't let me run the El Cap installation app.
2- Once it was installed, I booted back on my Sierra partition and replaced the boot.efi files on the El Cap disk.
3- Then I removed the SSD from the 2006 just in case.
4- Put the new 10.11.6 HD in it, everything went fine.
5- Put back the SSD and restarted (on the proper startup disk!)
6- migrated all users and apps to the HD, but only users and apps (I didn't want to mess with any of the system files).
7- Once it was done I erased the SSD, cloned the fresh HD installation on it and things are now back to normal.
Since then I've hidden the security update from the App Store...
[doublepost=1516840033][/doublepost]
Go to the App Store prefs and disable everything
[doublepost=1516840664][/doublepost]
It's been that way since we learned that Sierra would never be able to run on these macs. No big deal for me, these Mac Pros are solid and 10.11.6 is still recent, regardless of this vicious security update. The latest safari can run on it, the latest iTunes, and mostly every other "modern" app. It will take a long time before my 2006 machine reaches the sad state of "total uselessness"
I ended up with a clean install of El Capitan (10.11.6) on a spare HD. I did it directly on my Mac Pro 5,1 to make things easier (no need to make the "special version" of the installer to make it 2006-friendly).
1- I had to build a usb installer because Sierra wouldn't let me run the El Cap installation app.
2- Once it was installed, I booted back on my Sierra partition and replaced the boot.efi files on the El Cap disk.
3- Then I removed the SSD from the 2006 just in case.
4- Put the new 10.11.6 HD in it, everything went fine.
5- Put back the SSD and restarted (on the proper startup disk!)
6- migrated all users and apps to the HD, but only users and apps (I didn't want to mess with any of the system files
).7- Once it was done I erased the SSD, cloned the fresh HD installation on it and things are now back to normal.
Since then I've hidden the security update from the App Store...
[doublepost=1516840033][/doublepost]
Go to the App Store prefs and disable everything
[doublepost=1516840664][/doublepost]
Sadly, we all probably knew this day was coming but, I think now we may be officially on our own.
Hopefully not, but the writing is definitely on the wall.
It's been that way since we learned that Sierra would never be able to run on these macs. No big deal for me, these Mac Pros are solid and 10.11.6 is still recent, regardless of this vicious security update. The latest safari can run on it, the latest iTunes, and mostly every other "modern" app. It will take a long time before my 2006 machine reaches the sad state of "total uselessness"
Last edited by a moderator: