EFI error on cloned MacBook Pro drive?

[ignatius345]

I recently migrated from a 2012 Retina MacBook Pro to a 2015 Retina MacBook Pro (basically the same machine, but a bit quicker). The two being so similar, I cloned my old machine using Carbon Copy Cloner onto an external drive, and following CCC's instructions, I booted the new machine off that to test its viability as a bootable drive image. Everything started up and ran fine, so I cloned that external onto the newer MacBook. iCloud Drive got a little weird and a couple apps like Dropbox complained, but other than that it went without a hitch.

A few days later, I'm working on that newer MacBook Pro and this pops up:

I click on Show Report and it takes me to here (below). I can't read the eficheck.dump file, but the title suggests something about the Mac's EFI partition.

Should I be worried? Anyone know of a fix? I'd rather not reinstall everything but will of course if it's absolutely necessary. Is it possible that doing the clone from one Mac to another caused this? I'm not seeing any other issues.

 

[chrfr]

I recently migrated from a 2012 Retina MacBook Pro to a 2015 Retina MacBook Pro (basically the same machine, but a bit quicker). The two being so similar, I cloned my old machine using Carbon Copy Cloner onto an external drive, and following CCC's instructions, I booted the new machine off that to test its viability as a bootable drive image. Everything started up and ran fine, so I cloned that external onto the newer MacBook. iCloud Drive got a little weird and a couple apps like Dropbox complained, but other than that it went without a hitch.

A few days later, I'm working on that newer MacBook Pro and this pops up:
View attachment 862765
I click on Show Report and it takes me to here (below). I can't read the eficheck.dump file, but the title suggests something about the Mac's EFI partition.

Should I be worried? Anyone know of a fix? I'd rather not reinstall everything but will of course if it's absolutely necessary. Is it possible that doing the clone from one Mac to another caused this? I'm not seeing any other issues.
View attachment 862766

I'd suspect that you may have an outdated firmware version (BootROM) on the Mac. This would happen if you cloned a newer operating system onto the 2015 computer without ever having run that operating system's installer on the 2015. You can resolve it by running the new Mojave installer available in the App Store. It won't erase your data, but will apply any applicable firmware updates. The firmware updates include security fixes so it's worthwhile to re-run the installer.

 

[ignatius345]

I'd suspect that you may have an outdated firmware version (BootROM) on the Mac. This would happen if you cloned a newer operating system onto the 2015 computer without ever having run that operating system's installer on the 2015. You can resolve it by running the new Mojave installer available in the App Store. It won't erase your data, but will apply any applicable firmware updates. The firmware updates include security fixes so it's worthwhile to re-run the installer.

Very helpful, thanks. Would reinstalling MacOS from the recovery partition do the same thing or would that just put me back at some older version of Mojave?

 

[chrfr]

Very helpful, thanks. Would reinstalling MacOS from the recovery partition do the same thing or would that just put me back at some older version of Mojave?

Recovery should download the latest version of 10.14.6 with the last supplemental update installed, but it's probably safest to get the installer from the App Store.

 

[ignatius345]

Recovery should download the latest version of 10.14.6 with the last supplemental update installed, but it's probably safest to get the installer from the App Store.

Thanks again!