Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

erudyne

macrumors newbie
Original poster
Oct 17, 2018
14
7
I have a Mid 2014 MBP that I installed a NVMe hard drive (Samsung EVO 960) in a while ago.

It works perfectly (aside from hibernation) running High Sierra. It also works fine in Win 10 or Arch Linux. I can use dd to zero out the partition info on the drive, initialize with only mojave off a usb installer, and have the exact same issues, so I know it's not a bootloader issue.

In Mojave it will crash on boot every time, but only the first time. Loading bar fills about 5/6th of the way, then the grey screen with mouse cursor flashes for a moment, then back to the apple loading screen while the bar progresses, then it restarts. The weird thing is that when I start OSX again, it'll give me the message that informs me that the computer recovered from a crash in multiple languages, and then it boots up just fine. I get into Mojave, and everything works just fine (hibernation untested in mojave).

At the point of successful boot, sometimes it will ask me if I want to reopen programs and send a crash report to Apple. The crash report is more or less the same time with the ionvme kext being the culprit.

I'm functional enough right now just letting it ride through to the second boot attempt, but it really bugs me that I don't know what's being done so consistently differently that second time. Cursory web searches didn't get me much in the way of results, though I don't know if I'm asking the right questions here.

Does anyone have this issue? Does what I'm trying to ask make sense? Does anyone know the answer?
 

erudyne

macrumors newbie
Original poster
Oct 17, 2018
14
7
Didn't realize you could do verbose mode on a real mac. I thought it was just a hackintosh thing.

Tried it just now, and it worked on first boot for some reason. Tried cold booting normally 3 times after and it worked every time. For the last week it's always taken the second boot to start working properly. There were no updates and nothing I can think of has changed other than messing with a wireless driver in Arch (which shouldn't have had an impact). I am at a loss for words.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.