Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.I'm sorry—PR files?
Actually, TRIM is always enabled on NVMe.Hey RehabMan, thanks for your contribution to the community.
I have the latest high sierra build on an NVME drive with APFS. I read that TRIM is permanently enabled on these drives with APFS, which may be a big factor in my 2-3 minute boot time. I'm now thinking about whether it is worth the risk of copying my data over to another drive, reformatting into HFS+, and copying it back.
From what you know about the Mojave beta, is this something that will continue to be a problem or will this TRIM issue be fixed?
Hmm, so I may be better off just booting off a slower, non-NVME SSD formatted with HFS+JYes. TRIM is enabled at a lower level than file system choice.
The problem can be avoided with HFS+J because we can disable TRIM.Hmm, so I may be better off just booting off a slower, non-NVME SSD formatted with HFS+J
Will probably still be a problem as a full TRIM will still likely be performed. It is something you could always try. I use NVMe only for Windows currently.If I then stored my applications and documents on the NVME would that be fine with boot or will boot be slowed just because of the presence of an NVME even if it isn't being used as the boot drive.
As per rules, please update your hardware profile to allow others to help you easierThanks for all the information on this topic - I was able to sucessfully install HS 10.13.6 on a Samsung 840 EVO SSD with the .xml tweak.
The system seems to work well bar some driver issues BUT I can only boot off the installer USB. Further investigation revealed that the SSD only has the single partition and no EFI boot partition. Previously I had installed using APFS, also succesfully, and noticed that there were FOUR partitions created by the installer including EFI, Recovery, the main system and a preinstaller (I forget the details).
Has the xml hack resulted in the installer not creating the necessary boot partition?