Previous 1 7 8 9 10 11 Next 233 Replies Latest reply: Mar 9, 2015 12:02 PM by Jyri Palm Go to original post
  • Ed Newman Level 1 Level 1 (0 points)

    Just to add a data point to this thread, I've also seen symlink corruption. Experienced hangs on Aperture startup that were traced back to corrupt symlinks in framework directories within application package. Only appears to have started after upgrade to larger disks (6Tb boot drive across two 3Tb drives in JBOD). This is on an older Mac Pro (mid 2008). Software RAID config also had same problem in mirror mode. These are new drives and Mac OSX was completely reinstalled from scratch to try to diagnose Aperture hang.

     

    Would love to solve this as symlink corruption comes back again every week or so. Hasn't been clear whether this was due to Aperture saving state or something else.

     

    Please can someone confirm whether reconfiguring to smaller boot size mitigates problem?

  • agorstan Level 1 Level 1 (0 points)

    Same problem here, getting corrupted symbolic links in my containers folder. I too have upgraded to a 3TB drive.

  • btcreeper Level 1 Level 1 (0 points)

    Partition your drive if it's 3TB or larger.  I was having system problems constantly up until I partitioned the drive into smaller drives.  My symbolic link corruption issues have disappeared.  I haven't needed to reinstall OSX since I partitioned.  The only problem I'm having now is related to Lightroom 4.2 where every 3-4 days the symbolic links are breaking for different files within the application.  This has only been related to Lightroom and not the OS.  Maybe it's time for a new disk.

  • sgirard Level 1 Level 1 (40 points)

    Partitioning my 3TB Seagate drive (ST3000DM001) did not work for me. Everything seemed fine for a few days, but then Mail.app beachballed while starting up. After that, I found that my Address Book would not autocomplete email addresses when creating a new email message.

     

    I found that the symlink to the AddressBook at this location:

    ~/Library/Containers/com.apple.mail/Data/Library/Application\ Support was corrupt.

     

    Instead of looking like this:

    AddressBook -> ../../../../../Application Support/AddressBook

     

    the symlink looked like this:

    AddressBook -> O

     

    This AddressBook symlink has been corrupted at least 3 times since installing Mountain Lion (and upgrading my boot drive to the 3TB Seagate). Interestingly, after the corruption today, I found three items in my trash that I think are related:

    a 10 byte file named: O

    a 10 byte file named: O 11-39-08-346

    a 10 byte file named: O 15-20-04-863

    There does not appear to be any content in any of these files (viewed with Textedit).

     

    At this point my plan is to reinstall my old 1TB boot drive and reinstall Mountain Lion clean. I am wondering if Mountain Lion and the drive controllers on these big drives are not cooperating.

     

    This in on a 2008 Mac Pro and I have found the corrupt symlinks problem in various other places in the filesystem. For example, I found several corrupt symlinks to the llvm libraries in this location: /usr/bin/

  • Ed Newman Level 1 Level 1 (0 points)

    Sadly only response I have had from Apple on this topic, after posting a bug on the Developer site was "Take your machine to the genius bar"!

  • jas0nfl0yd Level 1 Level 1 (0 points)

    I think most of us on this thread are more qualified to what Apple refers to as so-called "Geniuses".

  • sgirard Level 1 Level 1 (40 points)

    I think I have resolved this issue on my 2008 Mac Pro. I think it was either a bad Mountain Lion install, or a conflict between the 3TB Seagate drive and Mountain Lion.

     

    Here's what I did: I reinstalled my old 1TB drive, did a clean install of Mountain Lion on that drive, and then I used Migration Assistant to copy my data to the old drive. (My apologies to those of you hoping for a more technical solution.)

     

    To anyone who is still experiencing the symlimk corruption, maybe you can try a clean install of Mountain Lion and then migrate your data using Migration Assistant. Since I changed two variables at the same time (hard drive and reinstall) I don't know which of the two solved my problem. Also, if you are finding 10 byte files with funny file names in your trash, you may be experiencing symlink corruption and not even know it (see my post above).

     

    Good luck to everyone.

  • dburr Level 1 Level 1 (15 points)

    sgirard wrote:

     

    I think I have resolved this issue on my 2008 Mac Pro. I think it was either a bad Mountain Lion install, or a conflict between the 3TB Seagate drive and Mountain Lion.

     

    Here's what I did: I reinstalled my old 1TB drive, did a clean install of Mountain Lion on that drive, and then I used Migration Assistant to copy my data to the old drive. (My apologies to those of you hoping for a more technical solution.)

     

    To anyone who is still experiencing the symlimk corruption, maybe you can try a clean install of Mountain Lion and then migrate your data using Migration Assistant. Since I changed two variables at the same time (hard drive and reinstall) I don't know which of the two solved my problem. Also, if you are finding 10 byte files with funny file names in your trash, you may be experiencing symlink corruption and not even know it (see my post above).

     

    Good luck to everyone.

    Unfortunately for me it definitely appears to be an incompatibility with >1.5 TB drives. I have tried multiple clean installs of both Lion and Mountain Lion, I have even tried running with no third party software/kernel extensions/drivers/etc., but the problem continues to crop up.

  • marcosw Level 1 Level 1 (0 points)

    dburr wrote:

     

    Unfortunately for me it definitely appears to be an incompatibility with >1.5 TB drives. I have tried multiple clean installs of both Lion and Mountain Lion, I have even tried running with no third party software/kernel extensions/drivers/etc., but the problem continues to crop up.

     

    I don't see the problem with a 2 TB drive, but did with a 4 TB drive.  I just ordered a MacPro and am planning on running tests with a set of known good 1 TB drives using 2 or 4 drives in Raid 0.  If the problem does not occur with either set of 2 drives but does occur with 4 drives that should definitely rule out a hardware issue with the drives.

  • mattloper Level 1 Level 1 (0 points)

    I experience the problem with volumes > 2TB, regardless of RAID configuration. I've tried RAID 0, RAID 1, and no RAID, and the problem keeps coming back if the volume is bigger than 2 TB. I've also tried replacing the drives, and reinstalling Mountain Lion, and changing RAID configurations, many times; the only thing that works for me is having the volume (which may span multiple drives, or not, doesn't matter for me) <= 2TB.

    But I want to be more precise: 2TB configurations don't exhibit symlink corruption, and 3TB and 4TB configurations do exhibit symlink corruption. I don't know the exact boundary between "working" and "not" in terms of disk size.

     

    I have a MacPro4,1 (from 2009), and I'm on Mountain Lion.

  • marcosw Level 1 Level 1 (0 points)

    I wrote:

     

    I don't see the problem with a 2 TB drive, but did with a 4 TB drive.  I just ordered a MacPro and am planning on running tests with a set of known good 1 TB drives using 2 or 4 drives in Raid 0.  If the problem does not occur with either set of 2 drives but does occur with 4 drives that should definitely rule out a hardware issue with the drives.

     

    Running Mountain Lion on a MacPro3,1 with 4x1TB drives in RAID 0 showed problems within a couple of days:

     

      16 lrwxr-xr-x  1 root  wheel  12 Mar  7 15:21 /usr/bin/gcc@ -> m/??S?/.&H?w

     

    I originally ran into this issue several months ago on my iMac when upgrading the 2TB internal drive to 4TB.  Since there is nothing duplicated between the two machines, as far as I'm concerned this cannot be a hardware issue.

     

    marcos

  • btcreeper Level 1 Level 1 (0 points)

    The problem has come back, very frustrating.

     

    I run this command periodically to see what's broken in the System directory:

     

    sudo find -L /System -type l -print0 |xargs -0 ls -l

     

    Then recreate the symbolic link using:

     

    ln -sf {source} {link}

     

     

    Lately it's been the java and diskimage frameworks that are screwed up.  Does anyone know of a way to monitor a directory or file for changes?  For now I'm going to setup a cronjob that checks every 5 minutes to see if I can narrow down the times when this happens then search the logs for activity.

     

    @OSX

  • marcosw Level 1 Level 1 (0 points)

    My experience is that the only links which become corrupted are those which are read.  I.e. on my iMac it was links related to Aperture and Mail and on my MacPro it was gcc and other links related to compiling code.  This is precisely what those two machines were used for.

     

    As further evidence I switched to an SSD boot volume and am using the same 4x1TB RAID 0 array that I had problems with for /User and haven't had any problems for 3 days. 

     

    btcreeper wrote:


    Does anyone know of a way to monitor a directory or file for changes? 


     

    You can add the -maxdepth option to find to not search subdirectories, i.e.

     

      sudo find -L /usr/bin -maxdepth 1 -type l -print0 |xargs -0 ls -l

     

    only checks the /usr/bin directory and

     

      sudo find -L /usr/bin/gcc -maxdepth 0 -type l -print0 |xargs -0 ls -l


    only check that one file. 

     

    I don't think find with -maxdepth 0 is very resource intensive, but if you prefer not using find an alternative for monitoring a single link would be to use ls and grep for the expected link, i.e.:

     

      ls -l /usr/bin/gcc | grep -q llvm-gcc-4.2

     

    This returns an exit status of 0 if the link is okay and 1 otherwise.

  • sgirard Level 1 Level 1 (40 points)

    My symlink corruption followed the same pattern as yours: links that were read (Address Book) and links used in compiling code (llvm).

     

    It's been almost a month since I went back to my 1TB boot drive and I have not experienced any more symlink corruption.

     

    When I experienced symlink corruption, it was only on the internal boot volume. However just because I didn't notice it anywhere else, doesn't mean it didn't  or couldn't happen; I am just not aware of it ever happening on any external drives or internal non-boot drives. I am using several large external drives for backup and file storage. I have done a quick look on those drives for symlinks and didn't find many, so maybe that explains the lack of symptoms on those drives.

     

    Another strange result of the symlink corruption was the appearance of the (3) empty 10 byte files in my trash when corruption occurred (see my post above). I saw this consistently. Has anyone else seen this behavior/symptom? I have not found any more of these files in my trash since downgrading my boot drive to the older 1TB device.

     

    The 3TB drive that exhibited symlink corruption was Seagate model number ST30000DM001 with firmware CC43.

    The Mac is a 2008 Mac Pro running Mountain Lion 10.8.2

  • btcreeper Level 1 Level 1 (0 points)

    I'm using this drive:

    Seagate Barracuda XT - ST33000651AS

    3 TB

    7200RPM

    SATA 6 Gb/s

    64MB Cache

    3.5 Inch Internal Drive

     

    I think it's time for a new non-Seagate drive.

     

Previous 1 7 8 9 10 11 Next