I don't think it works like a charm at this moment.Hey guys, if you are installing Mac OS High Sierra on a SSD, then format the SSD in APFS( Apple File System!). It works like a charm. APFS is the new update after Journaled. And it is specifically and specially made for SSDs! Enjoy!
Yes, if you want to install Mac OS High Sierra, you should format your new drive in APFS.Hey everybody,
Wanted to just share my experience as I have often sought out help with my Mac troubles on this site, but for once I was hoping I might be able to help someone.
I also ran into this firmware issue attempting to do a clean install of High Sierra on a new external SSD (Evo 860). My issue I was running into was that my internal hard drive had failed (iMac 27” 2012) and I wasn’t brave enough to open the thing up. Matching was running the most recent version of High Sierra.
I was able to boot into recovery mode (CMD + R) and format the new drive. I formatted to OS X Extended (Journaled) based on all of the different articles and forums I read prior to doing the procedure. Everything went fine until I got the “missing firmware partition...” error and the OS could not be installed on the drive.
I did go into terminal based on another members post and did some (what was scary to a rookie like me) commands. I ran the disk utility and even the repair disk command. This came to no avail as the OS still could not be installed and the drive icon still gray.
I’m a last ditch attempt to solve the problem in the wee AM hours, I decided to format my new drive to APFS rather than OS X Extended (Journaled). In my research I had found mixed reviews as to switching to APFS. My iMac had an HDD and therefore I never had moved to APFS. Since this was a brand new drive with nothing on it I figured I had nothing to lose.
End of story, once I made the switch to APFS, the OS could be installed and the rest went on without a hitch.
Now...still trying to figure out how to bring the old backups from my time machine onto the new OS. Not looking to do a full restore, but would like to get user folder and some keychain stuff off.
Sorry for the length, but just hoping this might help someone in a similar situation.
I had this issue on a 2014 Mini - I couldn't upgrade from El Capitan to High Sierra. So I tried a different approach - try and install Sierra first.Hey Guys, I tried upgrading my mac to High Sierra and I am getting this error. Any suggestions on what may be the cause? I am running Sierra right now.
If you don't get the error message in the original post of this thread ("An error occurred while verifying firmware"), I wouldn't think that trying any of the solutions here would apply. You can certainly try doing the upgrade in Safe Mode (post #13). I kind of gave up reading through most of the remainder of the solutions.I've skimmed this thread while searching for a solution to my problem -
I have a MacBook Pro (15-inch, Mid 2010) and when I upgrade to High Sierra, it goes through the reinstall process and after restart I'm back in Sierra. No firmware errors or anything. Would I be OK trying some of these suggestions? I can't find any other instances where somebody had this specific problem I'm having.
My Boot ROM version is MBP61.005D.B00, so slightly different than what you posted unless you made a typo. I appear to have the latest version of Sierra (16G1510), so it looks like I should keep digging for info. Thanks!If you don't get the error message in the original post of this thread ("An error occurred while verifying firmware"), I wouldn't think that trying any of the solutions here would apply. You can certainly try doing the upgrade in Safe Mode (post #13). I kind of gave up reading through most of the remainder of the solutions.
What you can do is check to see if you have the latest firmware. While running Sierra, run the "System Information" app and the window that comes up should say "Hardware Overview" in the right panel. If it doesn't, press on the first item, "Hardware" on the left panel. When you're there, what is the Boot ROM Version that you have? If you have the latest, for the mid-2010 15" MBP, that should be MBP61.005D.00B. This would presume you have the 10.13.6 (or 10.13.5 I believe as well) installer. If you have the latest version of Sierra, I believe it should have also put this EFI update on. If you don't have this Boot ROM version, what build version of Sierra are you running - this can be obtained by using the same "System Information" app, this time pressing on "Software" and will appear in the "System Version" item (the build number is the number in parentheses).
If you have the latest EFI firmware installed, then you don't have the problem that this thread is addressing and I would suggest you start a new thread. I seem to recall people having the same problem (doesn't upgrade, reverts to pre-install OS version) so you probably (hopefully) would get more specific responses there.
It's not a typo on my part. I got the EFI firmware version from file names in the 10.13.6 combo update .dmg (Apple no longer publishes an updated list of latest EFI versions so we have to resort to tactics like that to figure out what the latest EFI firmware should be). I do notice that for some of the EFI files in the updater, some are "00B" while most are "B00" so my guess would be that there was some mixup in the naming of the files (should be "B00", not "00B"). It could also be that the last 3 characters are ignored altogether since (in the 10.13.6 combo update at least) they are all "B00" or "00B", no other variation appears. In any case, you're unlikely to have the EFI firmware version issue that this thread is about.My Boot ROM version is MBP61.005D.B00, so slightly different than what you posted unless you made a typo. I appear to have the latest version of Sierra (16G1510), so it looks like I should keep digging for info. Thanks!
Hey Guys, I tried upgrading my mac to High Sierra and I am getting this error. Any suggestions on what may be the cause? I am running Sierra right now.
Thank you Peter! I am still having the error though. MY EFI is on both Disk 0 and Disk 1 and both come back OK. Any ideas? I am running a 2010 MacBook Pro with an SSD and HDD. Coming from OS 10.11 High Sierrra seemed to be ok until upgraded to the latest software update.Folks, you can try this even without rescue mode in terminal: "diskutil verifydisk disk0". Should work with those Macs with just one SSD inside. If you've got a more complex machine, check the location of the EFI partition with "diskutil list" first. Could be disk1 as well.
It's going to check your disk, where the EFI partition lies. Takes a few seconds. Like noted, I had this issue, and it was a problem with that little partition that's needed for firmware update. Macbook 12" 2017.
If you get this, then the partition is OK:
user@mac : diskutil verifydisk disk0
Started partition map verification on disk0
Checking the partition list
Checking the partition map size
Checking for an EFI system partition
Checking the EFI system partition's size
Checking the EFI system partition's file system
Checking the EFI system partition's folder content
Checking all HFS data partition loader spaces
Checking booter partitions
Checking Core Storage Physical Volume partitions
The partition map appears to be OK
Finished partition map verification on disk0
If yours is not OK "diskutil repairdisk disk0" in Rescue Mode terminal (boot with CMD-R) fixes it. This shouldn't be too dangerous of a fix, but of course do have a backup first.