TM issue: can't access share on NAS: "...original item can't be found"

Discussion in 'macOS' started by olee, Nov 24, 2010.

  1. olee macrumors newbie

    Joined:
    Nov 24, 2010
    #1
    Time Machine was making a backup to my NAS (a Lacie Network Space 2), when I suddenly got a power failure in my apartment. After that I can't access the share anymore. I can connect to the share but when I click on the share TM was copying to (named "Open Share"), I get the error message:
    "The operation can’t be completed because the original item for “OpenShare” can’t be found"
    I can access the other shares and if I use an ftp-application I can access all shares normal.
    Please help!
    I am on 10.6.4
     
  2. FourCandles macrumors 6502a

    Joined:
    Feb 10, 2009
    Location:
    England
    #2
    I've had similar problems on a QNAP NAS following a power cut.

    I found that manually deleting the .DS_Store files and (and possibly some other hidden Apple network files that are created because of the AFP network protocol) in the shared directory would solve the problem. They were likely corrupted because of the power outage.

    Because I couldn't access the NAS via the Finder, I had to use the QNAP web-browser based utility to browse the directory and show the .DS_Store files and delete them. Hopefully your LaCie has a similar utility.

    HOWEVER: I was using this as a regular network share for my Macs and not for Time Machine. I am not certain if Time Machine plants any other network fork files on a shared drive and therefore what happens if they are affected, so I'd strongly recommend you check that out before proceeding. But hopefully this will be useful.
     
  3. olee thread starter macrumors newbie

    Joined:
    Nov 24, 2010
    #3
    Thanks a lot!

    Thank you very much for your guidance. What I had to do was to delete the following hidden files:
    .AppleDB
    .AppleDesktop
    .AppleDouble

    Thank you very much!
     
  4. FourCandles macrumors 6502a

    Joined:
    Feb 10, 2009
    Location:
    England
    #4
    No problem. I remember that this issue really frustrated me before I found the solution, so glad to have helped.

    FWIW I understand you can use system utilities like Onyx to prevent OS X from dropping those files on to network volumes. Not tried it myself, and obviously you'd initially have to delete the ones that are already there again, but may be useful if you have frequent power outages.
     
  5. AndyfromTucson macrumors member

    Joined:
    Jan 10, 2010
    #5
    I occasionally get a similar error on my MacBook when trying to save files to my Ubuntu home file server (which uses Samba). What works for me is to disconnect the Ubuntu file server, then Force Quit (i.e. Relaunch) Finder, then connect to the file server again.
     

Share This Page