- Jan 16, 2011
- Z390 Designare
- Vega 64 + eGPU: 2 x RX 580
- Classic Mac
- Mobile Phone
- , ,
Hi @jiffyslot. Your EFI Folder is formatted as FAT32 and should not be affected by APFS. I'm using APFS now as the default. I've got and app under Windows 10 that lets me read/write to APFS so I don't need to do the HFS to APFS shuffle every time that the macOS is updated.Thanks @jb007. I didn't think so. The reason I asked is because that Terminal command returned an error and was unusable, so I figured something had changed.
When starting and the machine gets past post, I'm seeing a flurry of rapid, unreadable text (as in 4x game show end-credits speed) speed that I can't capture. the nvram -c command is not working in Clover's command/terminal tool, so all I can do is hit F11. When Mojave starts up, there's a brief lower-left side flurry of more text, then it all boots fine. Nothing seems to be in Verbose mode. It's just odd.
Additionally, the EFI folder did not copy over correctly to the cloned SSD (I dragged it from the Mojave APFS startup volume's EFI to the EFI of the destination, of course.) -So I had to -re-drag it from a 3rd backup I already had. I think this could be an APFS problem. I've never had this file-copy issue with HFS+ -that's why I was cloning Mojave to a clean HFS+ SSD. I just don't trust the APFS scheme which also caused problems in the past in my 2012 Mini.