Check out post #2 of this thread, about using the install USB drive to input Terminal commands.
"csrutil disable" in your case.
https://forums.macrumors.com/threads/trying-to-disable-sip-cant-access-recovery-mode.1930267/
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
"csrutil disable" in your case.
https://forums.macrumors.com/threads/trying-to-disable-sip-cant-access-recovery-mode.1930267/
@jbarley mentions a method to use a usb to get to Recovery.
I am interested in your set up. The software RAID configuration is probably masking the Recovery HD in some way. If you are willing, please share the following information here:
Using a Terminal
Code:
diskutil listI may need to ask for more information later...
Some time back I dabbled in Apple's software raid and one of the things I remember is the software would not allow for the creation of a partition for the Recovery volume.
More info can be found on this with a Google search.
"apple software raid and recovery partition"
Hi guys... I'm having a werid problem after Pikify my mac pro 2.1 with 32 gb with a nvidia Geforce 680 to El Capitan ... Everything works but i can't shutdown the computer... When i ask for shutdown everything disappears except for the desjtop image and it stays there forever.. If i force shutdown by pressing the power button it works but it then has to restart many times before i can go back to my session... Did i do something wrong?? Can i do something?? I can put it to sleep and back on without problems... But restart or shutdown doesn't work anymore.
It sounds like you need to try an SMC reset. There’s links in my signature below...
Humm it now shuts down but i had to reboot it at least ten times to have it working...what do you guys think of using Onyx for El capitan?
Works just like any Onyx generation for any OS ever, is a cleanup tool of choice for many, but it won't do a lot for shutting down your Mac. It's a SMC thing and you have it sorted out already (yes, sometimes it takes dozen of resets for SMC to settle down correctly)
Wow thanks this forum is awesome people are so ressourceful... I've been opening and reassembling py used macs for a while now nit exactly knowing what to do
I'm in the process of installing El Capitan on a recently gifted Mac Pro 1,1. But I can't find security update 2017-005 available anywhere online, it seems to have been taken down from the app store. Does anyone know how I can find out which security version the install I have done has, or where I can find a download, or maybe even have a copy they can share with me?
Use the Apple software download web site. Apple still publishes its software here (not just through the App Store)
https://support.apple.com/en_US/downloads
@Traace Thanks for your help but the terminal command line doesnt work. i always receive the following terminal answere:
touch: Volumes/El Capitan/System/Library/Extensions: No such file or directory
carsten-scholzs-computer:~ carstenscholz$
But the Extensions Folder is in that spot you can see in the Screenshot, i dont know why there is still the error message .. i might just re-install os el capitan i guess .. :/
touch: Volumes/El Capitan/System/Library/Extensions: No such file or directory
carsten-scholzs-computer:~ carstenscholz$
But the Extensions Folder is in that spot you can see in the Screenshot, i dont know why there is still the error message .. i might just re-install os el capitan i guess .. :/
You need to be exact with what you type (I am assuming that you have copied and pasted the error message above)?
If so then you are missing the initial forward slash
Code:
touch “/Volumes/El Capitan/System/Library/Extentions”Notice the first /
Any Unix-based system (MacOS, Linux, Solaris, etc...) has a common format for path names. A path is typically composed of elements:
//machine-name/folder/sub-folder/file
//machine is not often used, and is sometimes used as //network/machine (often in conjunction with the automounter)
// is often taken to mean “the local network”, thus //otherMac would represent a network connection to otherMac...
After that the first path element is taken to be relative to the root (or “top level”) of the local file system. Hence, if you omit the //machine element, by default /path is interpreted as the top level folder named path. Think of / as the explicit root of the local machine. If a path begins with // or / then it is often referred to as an “absolute path” because it is fully defined and will always refer to the same location.
If you omit the first / or // then the path is often referred to as a “relative path”. The interpretation is appended to the current working directory.
If you open a new Termial session, the current working directory is usually your home folder at
/Users/yourLoginName
Therefore if you type a path as
Code:
touch “Volumes/El Capitan/System/Library/Extentions”
Code:
touch “/Users/yourLoginName/Volumes/El Capitan/System/Library/Extentions”Whereas, if you include the first / it does not matter what the current working directory is, the Terminal will always interpret that as an absolute path
Code:
touch “/Volumes/El Capitan/System/Library/Extentions”P.S.
You can drag and drop onto the Terminal,
Type the initial touch and space, then drag the Extensions folder from the Finder window and drop it onto the Terminal window...
Last edited:
Grrrr! Every time I shut down my system for any extended length of time the SSD will not boot. This is the fourth time now I'm having to go through this. Every time is like the first. I can't remember how I got it to work last time and although I know I made notes somewhere I can't find them.
Many thanks! I visited the download page a couple of times via google search and the download button was inoperable. The page must have loaded incorrectly.
Does anyone know why a period of inactivity (10 days powered down) that would cause a drive to fail? There's nothing wrong with the OS - I replaced the boot.efi files with normal and booted from it with my laptop but I cannot get get the Mac Pro to boot from it. The recovery drive also went south somehow.
This is odd. When I run Pikify_v14 the boot.efi files it places in CoreServices and i386 are 1.1 mb, all the other boot.efi files that are provided and should work are only 319.4 kb. The files that worked previously, from looking at my backup, are 319.4 kb.
Ah ha! The old one's were owned by root and the new one's are owned by me. Changing ownership to root. Hopefully that fixes it.
That still didn't work.
Ah ha! The old one's were owned by root and the new one's are owned by me. Changing ownership to root. Hopefully that fixes it.
That still didn't work.
Last edited:
Older versions of Safari do not render the download button. It’s really annoying. You’d think that Apple’s web team would actually test against their own broswers. Safari as shipped with El Capitan 10.11.6 is affected. Only the most recent version of Safari works (in my experience). I had to download Chrome (of all things!)...
[doublepost=1534786108][/doublepost]
The MacPro has a NVRAM battery on the motherboard. Your symptoms are consistent with an expired battery.
Try replacing the battery...
Clear the PRAM (links in my signature).
On next boot hold down the ALT key when your hear the chime (or second chime if doing a PRAM reset)
Choose your SSD.
When you get to MacOS X, go straight to System Preferences > Startup Disk
Authorise
Choose your SSD.
That “should” at least ensure everything is clean and properly set....
P.s. also see my reply above (merged) about the battery...
[doublepost=1534839977][/doublepost]
Pikify v14 will correctly write the 300k versions of Pike boot.efi file. If it did not do this, then the machine would not boot after the install.
It sounds like you are applying updates. If you apply any of the OS updates (probably in the “combo” style), then the Pike versions of boot.efi files will be overwritten by the Apple versions (which are much bigger by file size), and then your machine will not boot. From the sparse description you provide, it sounds like the most likely cause of your issues.
Did you install CapitanPikeFix (and turn off SIP), or did you install Boot64 (SIP can be on or off)?
BEFORE applying any updates?
Without one of these two utilities, OS updates will likely overwrite the boot.efi files.
Did you say “yes” to the prompt that “enables automatic updates”? This is not a good thing to do on our modified MacPros. I strongly recommend that you turn off automatic updates...
What version of El Capitan are you starting with?
Any version lower than 10.11.6 will probably give the condition that requires an OS update to 10.11.6, which will likely cause your symptoms...
The quickest way to recover from an update-overwrite is to boot into the Recovery HD, start a Terminal session from the Utilities menu, and copy the Recovery HD’s boot.efi file to the two locations on your boot volume. Search this thread...
Last edited:
I did finally get it working but reinstalling the OS with "Install Piked OS X El Capitan.app" No, I haven't updated or set autoupdates. Are you kidding? This thing is so fragile ... I'm paranoid to install just about anything. I am at 10.11.6 and have never gone above that. Too scared.
I can't see a boot screen because of my video card, so it's not as easy as it should be.
I have noticed a folder called "OS X Install Data" on the root of my drive that has files that were updated yesterday when I ran the OS install ... that no one here ever talks about. It looks pretty important to me with what looks to be important files inside:
/OS X Install Data/InstallESD.dmg
/OS X Install Data/.disk_label
/OS X Install Data/boot.efi
/OS X Install Data/com.apple.Boot.plist
/OS X Install Data/PlatformSupport.plist
/OS X Install Data/.disk_label_2x
/OS X Install Data/prelinkedkernel
During my attempted fix I never looked at this directory. Whatever was wrong, I don't think was the boot.efi files. Although, I don't know why an extended shutdown would cause the drive not to boot normally.
Thanks for the reply!
I can't see a boot screen because of my video card, so it's not as easy as it should be.
I have noticed a folder called "OS X Install Data" on the root of my drive that has files that were updated yesterday when I ran the OS install ... that no one here ever talks about. It looks pretty important to me with what looks to be important files inside:
/OS X Install Data/InstallESD.dmg
/OS X Install Data/.disk_label
/OS X Install Data/boot.efi
/OS X Install Data/com.apple.Boot.plist
/OS X Install Data/PlatformSupport.plist
/OS X Install Data/.disk_label_2x
/OS X Install Data/prelinkedkernel
During my attempted fix I never looked at this directory. Whatever was wrong, I don't think was the boot.efi files. Although, I don't know why an extended shutdown would cause the drive not to boot normally.
Thanks for the reply!
That folder is the “modified installer” that Pikify writes.
Once you have successfully installed, then you can delete that folder...
If your gfx card does not show boot screens, and you want to use the Recovery HD:
Reboot, when you hear the chime, hold the Apple and R keys for approx 10 seconds...
I’m sorry to hear you think you have a fragile system. I and many others find our boxes are rock solid.
Things to think about:
RAM. El Capitan does not work well with low density RAM sticks (aka modules). If you have any 512Mb RAM sticks you should remove them. Ditto 1GB sticks. If that means you end up with little or no RAM then consider buying pairs of 2GB or 4GB sticks. There’s typically lots of relatively inexpensive RAM on the secondhand market. El Capitan is memory hungry, aim for a minimum of 8GB, you’ll get better performance and stability with more RAM. 8 x 2GB (for 16GB) or 8 x 4GB (for 32GB) are the favourites...
I know that I keep mentioning it, but all PCs including Macs usually have an NVRAM battery. MacPro 1,1 and 2,1 are approx 12 years old now. The battery may need to be replaced.
The selected boot disk is stored as a parameter in the NVRAM (hence the term parameter RAM or PRAM in Mac terminology). If the battery is dead or dying (not holding much charge), then an extended period without power will cause the PRAM to be wiped, it will forget which drive should be booted, amongst other things. It will badly affect the initial boot sequence.
It may cause the Power On System Tests to go into first-run mode, causing all checks to be run. This will extend the time to boot, especially if you have a lot of RAM. Once POST completes, the EFI firmware will look at the PRAM to find the selected boot drive. If the PRAM is blank because of the loss of power, then the EFI code will usually try a poll of the PCI bus. This doesn’t always work, and will sometimes result in the display of a “flashing question mark” over an image of a folder. This is a boot screen, which you say you cannot see because of your gfx card. Therefore you will be left in the dark about why it’s not booting.
If you’re lucky, and the power has been on for a few minutes, the PRAM battery may hold a charge long enough for a reboot to work. The previous EFI probe of the PCI bus might have located a bootable partition and stored that in the PRAM, allowing the machine to boot. This all depends on the residual charge that the PRAM battery (if you want to be technical, plus the residual charge in the motherboard capacitance) can hold, if that’s enough to maintain the PRAM contents, then the machine will likely boot okay.
This is why reboots are probably working once you’re up and running. However, if there’s an amount of time between shutdown and restart, then the residual charge will dissipate, and the PRAM contents will be lost.
You don’t say what make and model of gfx card you have. If the card has a VGA 15-pin port, and you have a suitable monitor and cable, you can often see the boot screens on this VGA. The EFI code will fall back to VGA. If the card has DVI-I ports, then you could fit a DVI-VGA adaptor, I know this works on my Nvidia GTX680.
I’m not sure if anyone has had any success with other digital-to-VGA adaptors (Mini Display Port to VGA for example)
If you’re up to 10.11.6 already, then be careful of the Security Updates. All of the Security Updates released in 2018 (labelled 2018-00x) will replace the kernel file with an incompatible version. This means that the boot.efi files and now the kernel file needs special attention.
Last edited:
When the box is working properly it is rock solid but it's gone south 4 times now and every time, although I keep notes on how to fix it, it's a nightmare getting it back up and running. The last time I recovered I did boot from the recovery drive, although that took days to get working, then I recovered from time machine and then had to replace the boot files. That took a week. I try to do the simplest and easiest things first but they seldom work. I just can't remember everything I did before so every time I have to fix it is like I'm doing it for the first time.
I have 26 gigs of ram now but I do have two 1 gig sticks in there.
What you say about the battery makes perfect sense. That sounds like it's my problem exactly. Also, I have two monitors and often times I don't turn on the second one ... while I was reinstalling the OS I realized it was displaying on the second monitor so I turned it on and ... voila there it was. I don't think I get a boot screen on that second monitor though, I'll have to check.
I've forgotten exactly what is in but the system says, AMD Radeon HD 6xxx 1024 MB graphics. It was supposed to show a boot screen but I was never able to get it to work.
Thank you very much for your help. It's very much appreciated.
[doublepost=1534884003][/doublepost]In order to insure the files stay intact do you recommend the CapitanPikeFix or the Boot64?
I have 26 gigs of ram now but I do have two 1 gig sticks in there.
What you say about the battery makes perfect sense. That sounds like it's my problem exactly. Also, I have two monitors and often times I don't turn on the second one ... while I was reinstalling the OS I realized it was displaying on the second monitor so I turned it on and ... voila there it was. I don't think I get a boot screen on that second monitor though, I'll have to check.
I've forgotten exactly what is in but the system says, AMD Radeon HD 6xxx 1024 MB graphics. It was supposed to show a boot screen but I was never able to get it to work.
Thank you very much for your help. It's very much appreciated.
[doublepost=1534884003][/doublepost]In order to insure the files stay intact do you recommend the CapitanPikeFix or the Boot64?
Now that I have the system back up and running I found it odd that all the windows were undersize for my big monitor ... I think there was never anything wrong with the OS or the system except that it had defaulted to the second monitor which I hadn't turned on. It probably booted just fine but was just showing on the wrong monitor.