Benches macOS

15

The operation cannot be completed because the original item for "Backup"...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

... cannot be found... now what is this?

I am now unable to access my USB HDs attached to my Airport Extreme... I see my drive in Finder... however, when I click on the drive I get a promtp saying "The operation cannot be cmopleted because the original item for "Backup" (the name of my drive) cannot be found".... can anyone help me??

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    stevebow

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I get this message trying to connect to one of my shares via Samba on my Vista PC, but connecting to the "Public" directory works ok though.

    Any ideas about this error message anyone?

  2. 0

    stevebow

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I can confirm both my Vista shares can be accessed fine using 10.4.11 so it appears to be a problem with 10.5.x. :^(

  3. 0

    kubmg2

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I to am getting the exact same error. It worked until I unplugged and plugged the USB drive back into my extreme.

  4. 0

    Disstroy

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm really annoyed. The 'easy' Mac solution isn't quite as carefree as their advertising would suggest. Especially given that I forked out a premium price over other modems for the AEBS. I am getting the same "Original Item" error. My old Macbook running Tiger does not have this issue so I'm quite certain the issue is unique to Leopard.

    Dear Apple: FIX THIS. NOW.

  5. 0

    yobaby

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm having exactly the same problem.

  6. 0

    Ednel

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'd be happy if anyone solved this. I cannot connect either to my Time Capsule or to a server (e.g. my MacBook Air on my AirPort network)--I can see my Time Capsule disk, or the directories on my MBA, in the finder, but when I click on them I get this same "this operation cannot be completed because the original Item
    ____ cannot be found" error message.

    BUT, when I log in as the root user, I can connect to both. What's up with that? I've spent 1 1/2 hours on the phone with Apple, archived and reinstalled my system, installed the latest update from downloads and not Software Update, and ran disk and permission utilities on everything (yes, including TechTool). Still no dice. I've even tried fixing the problem through Terminal using some of the suggested "fsck_hfs" solutions and have gotten nowhere.

    As I've searched for solutions, it's pretty apparent that people are having this problem everywhere (I was even overhearing another when shopping in Frye's yesterday). It doesn't take a genius to know that this is not just something that needs to be fixed but is damaging Apple's credibility. I've been an Apple/Mac user for 20+ years now because I wanted to do things with my computer, not DO MY COMPUTER for hours on end.

  7. 0

    Glenn Carter

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ednel,

    Try the following:

    *Proper Computer Name*

    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the TM process over again and do another full initial backup to the TC (Best done connected via ethernet).

    NOTE: If you are not experiencing issues with TM backups, DO NOT change your computers' name as TM will stop working for you. Also, changing a computers' name may cause print jobs sent from this computer over the network to vanish according to THIS KB article. (
    http://docs.info.apple.com/article.html?artnum=107331)

    According to THIS article (
    http://support.apple.com/kb/TS1760), Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.

    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)

    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.

    One poster observed, “After about three days of playing with the sparsebundle and time machine, I finally got it to work. The key for me was changing the computer name in the System Preferences - Sharing to a name that did not include spaces, symbols, etc. (just numbers and letters) and keeping the name of under 8 characters. Before this, I kept getting an "The backup disk image could not be mounted" error.”

    *Time Capsule Has a Long Name*

    “When using your Time Capsule for Time Machine backups in Mac OS X 10.5 Leopard or later, the Time Capsule backup volume may not mount and Time Machine may not be able to back up to it. This alert may appear: "Backup volume cannot be found"

    This can happen if the Time Capsule disk has a long name. (
    http://support.apple.com/kb/HT1170)

    Rename the backup volume via AirPort Utility:

    Open AirPort Utility (in /Applications/Utilities).

    Click your Time Capsule's icon.

    Click "Manual Setup".

    Enter the password for the Time Capsule if prompted.

    Click the Disks icon.

    Highlight the volume name that appears under "Time Capsule Disk".

    In the Name field, enter a name for the volume that is less than 27 characters long.

    Click Update.

    After Time Capsule restarts, on the Mac(s)using Time Machine, open Time Machine preferences and reselect the Time Capsule volume.”

    Let us know if any of these suggestions help.

  8. 0

    Ednel

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Glenn,

    Unfortunately, nothing works. The TC has a short name, my computer has a proper name. I changed the names anyway, did use TC to click on the renamed disk, which then suddenly turned off the switch in TC preferences. Now I can't back access TC at all or back up again until I go back in as a root user, and then -- voila -- TC works again.

  9. 0

    Ednel

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    To be clear, I can "see" servers (my Time Capsule, my MacBook Air on my network) in the finder and connect to them initially (e.g., I connect to my MBA and see my directories such as "Documents"). But if I try to connect to any of these directories (the Time Capsule disk, the "Documents" files on my MBA) I get the dreaded "The operation cannot be completed because the original item [TCDisk, Documents] cannot be found."

    Nor, interestingly, does the "eject" button appear on the finder window. I assume this means that there is some mounting problem.

    I have tried creating other accounts to see if it's just my account, and the same thing happens. BUT, when I log is as the root user, I can access my TCDisk and the MBA, and the "eject" icon appears.

    I really, really, REALLY need to get this fixed. I can't keep logging in as the Root to get my work done.

  10. 0

    Hank Schultz

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I thought you might appreciate a solution to this issue. I ran into the same issue after my hard drive died. I tried a restore from time machine, but my backup was borked, so I haven't yet gotten much off of it. I did an OS install over top of what I did manage to recover (which appeared to only be applications), and I updated to 10.5.5. Unfortunately, I was not able to mount
    any network volumes, regardless of the server.

    You noted that it worked if you logged in as root, so I checked my own machine, and that
    did work. I tried repairing permissions, and it spat out all kinds of warnings about ACLs where they weren't expected, and most claims say that this is harmless. That wasn't true in this case, as there was an ACL set on /Volumes and another one on /Network/Servers, though the first one is likely to be the problem.

    While logged in as root, I unmounted all of my disks (except the boot drive, obviously), deleted the /Volumes folder, recreated it, and reran the repair permissions--to make sure that the permissions were correct. After a reboot, everything works again.

    Additionally, for all of the files DiskUtility said had ACLs, I used "chmod -N" to get rid of them.

  11. 0

    Hank Schultz

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I should probably emphasize the danger in deleting the "Volumes" folder. If you delete it at the command line and you haven't unmounted your drives, every file and folder on those drives will be deleted before the /Volumes folder is deleted. It is CRITICAL that you unmount everything that shows up in that folder.

    Just to be safe, all I did was throw the folder in the Trash, since that won't actually delete anything until you empty the trash. 🙂

  12. 0

    Ednel

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This is probably something that I should know, but how do I delete or trash the /Volumes folder if the Boot drive (Mac HD) alias is in the folder? Also, when you say "rebuild" the folder, what do you mean?

    I just want to make sure of what I'm doing before logging in as root and really screwing things up. 🙂 But I really appreciate the direction here--it looks like this, done properly, might actually work.

    Thanks!

  13. 0

    Ednel

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It WORKS! Thanks so much! I was beginning to think I would have to change my name to "root." 🙂

  14. 0

    DuncanR

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This worked for me too. I started having the problem where my machine could not connect to the TC disk. I had upgraded to OSX 10.5.5. My GFs mac was still using 10.5.2 and was not having a problem. I enabled root, logged in as root, recreated the Volumes folder and checked permissions, and then logged back in as me. Everything works fine now.

  15. 0

    Flaviosi

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hank,

    I'm a real rookie and I'm going through this issue. Unfortunately, I could not understand what am I suppose to do to repair it. Could you translate your post into something "idiot's proof"? 🙂

    Thanks in advance!

    Flavio