can you disable trim?
Disabling SIP is not recommended because of security reasons.fixed my slow boot by disabling SIP
fixed my slow boot by disabling SIP
Again, disabling trim is not a good solution. Trim is important to the efficiency and life of your ssd.
In my opinion, if disabling trim is the only option ... there is not option.
https://support.apple.com/en-us/HT204899
System Integrity Protecton, a security technology that helps protect your Mac from malicious software.
Disabling SIP is not recommended.
5 seconds from chime to white Apple logo and 25 seconds more to the log-in screen, so I‘m happy!Nope.
5 seconds from chime to white Apple logo and 25 seconds more to the log-in screen, so I‘m happy!
I disabled SIP as well as gatekeeper. Didn't do a thing. Only when I disable trim do boot times return to a normal 20 secs (from about a minute). Since I don't want to disable trim, I'm stuck with slow boot times until apple fixes it in the .3 or .4 release (and I think that's probably being optimistic).
But since SIP was the secret to your slow boot times, and trim is the cause of mine, it's anyone's guess what the hell is actually going on here.
How do disable trim on boot time?
Does today's update fix this issue?
I have exactly the same thing with also a mbp mid 2012.I’m experiencing the exact same thing on my Mid-2012 MacBook Pro with a self installed SSD. Boot gets stuck around 70%, hangs, the screen goes black for about 10-15 seconds and then the boot finishes and the desktop appears. Anyone else experiencing the black screen portion?
Lack of TRIM was a big problem for my external FireWire drive - Samsung 850 EVO. It would slow down VERY quickly. Speeds would drop to below HD random speeds. Literally less than 1 MB/s. Absolutely horrible.I concur with the two posters a little ways above regarding both TRIM and SIP.
I -routinely- disable SIP on all my Macs.
The Mac OS ran fine -before- Apple came up with the concept of SIP, and I've had no problems insofar as the "protection" business is concerned.
I've been booting and running my Mac off USB3 for nearly 5 years.
TRIM has NEVER arisen as an issue.
Agreed with the poster who said its importance is overrated.
Possible workaround for High Sierra vs. TRIM:
- Normally, leave TRIM off
- Occasionally, boot from another source (perhaps the recovery partition), and run Disk Utility's repair disk function on your boot volume. When DU runs, it should automatically "TRIM unused blocks".
- This will get the boot drive "back into shape" insofar as TRIM matters
- When done, just reboot normally (with TRIM off).
Once every two weeks should work...
Request:
If there is someone running with TRIM disabled, could you try booting externally, running DU's repair disk function, and observing as to whether it actually does "TRIM unused blocks"... or not... and report back here?
On Late 2012 iMac 8 GB RAM 1 TB Rotational HD and Erase and Clean install 10.13.1 and also getting 2/3 load, black screen for 1 to 3 secs and then continues to load to Login screen. Have verified Filesystem Repair Logs and finding the following which is adding some time to boot up. Otherwise, system is working fineI’m experiencing the exact same thing on my Mid-2012 MacBook Pro with a self installed SSD. Boot gets stuck around 70%, hangs, the screen goes black for about 10-15 seconds and then the boot finishes and the desktop appears. Anyone else experiencing the black screen portion?
On Late 2012 iMac 8 GB RAM 1 TB Rotational HD and Erase and Clean install 10.13.1 and also getting 2/3 load, black screen for 1 to 3 secs and then continues to load to Login screen. Have verified Filesystem Repair Logs and finding the following which is adding some time to boot up. Otherwise, system is working fine
fsck_hfs started at Sun Nov 5 10:17:33 2017
** /dev/rdisk0s2 (NO WRITE)
** Root file system
Executing fsck_hfs (version hfs-407.1.3).
fsck_hfs completed at Sun Nov 5 10:17:33 2017
/dev/rdisk0s2: fsck_hfs started at Sun Nov 5 10:18:06 2017
/dev/rdisk0s2: /dev/rdisk0s2: ERROR: volume / is mounted with write access. Re-run with (-l) to freeze volume.
/dev/rdisk0s2: fsck_hfs completed at Sun Nov 5 10:18:06 2017