Orphaned blocks after emptying Trash

Discussion in 'OS X Mountain Lion (10.8)' started by NanoNyrd, May 31, 2013.

  1. NanoNyrd, May 31, 2013
    Last edited: May 31, 2013

    NanoNyrd macrumors regular

    Dec 1, 2011

    I am constantly (as in several times per week) getting minor corruption of my main drive (256 GB SSD). It always begins with emptying the Trash, every so often that will result in an error stating that one or more files are in use. Usually (but not always) I can get rid of them by rebooting (restarting Finder also worked today), but afterwards Disk Utility complains about orphaned blocks.

    I then boot in recovery mode, repair the disk, and the problem is solved. Until it reappear a few days later. :confused:

    What could be causing this? And what could I do to fix it?
  2. benwiggy macrumors 68020

    Jun 15, 2012
    Is this an SSD suppled by Apple, or one that you fitted yourself? If so, what model of SSD, and what Mac?

    At what point does Disk Utility complain about "orphaned blocks"? Is this in a Verify Disk procedure after the reboot?
  3. Mr. Retrofire macrumors 603

    Mr. Retrofire

    Mar 2, 2010
    Sounds like a problem with a non-Apple SSD or like a software problem (TRIM Enabler?).
  4. NanoNyrd thread starter macrumors regular

    Dec 1, 2011
    It is an original SSD in a MacBook bought on the net from Apple a couple of years back (where you could get MacBooks with SSD on the net, but not in stores). I have never dared to mess with TRIM.

      Capacity:	251 GB (251,000,193,024 bytes)
      Model:	APPLE SSD TS256B                        
      Revision:	AGAA0206

Share This Page