![]() If the EFI partition auto-mounts and I just unmount it, it won't make a difference. ![]() What usually happens is that I'll reboot a couple or few dozen times and the EFI partition will stay hidden and it'll stabilize. I want to call Apple about this, but I can't get my hands on a Mac that is 100% reproducible. However, since the EFI partition is read/only, I can't do anything with them. Sometimes they are empty, sometimes they are filled with what look like firmware updates. I have noticed that the contents of the EFI/APPLE/ folders sometimes vary from mac to mac. I've made sure that all the Macs have all the latest firmware/EFI/storage updates applied. I've made and remade the images from the brand newest Macs that we got with all the updates etc. *further details: we are running JSS 9.65, the problems have persisted since 10.9.x, the kernel panics only happen on Macs with SSDs (we have slowly transitioned from HDD Macs to SSD Macs and don't have many left), HDD Macs occasionally mounted the EFI partition, but even when they did, they NEVER crashed. ![]() I found this post that suggests running the recon command, but that has no effect on the EFI partition. if I can boot and reboot and reboot over and over until I happen to catch it on a boot without the EFI partition mounting, then I can safely run it and it will work for weeks or even months, but the kernel panics WILL return. The problem with that tool is that if the computer is in an unstable state, installing a new recovery partition will trigger a kernel panic. I have had SOME success in using Create Recovery Partition Installer.app with preventing the kernel panics but they do eventually return. Every so often the EFI partition won't automatically mount and the computer remains completely stable for the duration, but if they reboot, there is a chance that it will come back. The EFI partition is present right after imaging. At first I thought FileVault was causing the EFI partition to be mounted somehow at bootup, but I removed the enabling of FileVault from the imaging and enrollment process. If I re-enable it, the kernel panics return. if I completely disable FileVault, I am guaranteed to never have a kernel panic. There are other events that link it to FileVault. How do I know it's FileVault? Any and everything relating to FileVault can cause it to crash - including fdesetup commands, the simple act of enabling FileVault, or even clicking on the FileVault tab of the Security preference pane. After many months of troubleshooting, I have linked the presence of the EFI partition at startup to random Kernel Panics caused by FileVault. SOMETIMES repeated reboots will make it go away, but it will come back at some randomly selected boot up at a later time. I've been dealing with this for a long time and I'm still struggling to find a cure.Īfter imaging all brand new MacBook Pros with a fresh 10.10.x image when I login to the computers with the admin account 9 times out of 10 the EFI partition is automatically mounted on the desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |