Contribute
Register

[Guide] Avoid APFS conversion on High Sierra update or fresh install

Just a quick question: Should I disable TRIM on an APFS that doesn't see any performance impact?

Background: I did a clean install of macOS 10.13, avoiding APFS, and thus afterwards enabled TRIM. I then did an upgrade to macOS 10.13.1 (via the full 5 gig installer), where I forgot to disable the APFS-upgrade :rolleyes:. As the TRIM settings carried over I am now on APFS with TRIM. I don't see any performance impact whatsoever, so now I'm just wondering should I disable TRIM? What are the pros and cons?
 
Just a quick question: Should I disable TRIM on an APFS that doesn't see any performance impact?

Background: I did a clean install of macOS 10.13, avoiding APFS, and thus afterwards enabled TRIM. I then did an upgrade to macOS 10.13.1 (via the full 5 gig installer), where I forgot to disable the APFS-upgrade :rolleyes:. As the TRIM settings carried over I am now on APFS with TRIM. I don't see any performance impact whatsoever, so now I'm just wondering should I disable TRIM? What are the pros and cons?

There is no APFS conversion on updating from 10.13 -> 10.13.1.
 
There is no APFS conversion on updating from 10.13 -> 10.13.1.
When you do an install/upgrade from the full (~5 gig) 10.13.1 installer (and not from the 10.13.0 -> 10.13.1 upgrade) it does happen (well it did to me anyways). But what asking for is pros and cons of disabling TRIM on an APFS when everything actually runs okay.
 
When you do an install/upgrade from the full (~5 gig) 10.13.1 installer (and not from the 10.13.0 -> 10.13.1 upgrade) it does happen (well it did to me anyways). But what asking for is pros and cons of disabling TRIM on an APFS when everything actually runs okay.

Working TRIM always preferred, but probably not necessary as most SSDs have enough firmware support to run without TRIM.
 
There is no APFS conversion on updating from 10.13 -> 10.13.1.
I failed to update during this process, it seems like rebooting between update (black background with apple logo)
 
I failed to update during this process, it seems like rebooting between update (black background with apple logo)

Off-topic.
Open a separate thread with complete problem reporting files as per FAQ.
 
Hi, I'm getting black screen too. I've pasted the startosinstall code to terminal, it booted, picked the install MacOS Sierra then loading bar with Apple logo appeared, bar filled 60%ish, then black screen and sometimes restart sometimes nothing, it sits there with black screen.

Any suggestions?

Edit: I read a few posts and see that someone tried to read screen with a flash light, and turns out that's what happened to me too.

After the first reboot, I pick install MacOS Sierra, Apple logo with loading bar gets half then waits a bit then backlight turns off. I checked the screen with a flashlight, bar completed and installer appeared. 41 mins remaning. Then it restarted, I selected install MacOS again, same thing happened but this time at the end installer gave an error. "MacOS could not be installed on your computer. An error occured while verifying firmware. Quit the installer to restart your computer and try again."

First, why backlight turns off? Second, How to verify firmware without an error?

Thanks.
 
Last edited:
Hi, I'm getting black screen too. I've pasted the startosinstall code to terminal, it booted, picked the install MacOS Sierra then loading bar with Apple logo appeared, bar filled 60%ish, then black screen and sometimes restart sometimes nothing, it sits there with black screen.

Any suggestions?

Edit: I read a few posts and see that someone tried to read screen with a flash light, and turns out that's what happened to me too.

After the first reboot, I pick install MacOS Sierra, Apple logo with loading bar gets half then waits a bit then backlight turns off. I checked the screen with a flashlight, bar completed and installer appeared. 41 mins remaning. Then it restarted, I selected install MacOS again, same thing happened but this time at the end installer gave an error. "MacOS could not be installed on your computer. An error occured while verifying firmware. Quit the installer to restart your computer and try again."

First, why backlight turns off? Second, How to verify firmware without an error?

Thanks.

Off-topic.
Open a separate thread with problem reporting files as per FAQ.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 
Used for first test:

https://www.tonymacx86.com/threads/...s-high-sierra-on-any-supported-intel-based-pc
(Script executes OK!)

(used the Convert script, to prevent APFS and KEEP HFS+J

result while installing:

macOS could not be installed on your computer - An error occured installing macOS. To use Apple Diagnostics.. etc,


Your suggestion:


# list /Volumes to remind yourself of the name you gave it
ls -l /Volumes
# then change your working directory to it (in my case, I used '1013')
cd /Volumes/1013
# now change to the "macOS Install Data" directory
cd "macOS Install Data"
# now fix the minstallconfig.xml with PlistBuddy
/usr/libexec/PlistBuddy -c "Set :ConvertToAPFS false" minstallconfig.xml

(Executes OK!)

Also this gives same error:
macOS could not be installed on your computer - An error occured installing macOS. To use Apple Diagnostics.. etc,

SO for a Z68XP-UD3, you cannot keep HFS+J for now....


The recommended methods are in post #1.

This post contains alternatives that may still be useful in scenarios that post #1 methods may not be possible.


Fresh install scenario (or update), modifying minstallconfig.xml using PlistBuddy

Refer to this guide for an overview of the installation process from USB:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

The process involves creating an installer USB with createinstallmedia, then booting that USB (via Clover on the same USB). You then run the installer, create an HFS+J partition suitable for macOS with Disk Utility, then point the installer to that partition.

Even though you create a new HFS+J partition, if the target is an SSD, the installer will still convert it to APFS.

To avoid that, after running the installer, and upon the first reboot where you would be normally directing Clover to boot the next stage of the installer by selecting "Boot macOS Install from ...", instead, boot the "install_osx" partition on USB again. When that is finished booting, choose Terminal from the Utilities menu.

Now, in Terminal, navigate to your target volume:
Code:
# list /Volumes to remind yourself of the name you gave it
ls -l /Volumes
# then change your working directory to it (in my case, I used '1013')
cd /Volumes/1013
# now change to the "macOS Install Data" directory
cd "macOS Install Data"
# now fix the minstallconfig.xml with PlistBuddy
/usr/libexec/PlistBuddy -c "Set :ConvertToAPFS false" minstallconfig.xml

That's it! Now you're ready to quit Terminal, reboot, and continue the installation process by booting the "Boot macOS Install from ..." partition. When you're done, you'll have a fresh install on HFS+J instead of APFS.


Fresh install scenario (or update), modifying minstallconfig.xml using vi


Refer to this guide for an overview of the installation process from USB:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

The process involves creating an installer USB with createinstallmedia, then booting that USB (via Clover on the same USB). You then run the installer, create an HFS+J partition suitable for macOS with Disk Utility, then point the installer to that partition.

Even though you create a new HFS+J partition, if the target is an SSD, the installer will still convert it to APFS.

To avoid that, after running the installer, and upon the first reboot where you would be normally directing Clover to boot the next stage of the installer by selecting "Boot macOS Install from ...", instead, boot the "install_osx" partition on USB again. When that is finished booting, choose Terminal from the Utilities menu.

Now, in Terminal, navigate to your target volume:
Code:
# list /Volumes to remind yourself of the name you gave it
ls -l /Volumes
# then change your working directory to it (in my case, I used '1013')
cd /Volumes/1013
# now change to the "macOS Install Data" directory
cd "macOS Install Data"

Now, still in Terminal, edit the minstallconfig.xml file with vi:
Code:
vi minstallconfig.xml

You will find code:
Code:
    <key>ConvertToAPFS</key>
    <true/>

Your goal is to change the true to false.

If you know how to use vi, this will not be a problem. Otherwise, follow the instructions below very carefully:
- arrow such that the cursor is at the 't' in 'true'
- press the Del key (forward delete) four times (this removes 'true')
- press i (this puts vi into insert mode)
- type 'false' (without the quotes)
- press Esc (this takes vi out of insert mode)

The result should look like:
Code:
    <key>ConvertToAPFS</key>
    <false/>

No other changes should be made.

If the file looks good:
- press ':wq' (without the quotes) and press enter (':wq' saves the file and exits vi)

If the file doesn't look right, don't save it:
- press ':q!' (without the quotes) and press enter

That's it! Now you're ready to quit Terminal, reboot, and continue the installation process by booting the "Boot macOS Install from ..." partition. When you're done, you'll have a fresh install on HFS+J instead of APFS.
 
Used for first test:

https://www.tonymacx86.com/threads/...s-high-sierra-on-any-supported-intel-based-pc
(Script executes OK!)

(used the Convert script, to prevent APFS and KEEP HFS+J

result while installing:

macOS could not be installed on your computer - An error occured installing macOS. To use Apple Diagnostics.. etc,


Your suggestion:


# list /Volumes to remind yourself of the name you gave it
ls -l /Volumes
# then change your working directory to it (in my case, I used '1013')
cd /Volumes/1013
# now change to the "macOS Install Data" directory
cd "macOS Install Data"
# now fix the minstallconfig.xml with PlistBuddy
/usr/libexec/PlistBuddy -c "Set :ConvertToAPFS false" minstallconfig.xml

(Executes OK!)

Also this gives same error:
macOS could not be installed on your computer - An error occured installing macOS. To use Apple Diagnostics.. etc,

SO for a Z68XP-UD3, you cannot keep HFS+J for now....

You have a separate/unrelated issue.
Open a separate thread in the appropriate forum.
 
Back
Top