Finder pauses before accessing thunderbolt drive

New Mac Pro ( late 2013 ), latest Mavericks.
wd 8Tb My Book, thunderbolt.
if I try to access a folder on the drive and I haven't accessed the drive for a little while, like 10 minutes, the finder pauses up to 10 seconds before showing the contents of the folder.
Any idea why it would take this long and what do I do to remove this delay?
on a similar , maybe related , note, I use the drive to store video that I stream to a PS3 through a power line network. part way through the streaming the video will pause for 6-10 seconds , then resume. The only thing that has changed in this configuration is the new Mac pro. I was using a 2006 vintage macpro with internal drives before and never had a proble. Could this be related?

Any idea why it would take this long and what do I do to remove this delay?
It is probably spinning up the drive(s).

Similar Messages

  • Finder hangs when accessing external drive

    My finder hangs when accessing an external drive.
    It is specific to a drive the I created on my TC disk.
    That drive and TC work perfectly unless I mouint it and alter anything on that disk (I can read ok but writing causes a freeze.)
    The writing that I do is always ok; if I trash or move something it always ends up where I wanted it after a restart.
    The process looks like:
    I drag an item to the trash (or another directory) and the progress bar shows success down to 3 or 5 seconds and then it stops (curser becomes a spinning beach ball.)
    I can hear the tone of a successful transfer if I wait a little while but the finder is unresponsive untill I restart.
    Once restarted I can check the external disk and the file transer (to a directory or the trash) appears to have completed without corruption.
    I have repaired drives and permissions all over the place with no results.
    Can I just say that I tired of constant unnecessary updates that slow my computer, rearrange my settings and cause crashes and other problems that have to be researched and chased down through hours of online troubleshooting. I would love to have thoroughly tested software and hardware that just works without the hassle of having to constantly tweek my machine to get it to work consistantly.

    Are you saying you have this problem only with one drive, not with others?

  • Finder crashes when accessing network drive

    We have four macs on our network. When trying to access a volume on our network drive Finder crashes. The drive is accessible via FTP as well as From Windows Machines. Its only on Finder that we are having the problem. Everything use to work.
    Im on an iMac, my Finder totally spazes out. Blinking off an on. On another system it just crashes. On the other two systems it just won't access the drive & Finder closes.Just started today.
    If anyone know what this is please help!

    Hi Barry,
    Thanks for the suggestion. Unfortunately I did buy diskwarrior on my way home, ran it a few times. No success. It did identify problems it couldn't fix with a lot of the files that were in my suspect folder (a font folder) but since I can't access the files directly on my hard drive I can't get rid of them.
    I did follow your suggestion, but all that it did that I can see was scatter my folders on the desktop.
    Yet, while typing this, I just found a creative way to solve the problem!!! I was able to access the font folder in Bridge even though I couldn't access it otherwise. I deleted it in bridge and now things are working as normal!!! Thank God for Bridge. Amazing. Especially since that font folder has been on this machine for months, and the previous machine for years without ever causing a problem...

  • Finder crashes when accessing hard drive

    Everything was working fine until I installed Font Doctor and started using it to examine my fonts. It would crashed when I hit this one folder. I tried it again and identified the exact font folder that was causing the problem (or so I thought). I restarted the computer and decided to get rid of that font folder, but all my fonts are on my main hard drive, and everytime I click on the hard drive the finder crashes and comes up with a default window, so I can't access it. I can access files/programs through applications or user, and I can access specific files on the main hard drive through the programs but can't get into the hard drive directory.
    I did a search on this site and found this link:
    http://discussions.apple.com/thread.jspa?threadID=964617&tstart=90
    I thought it was the answer, especially since I had an old version of Stuffit on my system so I deleted Stuffit using the link enclosed. But when I did a search afterwards (after emptying the trash and restarting) it still showed stuffit things on my hard drive, not in the user or library folders which I can access, but on my main hard drive which I can't access.
    I looked at the code and it showed some of the same things that the previous poster mentioned.
    Here is some of the latest code after I restarted yet again:
    Mac OS X Version 10.4.10 (Build 8R2232)
    2007-07-24 18:31:50 -0700
    dyld: Library not loaded: @executable_path/../Frameworks/StuffIt.framework/Versions/A/StuffIt
    Referenced from: /Library/PreferencePanes/StuffIt AVR.prefPane/Contents/Resources/StuffItAVRDaemon.app/Contents/MacOS/StuffItAVRD aemon
    Reason: image not found
    2007-07-24 18:31:52.143 UniversalAccess[216] * -[NSBundle load]: Error loading code /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle/Contents/MacOS/ MagicMenuEnabler for bundle /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle, error code 2 (link edit error code 0, error number 0 ())
    2007-07-24 18:31:52.492 SystemUIServer[203] lang is:en
    2007-07-24 18:31:55.902 iCalAlarmScheduler[219] * -[NSBundle load]: Error loading code /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle/Contents/MacOS/ MagicMenuEnabler for bundle /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle, error code 2 (link edit error code 0, error number 0 ())
    terminate called after throwing an instance of 'IAException'
    terminate called after throwing an instance of 'IAException'
    terminate called after throwing an instance of 'IAException'
    2007-07-24 18:33:29.150 Safari[226] * -[NSBundle load]: Error loading code /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle/Contents/MacOS/ MagicMenuEnabler for bundle /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle, error code 2 (link edit error code 0, error number 0 ())
    2007-07-24 18:34:32.556 Mail[228] * -[NSBundle load]: Error loading code /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle/Contents/MacOS/ MagicMenuEnabler for bundle /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle, error code 2 (link edit error code 0, error number 0 ())
    2007-07-24 19:05:57.994 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:57.998 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:57.999 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.000 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.001 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.001 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.002 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.003 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.004 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.005 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.006 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.006 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.007 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.008 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.009 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.010 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.011 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.011 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.012 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.013 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.014 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.015 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.015 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.016 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.017 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:05:58.018 SyndicationAgent[276] WARNING: BestCalendarDateFromString - can't interpret: 'Tue 24 Jul 2007 17:35:46 -800'
    2007-07-24 19:07:55.169 Console[281] * -[NSBundle load]: Error loading code /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle/Contents/MacOS/ MagicMenuEnabler for bundle /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle, error code 2 (link edit error code 0, error number 0 ())
    Any ideas?
    Thanks so much!

    Hi Barry,
    Thanks for the suggestion. Unfortunately I did buy diskwarrior on my way home, ran it a few times. No success. It did identify problems it couldn't fix with a lot of the files that were in my suspect folder (a font folder) but since I can't access the files directly on my hard drive I can't get rid of them.
    I did follow your suggestion, but all that it did that I can see was scatter my folders on the desktop.
    Yet, while typing this, I just found a creative way to solve the problem!!! I was able to access the font folder in Bridge even though I couldn't access it otherwise. I deleted it in bridge and now things are working as normal!!! Thank God for Bridge. Amazing. Especially since that font folder has been on this machine for months, and the previous machine for years without ever causing a problem...

  • External hard drive connected to my airport extreme will no longer open, when navigating to it in Finder, the Finder window quits and reopens, cannot access hard drive, it is visible in airport utility, since the problem began I have updated firmware

    External hard drive connected to my airport extreme will no longer open, when navigating to it in Finder, the Finder window quits and reopens, cannot access hard drive, it is visible in airport utility, since the problem began I have updated firmware on Extreme as well as both of my Airport Expresses. Hard drive is USB connected to Extreme.

    Reboot the USB drive.. assuming it is powered.. or unplug and replug a self-powered drive.. (you should not use self-powered drives on AE before the latest model.. always use a powered hub).
    Does the drive now appear in finder..
    If not reboot both drive and the AE.. it should now appear.
    If it doesn't work with direct connection try a powered hub.. that can help.

  • Cannot access Seagate Thunderbolt drive since upgrade

    Just upgraded to Yosemite, now I cannot access my Seagate 3tb Thunderbolt drive. Any suggestions or patches?

    Yea that is a problem and expected
    If you are not trying to restore from that vault  the the easiest thing to do is just to create a new vault with the new setup and abandon the old vault.
    As vaults are only a snapshot of the current state of the library there is nothing to lose by doing this.
    If you are trying to recover the vault you can try this:
    Locate the vault in the Finder
    Select the vault (but don;t open it) and do a Get Info on it, Either right click and select Get Info from the menu or else select Get Info from the File menu or press command I (eye)
    In the Info window go to the Name and Extension section and change the extension from .apvault to .aplibrary.
    Now try double clicking the 'library' in Finder. Aperture should open and ask if you want to update the library. Say yes.
    At this point depending on why you recovered the vault you could use it as is or create a new vault from it.

  • LR3 can't find files after copying my previous hard drive to a new Lacie Thunderbolt drive

    I transferred my LR3 files from my WD hard drive to my new Lacie Thunderbolt drive and now I can only get the preview and it says the file is missing.  Is there a setting I need to change that I am not aware of?

    You have moved your image files outside of Lr (via your OS) and now Lr has lost the connection to your images. This happens every time you move images outside of Lr. Lr stores in its catalog - among all the other things - also the location of your images, and if the location stored in the catalog is different than the situation onyour hard drive you get the "missing" file message. "Missing" means that Lr does not "know" where your images are.
    You have to point Lr to the location of your image files to fix the broken link.
    In the Grid View (left side) in the folders panel you should see question marks in front of the folder names. That is Lr's indication that the link to the folders is broken.
    Go to the top-most folder in the hierarchy of the folders that show the question mark and right-click it (click with the right-hand button of you rmouse). Select <Find missing folder> in the fly-out menu, navigate to the coresponding folder on your LaCie and click on it. Lr will then also find the sub-folders under that folder on idt own - provided that you have not changed the folder names or the folder structure.
    If you have done that you have to "point" Lr to each folder individually with the procedure described above.
    BTW you will also get the "missing" message when you open Lr but your external drive is not switched on.
    WW

  • Trying to access my family pack email addresses to correct before moving over to icloud.  I can't find how to access it.

    I'm trying to access my family pack email addresses to correct before moving over to icloud.  I can't find how to access it. Can someone help me? 

    Welcome to the Apple Community.
    Connect it to iTunes with a USB cable and update it from the iTunes application.
    I have asked for your email address to be edited out. Posting your address in an open thread is a sure way to be bombarded by unwanted email, remember it will be here long after you have resolved your problem, for automated detection software to find.
    If you want people to contact you, enable others to see your email address in your profile.

  • Failure to access external drive (Thecus N2050)

    Hello,
    I have recently been unable to access my external hard drive -- a Thecus N2050 with two Seagate Barracuda drives (7200.10 500GB SATA2 3GB/S 7200RPM 16MB Cache) using RAID 1. My iMac is running OS X 10.5.5 Build 9F33.
    Upon turning on the external drive, all icons on the desktop disappear and the computer "freezes". I am unable to load a Finder window and access the contents of either hard drive (local or external). When the external drive is turned off, the desktop icons re-appear and everything works normally again.
    I tried accessing the external drive with another computer (a Mac Mini also running OS X 10.5.5 Build 9F33) and the problem was perfectly reproducible.
    I have accessed this external drive from both of these computers many times in the past without any problems, so I thought that the problem was with the external drive enclosure (a few months after the warranty expired, of course).
    However, I tried accessing this drive with my PowerBook G4 (running OS X 10.4.11 Build 8S165) ... and it worked fine. I disconnected it and tried once more to access it with either of the first two computers ... and it froze.
    I have been able to access this external drive from my iMac in recent months without incident; it was only last week that I discovered this problem. Nothing has been installed on these computers recently except for the regular OS updates. The only thing that the iMac and Mac Mini seem to have in common is that they are both running OS X 10.5.5 Build 9F33.
    Does this problem sound familiar to anybody else? Thanks in advance.

    I would consider trying the following:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • Can I create a OSX boot clone on an external thunderbolt drive and retain the original internal install as a bootable option for the rare times the MBP is mobile?

    Continuing my reaserch into the best upgrade options.
    I'm looking at thunderbolt storage.   But just just discovered that thunderbolt is apparently bootable...
    As the 2.5" sata HD in the MBP isnt the speediest thing in the world, I was wondering if people thought it was a good idea to clone my OSX install to a thunderbolt drive (currently contemplating a 4tb mirrored (2tb resultant vol) with a 250gb osx partition 250gb bootcamp partition and dividing the remaing space for time machine and win backup)
    the MBP mainly lives on the desk in the office and rarely is dis connected from its cluster of attachments.   But for when i do take it walk-about  can i leave the origional OSX install on the internal HD for mobile use?
    sorry for all the questions ( I feel like a noob again)
    also is there anyway to have two or more bootcamp drives? i'm not talking partitions within bootcamp but another complete bootcamp in its entirity....
    ta
    Stephen

    so once I've migrated bootcamp to the external thunderbolt drive I can use the space it occupyed on the internal HD for a partition for my home directory and all those other sharable assets...  point the internal and external copies of OSX at this and i't will remain current regardless of weather i'm connected to the external drives?
    That's the general idea but something's you need to be concerned about.
    1. I am not familiar with bootcamp so I do not know whether it can be run from an external drive.
    2. Before doing anything about moving your home directory make sure you backed up your original stuff on yet another disk.  Since you never attempted this before you could easily make a mistake and be hung out to dry if you cannot start over by reverting to the backup.  This is an important step not to be ignored.
    3. Contrary to what you read in the various web sites about moving your home directory, and there is plenty of them (google "move os x home directory"), I don't agree with the way they say to do the move, i.e, drag the home directory in the finder to the new location. 
    When I move the home directory I am always concerned about ownership and permissions info on the files which can be changed by simply moving the home dir in the finder.  So the safest way to protect against the is to use the terminal (in utilities) to create what's called a tar.gz (gz stand for gzip just another form of compression like zip is a form of compression) of your home dir and move tht tar.gz file to the new home dir location and then expand it.
    In terminal I would do the following (assume YOURACCOUNT is your current home directory):
    cd /Users
    tar czf  YOURACCOUNT.tar.gz YOURACCOUNT
    This will create the file YOURACCOUNT.tar.gz which you can now safely move to your new location.  Not only that you now have a backup copy of your current home dir in that compressed YOURACCOUNT.tar.gz file.
    Say you move YOURACCOUNT.tar.gz to a new drive called, NEWDRIVE.  Then in terminal,
    cd /Volumes/NEWDRIVE
    tar xzf YOURACCOUNT.tar.gz
    Now your YOURACCOUNT home directory is safely moved and all it's permissions and ownerships are persevered.  You still of course need to fix up the Accounts information to point to this new place as mentioned in those many articles on the topic.

  • Red Light on Promise Pegasus R4v Thunderbolt drive

    I was told by Promise to use the promise utility to fix this but I can't install the software downloaded from their site because it says Apple doesn't support it. It didn't come with a disk. Before I go and load all my data on this thing I want to know that drive is working right and a red light is not a good start, and knowing I can't use their software is even more troubling.

    I had this problem with an external G-Drive thunderbolt which I bought in August.  Started getting this message and replaced the drive at the Apple store under the 15 day return, and was very careful about not accidentally unplugging the replacement drive.  No problems until today. Yesterday, I accidentally unplugged the drive.  Now, after rebooting I am getting the message every 5-20 minutes.  So it appears there is some kind of reliability issue related to the drive state caused by a hot eject.  The vendor website the states the drive can be "damaged" by ejecting the drive without properly dismounting it through the finder.  Hopefully the problem is in a magnetic component that can be reformatted.
    Looking around I am seeing 5 or 6 threads that have come up in the last couple of months related to external thunderbolt drives.  This is obviously an issue that could sneak through QA.  So it appears to be a generic issue.  Maybe Yosemite would also fix it, but I'll start with a reformat.
    After I format this thing I will let you know what happens.
    Mac Pro OS X 10.9.5

  • Suddenly can't access shared drives on LAN but can access shared folders

    This just happened this past week.  Prior to last Monday everything had been working fine for over a year.  Here's the scenario:
    I have a LAN with a Tower Computer, a Desktop and a Laptop.  The tower computer has two external 2-bay cabinets connected via e-SATA.  One cabinet has two drives configured as Raid 1 (i.e. 1 mirrored logical drive and has the 'shared
    name' "Raid1-Array and the drive letter of Z: ), which is a repository for data that must be available to all computers on the LAN.  The other cabinet has two individual drives used for backup (stored offsite and only installed once
    a week).  One of the latter is for backup of the "local" Tower (Drive G: - not shared), and the other is shared for LAN backup of the Laptop ('shared name' "LT-Backup" and Drive F:).
    Suddenly this week, the laptop can no longer access the shared repository (Z:) nor its shared backup drive (F:) on the Tower.  As a temporary solution for the backup, I shared the laptop's backup folders of F:, and
    for some unknown reason the laptop can access those, but not the F: drive itself.  When I try to access Z: or F: using File Explorer I get an error message saying:
    "Windows cannot access \\TOWER-755\LT-Backup  You do not have permission to access
    \\TOWER-755\LT-Backup.  Contact your network administrator to request access"
    All of the computers are in the same "WORKGROUP" and the same "HomeGroup", and I've gone through all the Help & Support texts and have run every diagnostic that I could find, but all to no avail.
    Another creepy thing is that the desktop (the third computer on the LAN/WORKGROUP/HomeGroup) CAN access the drives, but that computer is only here temporarily while I'm working on it.  In light of this I'm assuming that the problem lies with the
    Laptop, but for the life of me I can't figure out what/how.
    I'd be very grateful for any/all help to resolve this mystery.
    Capt. Dinosaur

    any changes before this issue happen? any other device connected and facing same issue
    did you check folder share permission setting?
    how about you re-edit the setting for user name password

  • New Thunderbolt drive, How, or Do I even need to tell Lightroom where the Library is?

    I have learned, over time, to be very carful with Lightroom and now is no exception...
    I copied all of my files, the complete library of photos, over to a new Thunderbolt hard drive. I then erased and renamed the old firewire drive and now use that for a backup.:
    My question is: When I opened Lightroom it acted as if nothing had happened and all of the photos are showing. What is Lightroom doing? Is it using the old drive which is now a backup even though I renamed it? or, is Lightroom 5 so smart that it sees the new Thunderbolt drive and library and just decided on its own that 'this' is what is going to use?
    I have no idea what is going on, but since it is day 1 I want to be sure Lightroom is using the correct library, not the backup.
    Can someone help me determine that things are in place and working as they should?
    TIA,
    Ken

    JimHess wrote:
    I apologize for having to ask so many questions. But what was the name of the old drive before you renamed it? Additionally, if you go to the library module and right-click on one of your images, one of the options in Windows is to "Show in Explorer" and on the Mac I assume it would be to "Show in Finder". If you click on that option it should open your system browser and show you the folder where that file is located. And at the top of that window you should be able to see the name of the drive and folder you are looking at.
    The name of the old drive was "LaCie New 2TB" - I will now look at what comes up when I choose 'Show in finder' ( I'm on a Mac)
    Okay, back here and what I found was right-clicking on one of the images brings up "“A32Z7813.CR2” could not be used because the original file could not be found. Would you like to locate it?"
    So, even though I have no question marks or exclamation marks, Lightroom does not see the original Library or Catalog (which one is it?) of original images.
    So, I think the question is, How do I tell Lightroom to use the complete original files that are now on the new Thunderbolt drive?

  • IMac crashes when powering off external Thunderbolt drive

    Hi,
    I have an external LaCie d2 USB 3.0 drive that is connect to my iMac (27-inch, Mid 2011, 3,1 GHz Intel Core i5, 12 GB RAM) through Thunderbolt. Whenever I power off the drive by pushing the power button (yes I did verify: all partitions have been ejected correctly before in the Finder and verified in Disk Utility), the iMac crashes. It starts up again, displays a screen stating the computer was not shut down properly and then immediately restarts. After that it boots up fine.
    This started occurring after having installed 10.10.2 Beta. I did file a report with Apple. As this was beta software I decided to completely reinstall the iMac from scratch (a complete fresh install, just imported my documents manually after) and everything was working fine again (10.10.1). Boom, after having updated 10.10.2 yesterday the problem is back.
    I did manage to find a workaround: when I connect the drive through a UBS cable it works fine. Conclusion: this seems to be caused by a Thunderbolt related update in 10.10.2.
    Question: is any one else with an external Thunderbolt drive experiencing this and has perhaps found a fix?
    Thanks,
    Kurt
    Wed Jan 28 16:30:36 2015
    *** Panic Report ***
    panic(cpu 0 caller 0xffffff800341a46e): Kernel trap at 0xffffff80038e9774, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x00000000066ee000, CR4: 0x00000000000626e0
    RAX: 0x0000000000070001, RBX: 0xffffff8036919c00, RCX: 0x8883c87675b70011, RDX: 0xffffff81541e9088
    RSP: 0xffffff817bb0be90, RBP: 0xffffff817bb0be90, RSI: 0xffffff81541e9068, RDI: 0x0000000000000000
    R8:  0x0000000000987482, R9:  0xffffff8003a95740, R10: 0x000017d7912af429, R11: 0x000017d790927fa7
    R12: 0xffffff817bb0bf50, R13: 0xffffff7f85328044, R14: 0xffffff7f8533e978, R15: 0xffffff8003ad66c0
    RFL: 0x0000000000010202, RIP: 0xffffff80038e9774, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0
    Backtrace (CPU 0), Frame : Return Address
    0xffffff817bb0bb40 : 0xffffff800332fe41
    0xffffff817bb0bbc0 : 0xffffff800341a46e
    0xffffff817bb0bd80 : 0xffffff8003436683
    0xffffff817bb0bda0 : 0xffffff80038e9774
    0xffffff817bb0be90 : 0xffffff7f85328267
    0xffffff817bb0beb0 : 0xffffff7f8532bad7
    0xffffff817bb0bee0 : 0xffffff7f853281ed
    0xffffff817bb0bf00 : 0xffffff80033624f9
    0xffffff817bb0bfb0 : 0xffffff8003414dd7
          Kernel Extensions in backtrace:
             com.apple.driver.AppleAHCIPort(3.1)[93E1D2EC-50EE-3340-9676-0EA1E0B1AD45]@0xfff fff7f85324000->0xffffff7f8533efff
                dependency: com.apple.iokit.IOAHCIFamily(2.7.5)[DAF0353B-16D5-385A-A0F3-FD5CF3BA07F2]@0xfff fff7f84706000
                dependency: com.apple.iokit.IOPCIFamily(2.9)[56AD16B5-4F29-3F74-93E7-D492B3966DE2]@0xffffff 7f83b24000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    14C109
    Kernel version:
    Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64
    Kernel UUID: DCF5C2D5-16AE-37F5-B2BE-ED127048DFF5
    Kernel slide:     0x0000000003000000
    Kernel text base: 0xffffff8003200000
    __HIB  text base: 0xffffff8003100000
    System model name: iMac12,2

    Same issue:
    - 4TB LaCie d2 Thunderbolt & USB3.0 drive (model # 9000303)
    - iMac (27’’ mid-2011), Thunderbolt firmware version 25,1 and Port Micro firmware version 2.1.3 (as seen in System Information)
    - OS X Yosemite 10.10.2
    Unmounting LaCie d2 disk partitions is OK: the drive spins down and goes to sleep without problem. However when I take the power off (with the small switch at the rear of the unit), the iMac experiences a kernel panic.
    This issue did not occur with Yosemite 10.10.1, and does not occur either with another LaCie drive (8TB LaCie 2big Thunderbolt drive, model # 9000246). So the issue is specific to OS X 10.10.2, and only certain models of drive(s).
    We need a fix from Apple - the Operating System should be rock-solid in any circumstances.
    Curiously, OS X does not write a kernel panic log with every occurrence. It’s only after the 3rd or 4th kernel panic that it would actually produce this log:
    ===============
    Sat Jan 31 15:57:30 2015
    *** Panic Report ***
    panic(cpu 0 caller 0xffffff802241a46e): Kernel trap at 0xffffff80228e9774, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000002565b000, CR4: 0x00000000000626e0
    RAX: 0x0000000000070001, RBX: 0xffffff804e6e9000, RCX: 0xcb694f8798fc00ec, RDX: 0xffffff81e115d088
    RSP: 0xffffff820d1f3e90, RBP: 0xffffff820d1f3e90, RSI: 0xffffff81e115d068, RDI: 0x0000000000000000
    R8:  0x0000000000987939, R9:  0xffffff81e115d068, R10: 0x0000031b3cf5cc6a, R11: 0x0000031b3c5d5331
    R12: 0xffffff820d1f3f50, R13: 0xffffff7fa4295044, R14: 0xffffff7fa42ab978, R15: 0xffffff8022ad66c0
    RFL: 0x0000000000010202, RIP: 0xffffff80228e9774, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x0
    Backtrace (CPU 0), Frame : Return Address
    0xffffff820d1f3b40 : 0xffffff802232fe41
    0xffffff820d1f3bc0 : 0xffffff802241a46e
    0xffffff820d1f3d80 : 0xffffff8022436683
    0xffffff820d1f3da0 : 0xffffff80228e9774
    0xffffff820d1f3e90 : 0xffffff7fa4295267
    0xffffff820d1f3eb0 : 0xffffff7fa4298ad7
    0xffffff820d1f3ee0 : 0xffffff7fa42951ed
    0xffffff820d1f3f00 : 0xffffff80223624f9
    0xffffff820d1f3fb0 : 0xffffff8022414dd7
          Kernel Extensions in backtrace:
             com.apple.driver.AppleAHCIPort(3.1)[93E1D2EC-50EE-3340-9676-0EA1E0B1AD45]@0xfff fff7fa4291000->0xffffff7fa42abfff
                dependency: com.apple.iokit.IOAHCIFamily(2.7.5)[DAF0353B-16D5-385A-A0F3-FD5CF3BA07F2]@0xfff fff7fa365a000
                dependency: com.apple.iokit.IOPCIFamily(2.9)[56AD16B5-4F29-3F74-93E7-D492B3966DE2]@0xffffff 7fa2b24000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    14C109
    Kernel version:
    Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64
    Kernel UUID: DCF5C2D5-16AE-37F5-B2BE-ED127048DFF5
    Kernel slide:     0x0000000022000000
    Kernel text base: 0xffffff8022200000
    __HIB  text base: 0xffffff8022100000
    System model name: iMac12,2 (Mac-942B59F58194171B)

  • Cinema Display hookup via a Thunderbolt drive

    I believe it's possible to run a Cinema Display from my MBP via a Thunderbolt drive, going from the MBp to the TB and then, via a Mini-display to DVI cable, into the display.
    I've hooked it up this way with the display also plugged into its power supply and usb'd into the MBP: nothing
    When I click 'Find displays' I hear activity in the thunderbolt drive (a Lacie 2big) but that's about it. Nothing shows on the Cinema Display.
    I'm doing somethin wrong probably, a familiar scene.
    Anyone done this successfully?
    (I'm running 10.7.3)

    A dvi display with a resolution greater than 1920 x 1200 requires a dual link dvi adapter.  I assume you are using a single link dvi adaper (or cable).

Maybe you are looking for