Error loading kernel cache 0xe хакинтош

Hello frustrated, what the below quoted code says is that #1, created a valid cache (that’s good) #2 when it tried to update the symlink to point to it that process failed.

to resolve that error, from ether single user mode ( -s boot mode) or the recovery partition run this list of commands.

(CAUTION: both of these modes by default will give you SUDO access to the system be very carful what you type.)

Hi!

Thanks, the links was useful. But I am not getting any solution. The tutorial there does not account for the fact that the user needs SUDO permissions. 

I ran with sudo and here is what I get…(not what the OP of that tutorial gets)

This is so frustrating!!!

KernelCache ID: C79B2CECB584A805F14556B0A116AE60
symlink("../../../PrelinkedKernels/prelinkedkernel", "/Volumes/MAC SSD/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 2 (No such file or directory)
iMac:~ b$ 

Help Please!

Thank you so much

P.S. I even re-ran without sudo code and I followed the steps and still had no luck.

<code>

fsck

mount —uw /

rm —rf «/Volumes/MAC SSD/System/Library/Prelinkedkernel/prelinkedkernel»

touch «/Volumes/MAC SSD/System/Library/Extensions» && kextcache -system-caches «/Volumes/MAC SSD/»

kextcache -u «/Volumes/MAC SSD/»

</code>

this list of commands is slightly different from the ones in the aforementioned guide, but they do basically the same thing.

the differences are that I took your Volume name to customize them, and that I forced the rebuild of your system cache after deleting the prelinkedcache. this has the effect of having the kext cache manager look for where these files are missing from and rebuilding them in my experience.

HBP

I like a moron got conned into installing High Sierra on my perfectly running hack. Impatient me installed High Sierra without letting my time machine backup finish, so I’m trying to recover it.

I made sure to upgrade Clover and my kexts (mostly fakesmc), the upgrade booted and installed fine, but now when I boot I get:

fs_get_inode_with_hint:7825: failed to load inode 8590481811 ret 22 Error loading kernel cache (0xe).

I’ve had that error before and google had some suggestions. Apparently in the process of upgrading it upgraded my FS to APFS and I didn’t want it to (I have apfs.efi in my drivers64UEFI folder).

I booted into the high sierra installer and deleted the kernelcache as advised by /u/corpnewt, ran a few kextutil commands, and no dice. I know Clover used to have an option to boot without caches, but that appears to be gone now.

I was needing to do a reinstall anyway, but thanks to APFS being case sensitive, and my Sierra install being insensitive, I’m able to see my old install’s files, but not copy them (at least that’s what I think).

Any suggestions? I have read/write access to the old install if I boot into the High Sierra installer for whatever.

Thanks.

For testing purposes, I have a VM in VirtualBox currently runnning macOS 10.12 Sierra. Now that macOS 10.13 High Sierra is in Beta, I wanted to upgrade my VM to this new release. However, this proved to be difficult with the usual ways. This blog post will describe how to upgrade a Sierra VM to High Sierra.

The problem preventing the upgrade appears to be the boot sequence in VirtualBox. It looks like the EFI implementation of VirtualBox does not honor the way macOS wants to select the startup disk/volume/startup script or in whatever way that is actually supposed to work. The result is that you can click through “Install macOS 10.13 Beta.app”, but after the restart the old system comes up as if nothing happened.

Follow these steps to get around this problem:

1. Boot the VM normally in VirtualBox.
2. Open “Install macOS 10.13 Beta.app”, click through until you get to “Restart”.
3. As soon as the screen turns black, start to hammer the F12 key. Make sure your keyboard is grabbed by the VM.
4. If you managed to hit F12 at the right time, the VirtualBox EFI should pop up. If the VM starts up normally, go back to step 2.
5. Now use your arrow keys to select Boot Manager and hit Return, then launch the EFI Internal Shell from there.
6. Inside the shell, type the following commands:

   Shell> fs1:
   FS1:> cd "macOS Install Data"
   FS1:macOS Install Data> cd "Locked Files"
   FS1:macOS Install DataLocked Files> cd "Boot Files"
   FS1:macOS Install DataLocked FilesBoot Files> boot.efi
   

With the last command, the system should continue booting. After a short moment, the installer will turn up and begin to upgrade your system from macOS 10.12 Sierra to macOS 10.13 High Sierra. Now you will have to wait for the macOS Installer to finish, which may take a while.

In case VirtualBox crashes with “Guru Meditation: VERR_IEM_INSTR_NOT_IMPLEMENTED” on the login screen when booting the new system, update to the latest VirtualBox test build, which implements the missing instruction.

This post was inspired by another blog post documenting similar instructions on how to enter the macOS Recovery in VirtualBox. For completeness and archival purposes, you can use the following EFI commands to boot macOS Recovery:

Shell> fs2:
FS2:> cd com.apple.recovery.boot
FS2:com.apple.recovery.boot> boot.efi