- Joined
- Jul 15, 2017
- Messages
- 170
- Motherboard
- Gigabyte GA-Z270XP-SLI
- CPU
- i7-7700K
- Graphics
- RX 6600 XT
- Mac
- Mobile Phone
In case this of benefit to someone else, I'd been trying to upgrade from 10.14.6+ to 10.15.3 without success and assumed that it was something in my config.plist causing my problem as obviously there were a Lot of successes with leaving the kexts in /L/E.
But, for me - after I removed the standard kexts (and also AppleAHCIPortHotplug.kext for SATA hot plugging installed by Hackintool), I was able to install without a problem - and then import (both upgrading and installing from scratch and then migrating failed).
My clue was that the migrate failed after a successful install to a formatted SSD. While booted up from another SSD I could see that the migrate pulled in all my kexts from /L/E.
When I removed the kexts from /L/E and tried another install and migrate, it worked.
Anyway, here are the details that worked for me.
I really have no idea why they can't be in /L/E for my motherboard (the error was appleNVMe Assert failed)? There's just no valid reason that I can see - and it seemed like there were many benefits for kexts in /L/E?
But, for me - after I removed the standard kexts (and also AppleAHCIPortHotplug.kext for SATA hot plugging installed by Hackintool), I was able to install without a problem - and then import (both upgrading and installing from scratch and then migrating failed).
My clue was that the migrate failed after a successful install to a formatted SSD. While booted up from another SSD I could see that the migrate pulled in all my kexts from /L/E.
When I removed the kexts from /L/E and tried another install and migrate, it worked.
Anyway, here are the details that worked for me.
I really have no idea why they can't be in /L/E for my motherboard (the error was appleNVMe Assert failed)? There's just no valid reason that I can see - and it seemed like there were many benefits for kexts in /L/E?