Hi guys, I'm facing a rather strange issue on my Mac Pro (2009, upgraded to the 5,1 firmware, if it makes a difference, running El Capitan 10.11.6).
I recently added a hard drive coming from another mac inside it (actually, I cloned the drive from another mac running El Capitan, since the computer died and I needed the data as is, and the special architecture it had, and the programs, etc. and I was in a rush to finish some projects, so no time to reinstall everything). It is not my main boot drive. I also have a clean install of El Capitan as a main boot drive.
I noticed when I boot on the secondary drive (let's call it drive B) but also when I boot on the main drive (Drive A) that the console is throwing all sorts of permissions errors at me. Permissions are located on a subsection of Drive B, that's a data partition. That's not even linked to Drive A in any way, so first thing first, I don't even understand how Drive B is affecting Drive A when I boot on Drive A, since the two of them are physically separated, and I don't quite grasp why would El Capitan on Drive A ever need to load the extensions from Drive B to work since it has its on extensions on Drive A.
Anyway.
I tried, of course, to repair the permissions. Permissions have been successfully repaired, and are not triggering any error anymore whenever I search for them in the terminal. However, I'm still getting errors in the Console all the time when I'm logged in on Drive B (haven't tried Drive A again since I'm getting crazy on Drive B ATM).
It doesn't affect the behaviour of the computer, but obviously I don't like that, at all.
SIP is disabled.
I don't have a flashed graphic card, so anything that needs to be done in recovery mode would be a hassle. Also, since it's a secondary drive, NVRAM reset doesn't do anything (in case it would be needed. I did it already, and I then chose my graphic card again via screen share since I have a bunch of other macs lying around). I could of course swap the drive places and put Drive B as primary drive in slot 1 for tests, but right now I'd rather have a command line solution, since I guess there must be one.
Also, my bluetooth is acting stupid, no idea why, I have a magic mouse that just can't get recognised, like, ever, and when it was before all that (I ended up deleting the kext for bluetooth since they appeared corrupted) it kept getting disconnected and behaving erratically. The mouse works perfectly on my other computers. The mouse doesn't connect on either Drive A or Drive B. My other bluetooth mouse, Mighty Mouse, is working fine. This is so weird I thought I had to mention it.
Anyway, back to the matter at hand : here's my console output.
As you can see, it's a loop. After a while, it stops, out of sheer despair. (
11/07/18 13:50:54.038 com.apple.kextd[47]: /Volumes/Almost Precious has failed to update 26 times, not trying again)
Almost Precious is the name of the partition holding the data, it's partition where my user folder is. I had to do some kind of special mix, on the old computer I had two different drives, a SSD for the system, and a HD for the data. Here everything is on Drive B, but on two different partitions. It was a kind of fusion drive, done when the fusion drive didn't exist, back in 2011, a very ugly solution, that I don't really have time to change right now but that won't remain as is. I plan to progressively transfer all the data to a new drive inside that mac, and to get rid of the system on Drive B and use only Drive A, but like I said, I have a few projects that I started on that old computer that died on me and I need to finish them (and it might take a few more months).
Thank you so much for all advice!
I recently added a hard drive coming from another mac inside it (actually, I cloned the drive from another mac running El Capitan, since the computer died and I needed the data as is, and the special architecture it had, and the programs, etc. and I was in a rush to finish some projects, so no time to reinstall everything). It is not my main boot drive. I also have a clean install of El Capitan as a main boot drive.
I noticed when I boot on the secondary drive (let's call it drive B) but also when I boot on the main drive (Drive A) that the console is throwing all sorts of permissions errors at me. Permissions are located on a subsection of Drive B, that's a data partition. That's not even linked to Drive A in any way, so first thing first, I don't even understand how Drive B is affecting Drive A when I boot on Drive A, since the two of them are physically separated, and I don't quite grasp why would El Capitan on Drive A ever need to load the extensions from Drive B to work since it has its on extensions on Drive A.
Anyway.
I tried, of course, to repair the permissions. Permissions have been successfully repaired, and are not triggering any error anymore whenever I search for them in the terminal. However, I'm still getting errors in the Console all the time when I'm logged in on Drive B (haven't tried Drive A again since I'm getting crazy on Drive B ATM).
It doesn't affect the behaviour of the computer, but obviously I don't like that, at all.
SIP is disabled.
I don't have a flashed graphic card, so anything that needs to be done in recovery mode would be a hassle. Also, since it's a secondary drive, NVRAM reset doesn't do anything (in case it would be needed. I did it already, and I then chose my graphic card again via screen share since I have a bunch of other macs lying around). I could of course swap the drive places and put Drive B as primary drive in slot 1 for tests, but right now I'd rather have a command line solution, since I guess there must be one.
Also, my bluetooth is acting stupid, no idea why, I have a magic mouse that just can't get recognised, like, ever, and when it was before all that (I ended up deleting the kext for bluetooth since they appeared corrupted) it kept getting disconnected and behaving erratically. The mouse works perfectly on my other computers. The mouse doesn't connect on either Drive A or Drive B. My other bluetooth mouse, Mighty Mouse, is working fine. This is so weird I thought I had to mention it.
Anyway, back to the matter at hand : here's my console output.
Code:
11/07/18 13:50:32.215 com.apple.kextcache[2549]: rebuilding /Volumes/Almost Precious/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
11/07/18 13:50:33.215 com.apple.kextcache[2550]: IOSystemManagement.kext has incorrect permissions; omitting.
11/07/18 13:50:33.216 com.apple.kextcache[2550]: IONVRAMFamily.kext has incorrect permissions; omitting.
11/07/18 13:50:33.217 com.apple.kextcache[2550]: ApplePlatformFamily.kext has incorrect permissions; omitting.
11/07/18 13:50:33.217 com.apple.kextcache[2550]: AppleNMI.kext has incorrect permissions; omitting.
11/07/18 13:50:33.217 com.apple.kextcache[2550]: System.kext has incorrect permissions; omitting.
11/07/18 13:50:33.234 com.apple.kextcache[2550]: IOHIDSystem.kext has incorrect permissions; omitting.
11/07/18 13:50:33.235 com.apple.kextcache[2550]: IOHIDEventDriver.kext has incorrect permissions; omitting.
11/07/18 13:50:33.260 com.apple.kextcache[2550]: CellPhoneHelper.kext has incorrect permissions; omitting.
11/07/18 13:50:33.266 com.apple.kextcache[2550]: AppleUSBTopCase.kext has incorrect permissions; omitting.
11/07/18 13:50:33.273 com.apple.kextcache[2550]: AppleTopCaseActuatorHIDDriver.kext has incorrect permissions; omitting.
11/07/18 13:50:33.274 com.apple.kextcache[2550]: AppleTopCase.kext has incorrect permissions; omitting.
11/07/18 13:50:33.275 com.apple.kextcache[2550]: AppleThunderboltPCIAdapters.kext has incorrect permissions; omitting.
11/07/18 13:50:33.335 com.apple.kextcache[2550]: USBStorageDeviceSpecifics.kext has incorrect permissions; omitting.
11/07/18 13:50:33.337 com.apple.kextcache[2550]: SonyXDCAMDriver.kext has incorrect permissions; omitting.
11/07/18 13:50:33.343 com.apple.kextcache[2550]: FireWireStorageDeviceSpecifics.kext has incorrect permissions; omitting.
11/07/18 13:50:33.344 com.apple.kextcache[2550]: AppleXserveRAID.kext has incorrect permissions; omitting.
11/07/18 13:50:33.347 com.apple.kextcache[2550]: AppleATAPIStorage.kext has incorrect permissions; omitting.
11/07/18 13:50:33.358 com.apple.kextcache[2550]: AppleMobileDevice.kext has incorrect permissions; omitting.
11/07/18 13:50:33.360 com.apple.kextcache[2550]: AppleKextExcludeList.kext has incorrect permissions; omitting.
11/07/18 13:50:33.369 sandboxd[414]: ([1845]) systemsoundserve(1845) deny file-read-data /private/var/root/Library/Preferences/.GlobalPreferences.plist
11/07/18 13:50:33.370 com.apple.kextcache[2550]: No kexts found for architecture i386.
11/07/18 13:50:33.373 com.apple.kextcache[2549]: Child process /usr/sbin/kextcache[2550] exited with status 71.
11/07/18 13:50:33.373 com.apple.kextcache[2549]: Error 107 rebuilding /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
11/07/18 13:50:33.373 com.apple.kextd[47]: helper error while updating /Volumes/Almost Precious (error count: 23)
11/07/18 13:50:33.374 com.apple.kextd[47]: async child pid 2549 exited with status 71
11/07/18 13:50:37.656 com.apple.kextcache[2552]: rebuilding /Volumes/Almost Precious/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
11/07/18 13:50:38.462 com.apple.kextcache[2553]: IOSystemManagement.kext has incorrect permissions; omitting.
As you can see, it's a loop. After a while, it stops, out of sheer despair. (
11/07/18 13:50:54.038 com.apple.kextd[47]: /Volumes/Almost Precious has failed to update 26 times, not trying again)
Almost Precious is the name of the partition holding the data, it's partition where my user folder is. I had to do some kind of special mix, on the old computer I had two different drives, a SSD for the system, and a HD for the data. Here everything is on Drive B, but on two different partitions. It was a kind of fusion drive, done when the fusion drive didn't exist, back in 2011, a very ugly solution, that I don't really have time to change right now but that won't remain as is. I plan to progressively transfer all the data to a new drive inside that mac, and to get rid of the system on Drive B and use only Drive A, but like I said, I have a few projects that I started on that old computer that died on me and I need to finish them (and it might take a few more months).
Thank you so much for all advice!