After Trimforce MBP does not Boot "No Parking" sign

Discussion in 'OS X Yosemite (10.10)' started by sudiste, Jul 1, 2015.

  1. sudiste macrumors newbie

    Jul 1, 2015

    Already posted here [1] but my post was undergoing by various discussions.
    no idea if Hell was riding me this morning, i never install the newest updates on the first day, but this morning i have pushed the buttons without thinking and enabled the trimforce function,
    First i have disabled and uninstalled "Trim Enabler" while doing this i re-enabled the Kext signing.

    Executed "Trimforce enable" after a reboot it was all good and wanted to see if there is a way to check if it's enabled or not, so i reapplied the command again, bad idea!
    Now the machine boots and stops with the No Park Sign.
    Bootet in Safe and Single user mode, same problem.
    Started in Recovery Mode, the Disk is visible and the Disk Check did not found any errors.
    Still in the Recovery Mode i was able to locate the binary in /usr/bin
    Tried to "trim force disable" on the terminal, i can call the command and i can confirm with Yes but at the end it says:
    "touch: /System/Library/Extensions/: Read-only file system"

    Would be cool if somebody can help me undo this.

    The machine is a MBP early 2011 with a Intel 520 SSD and 240Gb capacity.

  2. sudiste thread starter macrumors newbie

    Jul 1, 2015
    Hmm, nobody knows how to get RW access on the Local Volume via Terminal?
    Have searched in Google, but didn't found yet the golden command.

    Any Help is appreciated.
  3. sudiste thread starter macrumors newbie

    Jul 1, 2015
    OK, one step done and just for the record, to have RW access in the Recovery Console (Terminal) type
    mount -o rw /

    Have now Trimforce disabled, but still gets the No Parking Sign at Boot, how debug where it's stuck?
    In Verbose mode it doesn't talk much, after loading
    "AppleUSBMultitouch Diver"
    it stops moving further.
  4. dyn macrumors 68030

    Aug 8, 2009
    IIRC the Intel 520 is a Sandforce drive which you should not use TRIM on since there are issues with its TRIM implementation.

    You may need to restore from backup.
  5. Draeconis macrumors 6502a

    May 6, 2008
    I have trimforce enabled on an Intel 330 and an Intel 335, both machines just had this issue today for no reason.

    There are no issues I'm aware of using TRIM on these drives, and have been using TRIM in various forms since 2011 without incident until now.
  6. sudiste thread starter macrumors newbie

    Jul 1, 2015
    Thanks for your feedback,
    Today i have restored the machine from Nas Backup (Timemachine) without success, same issue,
    Now i'm restoring a older Backup from Thunderbolt disk.

    How have you acheved the recovery?
  7. Draeconis macrumors 6502a

    May 6, 2008
    This is because your command, while pointing at /Volumes/[volumename]/usr/bin/trimforce, isn't trying to make changes on /Volumes/[volumename]/, it's trying to make changes to root, which when you're in the Recovery HD partition, is a read-only partition.
  8. Draeconis macrumors 6502a

    May 6, 2008
    I'm not sure what the cause was, so it makes the issue hard to diagnose. Both machines previously had TRIM enabled via the script originally written by Grant Pannell, but the IOAHCIBlockStorage.kext that was modified would have been overwritten when installing OS X 10.10.4.
  9. Draeconis macrumors 6502a

    May 6, 2008
    Managed to fix it by running nvram boot-args=kext-dev-mode=1, rebooting, then running;

    nvram -d boot-args

    cd "/Volumes/Macintosh\ HD"

    rm -rf System/Library/Extensions/IOAHCIFamily.kext

    cp -r /System/Library/Extensions/IOAHCIFamily.kext System/Library/Extensions/IOAHCIFamily.kext

    chown -R root:wheel System/Library/Extensions

    chmod -R 755 System/Library/Extensions

    touch System/Library/Extensions

    kextcache -u "/Volumes/Macintosh\ HD"
  10. h9826790 macrumors G5


    Apr 3, 2014
    Hong Kong
    This will restore that system file back to the state that user before apply TRIM Enabler (or any other same method to modify the system file), which should able to fix the boot issue.

    However, after this action, the trimforce command may be no longer applicable (because that IOAHCIFamily.kext may be from 10.10.3). The user should (and I personally highly recommended) reinstall the OSX 10.10.4 once more to make sure all system files updated to the 10.10.4 version.
  11. sibelius101 macrumors newbie

    Aug 8, 2014
    I had this problem. I reinstalled 10.10.4 via the recovery partition. After rebooting everything is OK. Trim is enabled and all of my settings are still in place.
  12. Draeconis macrumors 6502a

    May 6, 2008
    Sorry yes, should have mentioned that this was run from Recovery HD, and it's really only to get you back up and running temporarily.

    After this you should be able to get back in, but I'd back up your account and reinstall OS X.

Share This Page

11 July 1, 2015