Okay thanks. I checked the md5 of my kernel and it's not updated, so my issue is different
[doublepost=1524036430][/doublepost]
Yeah only I can't boot into OSX currently
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
Okay thanks. I checked the md5 of my kernel and it's not updated, so my issue is different
[doublepost=1524036430][/doublepost]
Yeah only I can't boot into OSX currently
Hi @sOwLOkay thanks. I checked the md5 of my kernel and it's not updated, so my issue is different
[doublepost=1524036430][/doublepost]
Yeah only I can't boot into OSX currently
Try a verbose boot (hold Cmd and V after the chime, let go when you see text)
See where it gets to....
Is that mode showing kernel logs? I really want to figure this out without re-installling.. Many many things configured on the OS level, I'm so sad
I can't forgive myself for actually bricking my backup as well. I'll try a verbose boot once I'm home.I'll probably have to start a new thread about my issue, but If it's any hint my problems started with a failing GPU. I noticed at first that logging into the OS via VNC has become unreliable and needed restarts to work. I tried a screen (headless machine) and sure enough I was greeted with artifacts everywhere. I bought a new GPU, got picture, am able to boot into recovery HD properly, etc. Still, apple logo only loads half way before I get a spinning death ball. Same on safe mode. What's very weird is that some things do work even without getting into the OS. The computer gets the static IP in the network and the shared drives are perfectly usable from networked machines.
Meh, like I said, I'll start a new thread. I was kind of hoping I somehow installed the update.
Okay thanks. I checked the md5 of my kernel and it's not updated, so my issue is different
[doublepost=1524036430][/doublepost]
Yeah only I can't boot into OSX currently
Hi all,
I got same issue, after updating by mistake to latest security update 2018-002, when reboot, gray screen appears with apple logo for 1 sec then it reloads again.
I checked the kernel and indeed it was modified as expected, I re-linked 2017 kernel version again but boot failure still present.
Doing verbose boot (Cmd + V) boot stops at very early stage: right after :
Code:
ACPI: sleep states S3 S4 S5Googling for that I spotted:
https://www.tonymacx86.com/threads/solved-el-capitan-kernel-panic-after-upgrade.176178/
So I booted into recovery partition and used this command in terminal:
Code:
touch /Volumes/Macintosh\ HD/System/Library/Extensions/ && kextcache -Boot -U /Volumes/Macintosh\ HDAfter kextcache was rebuild I was able to boot into OSX properly.
Hope this helps,
cheers,
Trax
Hmm, I don't know where bootlogs are stored, so I used my iphone to make a video during verbose boot and check the logs on last frame
After trying to fix it with kernel re-link I attempted to re-install 10.11 via pinkify v14 USB disk I used earlier, but the install is not starting (I can just see grey screen with apple logo and small progress bar moving very slowly and nothing happens when it reach the end). So in my case fault was on much lower level which also was causing pinkify install fail.
In the kextcache rebuild command you need to use boot folder as argument, mine is "/Volumes/Macintosh\ HD" if you have a differenvt name you need to replace it. In first attempt I used just "/" as in the link in my reply, this didn't work till I replaced it with "/Volumes/Macintosh\ HD".
2018-002 definitely breaks your El Cap Install. Also app store no longer offers the working 2017-001/005 security updates after fresh 10.11.6 install, You need to download packages from apple website.
https://support.apple.com/kb/DL1914?locale=en_US
https://support.apple.com/kb/DL1920?locale=en_US
https://support.apple.com/kb/DL1932?locale=en_US
https://support.apple.com/kb/DL1939?locale=en_US
https://support.apple.com/kb/DL1945?locale=en_US
https://support.apple.com/kb/DL1914?locale=en_US
https://support.apple.com/kb/DL1920?locale=en_US
https://support.apple.com/kb/DL1932?locale=en_US
https://support.apple.com/kb/DL1939?locale=en_US
https://support.apple.com/kb/DL1945?locale=en_US
Last edited:
Linking as in ln? I've never had any luck with just linking the kernel, had to copy it. Didn't try a kextcache rebuild, though.
Hi rthpjm,
I did what you say because I also failed boot into my system and boot into the recovery over and over again.
It said that :
Localhost com.apple.xpc.launchd[1] (com.apple.xpc.launched.domain.system)
<error>: Could not read path: path = /Library/LaunchDaemons. error = 2: No such file or directory.
<error>: Failed to bootstrap path: path = /Library/LaunchDaemons, error = 2 No such file or directory.
<errir>: assertion failed:15A284...
I can't figure out what's going on. I upgrade my system and it goes like this.
Can you help me? Thanks a lot!
Hmm, I don't know where bootlogs are stored, so I used my iphone to make a video during verbose boot and check the logs on last frame
After trying to fix it with kernel re-link I attempted to re-install 10.11 via pinkify v14 USB disk I used earlier, but the install is not starting (I can just see grey screen with apple logo and small progress bar moving very slowly and nothing happens when it reach the end). So in my case fault was on much lower level which also was causing pinkify install fail.
In the kextcache rebuild command you need to use boot folder as argument, mine is "/Volumes/Macintosh\ HD" if you have a differenvt name you need to replace it. In first attempt I used just "/" as in the link in my reply, this didn't work till I replaced it with "/Volumes/Macintosh\ HD".
Yep I ran the command properly. In fact, it did find a kext with a wrong signature, which I have removed and rebuilt once again, but that wasn't the problem it seems.
@rthpjm: many thanks for the instructions on p56 — just followed your YouTube vid and it worked perfectly!
You can get the 2017-005 Security Update from the support downloads section. Remember the method before the App Store
!https://support.apple.com/en_GB/downloads/Security
The command line from the TerminalOkay thanks. I checked the md5 of my kernel and it's not updated, so my issue is different
[doublepost=1524036430][/doublepost]
Yeah only I can't boot into OSX currently
Code:
uname -awill give you the kernel name/number/version, if you get the IP address and disks are accessible, then it won’t be the kernel that’s causing your issue.
The “system log” is /var/log/messages, it’s a text file....
You can also check the kernel ring buffer log
Code:
dmesgVery low level log info direct from the kernel (or kexts) is written here. It’s sort of an in-memory buffer on most systems, it’s not usually a file on the disk, hence the dmesg command to dump it.
You’re looking for “unusual” items.....
rthpjm - Many thanks for the instructions on Page 56.
I used these on a second hand mac Pro I purchased (Upgarded the CPU to 2 x 4 core 3.0Ghz), and it installed perfectly - I'm now using it to run Parallels (for Windows Dev), and also as a MySQL server
Cheers,
Nick
I used these on a second hand mac Pro I purchased (Upgarded the CPU to 2 x 4 core 3.0Ghz), and it installed perfectly - I'm now using it to run Parallels (for Windows Dev), and also as a MySQL server
Cheers,
Nick
Hi all,
Need some help here:
1. I got the target drive (80gb flash SATA) hooked up via SATA-to-USB to a MacBook Pro (High Sierra) w/ 16gb RAM
2. Downloaded the latest El Capitan from App Store (in Applications folder)
3. Used the pikify3.1 script via terminal and successfully built the installation drive.
4. After completion, hooked target drive back into the Mac Pro 1,1 (10 gb of RAM)
5. Boot right into it on the first try and begin installation
6. Around the 6 minute mark, the screen goes blank and the system reboots (guessing KP)
7. Boots right back into the installer and wants to do the installation again from the beginning
8. Tried again, same result, black screen and reboots around the 6 minute mark.
What am I missing here?
Kevin
2 GB of RAM, as stated millions of times in this thread.
From the post you quoted:
- If you are running from a MacPro, you must have 12Gb of RAM or more.
Thanks guys. My apologies, I forgot to mention that I am well aware of the 12 GB requirement and was wondering if there was a workaround, such as doing the installation from the MacBook Pro, update the EFI and then dropping the drive into the MacPro, thereby bypassing the requirement.
The reason is because I'm trying to avoid putting more $ into the MacPro knowing that El Capitan is likely the end of the road.
Thoughts?
If a workaround is not possible, I'm looking for recommendations on best options to acquire 4x2gb sticks. I'm currently running 4x2gb(from OWC several years back) and 4x512mb(original)
Thanks again.
The reason is because I'm trying to avoid putting more $ into the MacPro knowing that El Capitan is likely the end of the road.
Thoughts?
If a workaround is not possible, I'm looking for recommendations on best options to acquire 4x2gb sticks. I'm currently running 4x2gb(from OWC several years back) and 4x512mb(original)
Thanks again.
It is possible to do the install from another Mac and then modify the install and put the drive into the Mac Pro.
I believe that is covered in this thread somewhere back.
Some time back I did something similar.
I booted my MP1,1 from an external drive running Lion.
Then I cloned a working El-Cap system from a mac mini via FW target disk mode to the MP's boot drive.
All that was left was to copy the modified boot.efi to the new El-Cap installation (2 locations) and all was good.
After creating a Recovery partition I modified the boot.efi files also to make in boot-able.
I booted my MP1,1 from an external drive running Lion.
Then I cloned a working El-Cap system from a mac mini via FW target disk mode to the MP's boot drive.
All that was left was to copy the modified boot.efi to the new El-Cap installation (2 locations) and all was good.
After creating a Recovery partition I modified the boot.efi files also to make in boot-able.
I bought server-pulled RAM from HP and Dell machines with small heatsinks. Pretty low price, around 35€ for a 2x4GiB kit. I have two sets installed for a total of 16 GiB.
But if you get El Capitan installed any other way, you're good to go as long as you get rid of the 512 MiB sticks. That leaves you with 8 GiB, which works fine in one of the three 1,1s I have access to. The third Mac Pro with only 4 GiB is somewhat unstable, so I guess 8 GiB is the minimum.