HT1198 Time Machine backup of mounted volume

If I use the latter solution, and make and mount a disk image, where I store my pictures, how can I get Time Machine to backup this data? Do I have to backup the whole image file, or can I setup Time Machine to backup data from the mounted volume?

One for the Time Machine forum for 10.6 or whatever version of the OS you have.
Regards
TD

Similar Messages

  • External hard drive time machine backups not mounting

    I have used Seagate 500.11 external hard drive as a backup location for the time machine for over two years. I just got a message that it had not updated in over thirty days.  It is not listed on FInder, but it is listed on the disc utility.  The Time machine backups  are grayed out on the disc utility screen and cannot be mounted, even after the repair and verification tests said that their volumes were ok.  What should I do?

    Time Machine does not create bootable clones. It does not even create a bootable backup. If that's what you prefer then do not use Time Machine.
    If you use Time Machine then you must allocate at least twice as much space for the backups than the capacity of the drive you are backing up. A 2 TB backup drive would be suitable for a 1 TB main drive or smaller.
    If you plan to create a bootable backup, then partition the backup drive with one partition the size required for the clone. Then use the other partition for you additional storage neeeds.

  • Time Machine backup fails because "volume could not be found".

    I just had my logic board replaced in my Macbook Pro and went to do a backup (yeah, I didn't do this right before it crashed) and now Time Machine backup fails with the message "volume could not be found"  Under Time Machine/Choose Disk, it appears that the drive is the one selected.  The computer "sees" the drive and I can read files on it.  The only other thing that has happened in the meantime is that a friend helped pull a file off the hard drive that I needed for a project.  No apparent issues there.  Any suggestions?

    You might try going to /Library/Preferences, then drag the file com.apple.TimeMachine.plist to the Desktop.  Reboot your Mac, then try declaring the backup disk for Time Machine.  It might help if you mount the backup disk first.
    Are you using Time Machine to write its backups to the disk of a Time Capsule?  If not, since this discussion section is for Apple's Time Capsule AirPort base station, a discussion involving Time Machine should be held on the discussion section for whatever version of OSX that you're using.

  • Time machine backups to remote volumes

    Hi all,
    Been having trouble with backing up a Lion system onto a remote (network) volume.  The idea is basically to back up a (client) Mac onto a disk hosted by another Mac (the backup server).
    I can get the initial backup to work:
    1. share the disk to back up to on the backup server via File Sharing, and ensure to use an administrator account at the client Mac to log onto in order for it to see the backup disk.
    2. mount the backup disk over the network onto the client Mac.
    3. get Time Machine to select that network disk as a backup disk.
    4. start the backup.
    All this works, and I am left with a good initial backup.  However, subsequent backups fail with the following message after the client Mac is next rebooted:
    The syslog shows some rather perculiar difficulty in managing its backup disks:
    15/12/11 11:44:31.309 PM com.apple.backupd: Starting standard backup
    15/12/11 11:44:31.436 PM com.apple.backupd: Attempting to mount network destination URL: afp://Tony%20Kavadias@L%C3%B3rien._afpovertcp._tcp.local/Rivendell
    15/12/11 11:44:31.792 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Rivendell-1 using URL: afp://Tony%20Kavadias@L%C3%B3rien._afpovertcp._tcp.local/Rivendell
    15/12/11 11:45:10.045 PM com.apple.backupd: Failed to eject volume /Volumes/Rivendell-1 (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)
    15/12/11 11:45:10.046 PM com.apple.backupd: Waiting 60 seconds and trying again.
    15/12/11 11:46:10.108 PM com.apple.backupd: Network destination already mounted at: /Volumes/Rivendell-1
    15/12/11 11:46:46.912 PM com.apple.backupd: Failed to eject volume /Volumes/Rivendell-1 (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)
    15/12/11 11:46:46.913 PM com.apple.backupd: Waiting 60 seconds and trying again.
    15/12/11 11:47:46.967 PM com.apple.backupd: Network destination already mounted at: /Volumes/Rivendell-1
    15/12/11 11:48:23.618 PM com.apple.backupd: Failed to eject volume /Volumes/Rivendell-1 (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)
    15/12/11 11:48:23.618 PM com.apple.backupd: Giving up after 3 retries.
    15/12/11 11:48:33.630 PM com.apple.backupd: Backup failed with error: 21
    More digging around leads to the observation that /Volumes/Rivendell-1 (the filesystem that Time Machine mounts from the backup server) is now stuck and cannot be unmounted—to get rid of it, I have to reboot the client Mac.  And that the sparse disk image file Annuminas.sparsebundle is mounted read-only when Time Machine attempts to mount it for writing subsequent backups to!
    The only way I can recover is to erase the backup and start another initial one, but that defeats the purpose of having a continuously running Time Machine backup.
    The client Mac is running Mac OS X 10.7.2 Lion, while the backup server is running Mac OS X 10.6.8 Snow Leopard.  The latter is really just using AFP services to export a disk to the network, whereas Lion is using Time Machine to make backups on the network disk.
    Any help or ideas would be greatly appreciated.  Many thanks,
    —tonza

    Oh... discovered something odd... the Time Machine Backups volume (that is the volume that is mounted from the Annuminas.sparseimage file on the fileserver) is being mounted read-only!
    /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local, nobrowse)
    map -hosts on /net (autofs, nosuid, automounted, nobrowse)
    map auto_home on /home (autofs, automounted, nobrowse)
    afp_000000004oMw0oYHtK1bbUQr-1.2d000004 on /Volumes/Rivendell (afpfs, nobrowse)
    /dev/disk1s2 on /Volumes/Time Machine Backups (hfs, local, nodev, nosuid, read-only)
    How is Time Machine going to write to a read-only volume?!  This is not making any sense!
    If there is one thing I do know about the BSD kernel is that filesystems are mounted read-only if it has been detected by the filesystem driver that a volume is marked dirty or corrupt.  Another thing I'll do is check via Disk Utility that Time Machine Backups needs to be fixed.  If Time Machine is indeed making faulty sparse images, it may be due to Snow Leopard's AFP server after all.
    —tonza

  • Unable to configure Time Machine backups to shared volume on network

    I've been unable to coax Time Machine (TM) into using a networked shared volume that SuperDuper! accesses without a hitch.
    My wife and I have laptops (TiBook and MacBook Pro, respectively), and we have a G4 Mac Mini with an external 300 GB HD. The Mini is connected to a wired Ethernet port on a GigE Airport base station (I've long ago given up on connecting that HD to the Airport). Our laptops connect wirelessly. All three machines are now running 10.5, and I've checked that the Mini is sharing the external HD via System Preferences. My wife and I both have accounts on the Mini, and those accounts provide read/write access on the external HD. Mounting that volume from our laptops works perfectly, as does backing up to it using SuperDuper! TM, however, doesn't recognize that volume as a backup location.
    Any ideas?
    Thanks,
    Andreas

    Adapting the instruction in this post worked for us. I connected to the Mini via ssh and entered the commands to enable the external HD. It then showed up as a TM backup location on both of our computers, and the progress meters for the initial backup are ticking away.
    Cheers,
    Andreas

  • Time machine Backup not mounting

    Since upgrading the back up disc which is an external firewire disc no longer shows up on the desktop or to time machine, I can see it in Disk utility, the drive is recognised but the backup isn't mounted and I can't force it to mount either I've run verify and repair discs but both report it as OK, when I try to mount it in disc utility I'm told to run first aid which I have to no avail.
    It won't work with USB or different leads, any bright ideas out there?
    Apple support are coming back to me monday

    My external drive backup for Time Machine dropped out too. It was ok when I first installed Snow Leopard, but when I tried to open Microsoft Office 2004 a few hours later, I had all kinds of freezing problems (with Skype, Word and inDesign, everything) which had never happened before. No amount of pulling out the external drive plugs and restarting made any difference. (You can see what a tech boffin I am.) The drive was dead and would not show up on my desktop. (I was also worried I might have lost all my back up data).
    I later found out that Office 2004 is not Intel based software. So I updated with 2008 Office, pulled and replugged the ex drive and restarted and it worked. And all my data is there and everything is operating as normal. So for me, Office 2004 seemed to be the culprit. Hope this helps someone.

  • Time Machine Backup of mounted disk

    Hi,
    For sharing my iPhoto Library among multiple users on a MacBook Pro running, currently 10.6.8, I have by a Apple Support guide created a disk image file, and mounted it for storing my pictures without permission issues.
    However, to account for future expansion, the disk image is made to be 100 GB, while current photo library size is approx 50 GB. Is there any way of getting Time Machine to backup the files within the mounted disk, rather than backing up the disk image file itself? So that the size of the backup at present would be the actual size of contents of the disk, rather than the whole disk image file itself? And furthermore, by copying a disk image file, will the actual files within also be backuped?
    Hoping this makes sense to some you you, thanks!

    Create a sparse bundle disk image and copy your library there. A sparse bundle disk image consists of strips, rather than one single file. The bundle will expand to fit your needs by adding strips. If things change in the bundle, TimeMachine should be smart enough to only backup the changed strips, not the entire image. So if you tell Disk Utility to create an empty sparse bundle disk image of  1000GB and you put in only 50 GB, the bundle will only occupy 50 GB.
    When you delete loads of data, you can even shrink back the disk image (through a terminal command) to free up real disk space.
    Message was edited by: eljonco, added shrinking info

  • Time machine backup from two volumes

    I  have an SSD boot drive and a HHD home drive on my Mac Pro. Both drives are included in TM backup.  Question, If I restore to a new HDD from the backup, does it restore a combined drive, or restore to two partitions, or two volumes?

    If you're talking about restoring from a snapshot in Recovery mode, that would only restore the startup volume.

  • Help Incomplete Time Machine Backup and I can't set ownership options

    Two days ago my iMac HD stopped working and I decided it was time to upgrade my machine so I purchased a new iMac with Mavericks installed. I seem to only have a partial Time Machine Backup located on my NAS drive, so I read various threads about how to manually retrieve files from the .inprogress file. I was able to browse the package contents and when I navigated to Macintosh HD the folder was greyed out and when I attempt to open the folder it looks empty. When I select get info the Macintosh HD folder shows almost 80GB and over 160,000 files inside. I tried copying the folder onto the desktop which failed and also onto an external drive formatted the same way as the NAS - Mac OS Extended (Journaled, Case Sensitive). Everytime I try it says something along the lines of me not having the ownership rights to copy the file over.
    I tried going to the NAS drive and the mounted sparsefile and couldn't figure out how to get the ignore ownership on this volume option. When I go to Disk Utility it says Owners Enabled Yes, I can't figure out how to turn that off to let me copy the file over. I tried some recommendations about creating an Alias to Macintosh HD and also setting up Automator actions Get Selected Finder Items > Get Folder Contents > Open Finder Items > Copy Finder Items (to desktop or external drive) both of these failed.
    I also don't understand why I can't view the files inside the greyed out Macintosh HD as get info shows many files inside. The sharing and permissions already says everyone can read. Is there anyway I can recover some of the files? It would be so great!
    Thanks for helping me.

    I solved the problem and I hope this solution can help others with incomplete Time Machine Backups.
    1. I made sure hidden files were shown by pasting the following line into Terminal:
    defaults write com.apple.finder AppleShowAllFiles -boolean true ; killall Finder
    2. On NAS drive I have a folder called Time Machine Backup and inside that folder it lists the different users with Time Machine Backups. I double clicked the user with the incomplete time machine backup to mount it.
    3. Once mounted there should be a folder called backups.backupdb > machine name > dateandtime.inprogress. I right click that .inprogress file and selected show package contents. This lead to another folder randomly named with numbers and text. Inside that folder you should see a greyed out Macintosh HD folder. The date of the greyed out Macintosh HD folder might read something like January 24th, 1984. This appears to be the date that the Macintosh 128k was first introduced. I read on another thread that the creation date of the folder is incorrectly set after a crash resulting in the greyed out folder.
    4. Due to the NAS having ownership issues I was not able to drag either the greyed out Macintosh HD or the folder above it to an external drive or the desktop of my new computer. Automator didn't work either. Here is what did work: I trashed the folder with the greyed out Macintosh HD inside from the NAS and dragged it from the trash onto my desktop. The move took a few hours to complete and the files were now all successfully on the new computer.
    5. Once on the desktop the Macintosh HD folder was still greyed out. The solution was to select in the finder: View > Show Path Bar, then search for any file you remember inside your backup. For example I searched the word download and files inside the greyed out Macintosh HD folder showed up. Left clicking the file confirmed the path, that it was from the greyed out Macintosh HD folder. Now you can simply right click one of the folders in the Path Bar and open in new tab if you have Mavericks. I still couldn't directly open the Macintosh HD folder in a new tab, but I could open any of the subfolders inside in a new tab, including the users which lets you access all the backup files. I tested in Mountain Lion that you can also choose Open in Enclosing Folder by right clicking the file that you searched for or right clicking the folder in the bottom of the Path Bar.
    6. Once I was done organizing backup files, I turned off hidden files by pasting this line into Terminal:
    defaults write com.apple.finder AppleShowAllFiles -boolean false ; killall Finder
    This took me days to figure out how to make use of an .inprogress file and greyed out Macintosh HD folder.
    Hope this helps!!!

  • Time Machine Backup after clean install?

    Hi,
    I just took the plunge and made a clean install of Mavericks on an SSD called "A". On this volume I only have the system and the applications. My User Account is on a separate volume "B" and my third volume is a 4TB volume "C" with my Time Machine backup. My volume "B" is backuped on the  TM volume "C".
    In the past I have had very nasty experiences with Time Machine, where a whole backup was deleted because Time Machine thought I was on a completely new computer. Now I don't want to repeat this experience, because when opened after the system install, TM didn't recognize neither volume "B" nor "C".
    Any ideas of how to make sure TM doesn't delete the old stuff? I don't want to try around and eventually lose everything.
    Thanks!

    Inherit a Backup
    Inherit a Backup (2)

  • Time Machine backup volume will not mount

    Once I goy Time Machine up and running over almost two years ago, I have had little cause for concern. A few lengthy backups here and there but I have been able to restore without any problems whatsoever. It has been extremely useful many times.
    A couple of days ago, I noticed that the backup volume was not mounted (I backup to one of my four internal drives) and launched Time Machine. I got the error:
    The storage location for Time Machine backups can't be found.
    When I run Disk Utility the generic disk icon is in the left hand pane but not the volume. None of the tasks are available except Erase and Partition - there is no option to Verify Disk, Repair Disk, Verify Disk Permissions or Repair Disk Permissions.
    According to my logs, the last backup at 18:12 on 20th November was successful. I didn't notice that the volume had not mounted the until the next day.
    I'm very concerned that I have lost almost two years of data security. Is there any way I can repair the disk or recover the backups?
    Thanks.

    If Disk Utility can't see any partitions, it's not good.
    First, turn TM off.
    Then try ejecting, disconnecting and powering the drive off for a few minutes, then reattaching it. Then try again with Disk Utility. If still no help, the drive is likely dead.
    There's a very small chance that +Disk Warrior+ (version 4.1.1 or 4.2 only), or another heavy-duty disk repair app can fix it, if you already have one. But I wouldn't suggest spending the $$ for one unless you think you'll need it in the future -- DW is about $100.
    Most likely, your disk is dead. There's a small chance that a +Data Recovery+ app such as +Data Rescue+ can recover some of the data. Check via Google, VersionTracker.com, or MacUpdate.com for +Data Recovery.+ There are services and apps, none cheap. Some of the apps have a free demo or test mode that will tell you if there's anything that can be recovered, and perhaps actually recover a single file; then you pay for it and recover whatever else can be recovered. You'll need another external disk to receive the recovered items.
    You won't get the normal Time Machine folder structure, though, just "raw" files. Even if you do recover files, you'll most likely have to figure out what goes where and copy them to the right places manually.
    So I'd suggest immediately getting a new drive and doing a new TM backup to it, so you have something. Put a second partition on it that you can use for the recovered files if and when you do that.
    If those are your only backups, I'd recommend getting a second external, perhaps a portable one, and using CarbonCopyCloner or SuperDuper to make a full "bootable clone" to it, then take it to your safe deposit box, workplace, relative's house, or other secure location. And/or, you might want to look at Mozy, Carbonite, or other online backup services.

  • Time Machine failing to mount backup volume

    Hi
    I set up a network shared drive (afp) and successfully used it for Time Machine backup from one of my Macs.
    However, from my other Mac, when I turn on TM and choose the network drive, nothing happens -- in the TM preference pane the disk doesn't get selected and the message remains "Choose Backup Disk...". In the console I get the following:
    20/5/08 4:39:13 PM System Preferences[185] FSMountServerVolumeSync received error: -36
    20/5/08 4:39:13 PM System Preferences[185] Failed to mount url: afp://;AUTH=No%20User%[email protected]/500GB%20Network%20Storage
    Any ideas?
    Thanks!

    Here's the solution:
    During the backup attempt Time Machine creates the bundle image on the share. This is called <computer’s name>_<string>.sparsebundle (by the way, string is the MAC address of the local en0 device without colons). You should keep the exact name in mind (e.g. by copy & paste or by looking in Console or by constructing it yourself from computer’s name and MAC address).
    Afterwards you start Disk Utility and create another “sparse bundle disk image” on your local drive. Volume Size should be the designated maximum size of the Time Machine backup (don’t be afraid, only by using the image it will increase in size). Further parameters: Volume Format - Mac OS Extended (Journaled); Partitions - No partition map.
    After this use the exact name Time Machine assigned to its bundle image to rename your newly created image (if not already done while creating your own image). Finally you copy the image on the share and manually start a backup via menu bar.
    Voilà. Afterwards Time Machine should start the tedious initial backup.
    from http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/

  • "No such file or directory" errors on Time Machine backup volume

    I remotely mounted the Time Machine backup volume onto another Mac and was looking around it in a Terminal window and discovered what appeared to be a funny problem. If I "cd" into some folders (but not all) and do a "ls -la" command, I get a lot of "No such file or directory" errors for all the subfolders, but all the files look fine. Yet if I go log onto the Mac that has the backup volume mounted as a local volume, these errors never appear for the exact same location. Even more weird is that if I do "ls -a" everything appears normal on both systems (no error messages anyway).
    It appears to be the case that the folders that have the problem are folders that Time Machine has created as "hard links" to other folders which is something that Time Machine does and is only available as of Mac OS X 10.5 and is the secret behind how it avoids using up disk space for files that are the same in the different backups.
    I moved the Time Machine disk to the second Mac and mounted the volume locally onto it (the second Mac that was showing the problems), so that now the volume is local to it instead of a remote mounted volume via AFP and the problem goes away, and if I do a remote mount on the first Mac of the Time Machine volume the problem appears on the first Mac system that was OK - so basically by switching the volume the problem switches also on who shows the "no such file or directory" errors.
    Because of the way the problem occurs, ie only when the volume is remote mounted, it would appear to be an issue with AFP mounted volumes that contain these "hard links" to folders.
    There is utility program written by Amit Singh, the fella who wrote the "Mac OS X Internals" book, called hfsdebug (you can get it from his website if you want - just do a web search for "Mac OS X Internals hfsdebug" if you want to find it ). If you use it to get a little bit more info on what's going on, it shows a lot of details about one of the problematic folders. Here is what things look like on the first Mac (mac1) with the Time Machine locally mounted:
    mac1:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac1:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac1:xxx me$ ls -lai
    total 48
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 .
    282780 drwxr-xr-x 12 me staff 442 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 Documents
    729750 drwx------ 104 me staff 7378 Jan 15 14:17 D2
    728506 drwx------ 19 me staff 850 Jan 14 09:19 D3
    mac1:xxx me$ hfsdebug Documents/ | head
    <Catalog B-Tree node = 12589 (sector 0x18837)>
    path = MyBackups:/yyy/xxx/Documents
    # Catalog File Record
    type = file (alias, directory hard link)
    indirect folder = MyBackups:/.HFS+ Private Directory Data%000d/dir_135
    file ID = 728505
    flags = 0000000000100010
    . File has a thread record in the catalog.
    . File has hardlink chain.
    reserved1 = 0 (first link ID)
    mac1:xxx me$ cd Documents
    mac1:xxx me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac1:Documents me$ ls -lai | head
    total 17720
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 .
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    146 drwxr-xr-x 2 me staff 68 Feb 17 2009 .parallels-vm-directory
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    148 drwxr-xr-x 2 me staff 136 Aug 28 2009 ACPI
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    So you can see from the first few lines of the "ls -a" command, it shows some file/folders but you can't tell which yet. The next "ls -la" command shows which names are files and folders - that there are some folders (like ACPI) and some files (like A.txt and A9.txt) and all looks normal. And the "hfsdebug" info shows some details of what is really happening in the "Documents" folder, but more about that in a bit.
    And here are what a "ls -a" and "ls -al" look like for the same locations on the second Mac (mac2) where the Time Machine volume is remote mounted:
    mac2:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac2:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac2:xxx me$ ls -lai
    total 56
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 .
    282780 drwxr-xr-x 13 me staff 398 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 Documents
    729750 drwx------ 217 me staff 7334 Jan 15 14:17 D2
    728506 drwx------ 25 me staff 806 Jan 14 09:19 D3
    mac2:xxx me$ cd Documents
    mac2:Documents me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac2:Documents me$ ls -lai | head
    ls: .parallels-vm-directory: No such file or directory
    ls: ACPI: No such file or directory
    ... many more "ls: ddd: No such file or directory" error messages appear - there is a one-to-one
    correspondence between the "ddd" folders and the "no such file or directory" error messages
    total 17912
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 .
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    If you look very close a hint as to what is going on is obvious - the inode for the Documents folder is 152 on the local mounted case (the first set of code above for mac1), and it's 728505 in the remote mounted case for mac2. So it appears that these "hard links" to folders have an extra level of folder that is hidden from you and that AFP fails to take into account, and that is what the "hfsdebug" shows even better as you can clearly see the REAL location of the Documents folder is in something called "/.HFS+ Private Directory Data%000d/dir_135" that is not even visible to the shell. And if you look closely in the remote mac2 case, when I did the "cd Documents" I don't go into the inode 135, but into the inode 728505 (look close at the "." entry for the "ls -la" commands on both mac1 and mac2) which is the REAL problem, but have no idea how to get AFP to follow the extra level of indirection.
    Anyone have any ideas how to fix this so that "ls -l" commands don't generate these "no such file or folder" messages?
    I am guessing that the issue is really something to do with AFP (Apple File Protocol) mounted remote volumes. The TimeMachine example is something that I used as an example that anyone could verify the problem. The real problem for me has nothing to do with Time Machine, but has to do with some hard links to folders that I created on another file system totally separate from the Time Machine volume. They exhibit the same problem as these Time Machine created folders, so am pretty sure the problem has nothing to do with how I created hard links to folders which is not doable normally without writing a super simple little 10 line program using the link() system call - do a "man 2 link" if you are curious how it works.
    I'm well aware of the issues and the conditions when they can and can't be used and the potential hazards. I have an issue in which they are the best way to solve a problem. And after the problem was solved, is when I noticed this issue that appears to be a by-product of using them.
    Do not try these hard links to folders on your own without knowing what they're for and how to use them and not use them. They can cause real problems if not used correctly. So if you decide to try them out and you loose some files or your entire drive, don't say I didn't warn you first.
    Thanks ...
    -Bob

    The problem is Mac to Mac - the volume that I'm having the issue with is not related in any way to Time Machine or to TimeCapsule. The reference to TIme Machine is just to illustrate the problem exists outside of my own personal work with hard links to folders on HFS Extended volumes (case-sensitive in this particular case in case that matters).
    I'm not too excited about the idea of snooping AFP protocol to discover anything that might be learned there.
    The most significant clue that I've seen so far has to do with the inode numbers for the two folders shown in the Terminal window snippets in the original post. The local mounted case uses the inode=728505 of the problematic folder which is in turn linked to the hidden original inode of 135 via the super-secret /.HFS+... folder that you can't see unless using something like the "hfsdebug" program I mentioned.
    The remote mounted case uses the inode=728505 but does not make the additional jump to the inode=135 which is where lower level folders appear to be physically stored.
    Hence the behavior that is seen - the local mounted case is happy and shows what would be expected and the remote mounted case shows only files contained in the problem folder but not lower-level folders or their contents.
    From my little knowledge of how these inode entries really work, I think that they are some sort of linked list chain of values, so that you have to follow the entire chain to get at what you're looking for. If the chain is broken somewhere along the line or not followed correctly, things like this can happen. I think this is a case of things not being followed correctly, as if it were a broken chain problem then the local mounted case would have problems also.
    But the information for this link in the chain is there (from 728505 to the magic-135) but for some reason AFP doesn't make this extra jump.
    Yesterday I heard back from Apple tech support and they have confirmed this problem and say that it is a "implementation limitation" with the AFP client. I think it's a bug, but that will have to be up to Apple to decide now that it's been reported. I just finished reporting this as a bug via the Apple Bug Reporter web site -- it's bug id 8926401 if you want to keep track it.
    Thanks for the insights...
    -Bob

  • External HDD (for Time Machine backup) detected but won't mount on desktop

    I have been using this external HDD as my Time Machine backup for many months now. No desktop display settings have been changed (I checked), but now it won't mount on my desktop. I suspect one of my kids was banging around on the keyboard, as they have done in the past, and renamed it. Unfortunately it appears they renamed it to NULL this time around. I didn't think that was possible, but I've plugged it into 3 different Windows and iMac machines, and in all cases the external drive gets detected, but then in all cases it doesn't mount. The Volume Label does appear blank in the device properties.
    Is there a way to access my drive again to rename it? Will that allow it to mount again? Or is there a way to access it to just reformat the whole darn thing?
    Thanks!
    Tom

    I don't think it's possible to have a null name for a drive so i suspect there is a problem with it. open disk utility. does it show the name of the drive? try repairing it (repair disk not permissions). if that doesn't help you can always reformat it with Disk Utility. select the whole drive ( model, not name) and use the partition tab.

  • Unable to restore from Time Machine after an erase and reinstall - MacbookPro cannot access my old Time Machine backup volume. Desperate for help please?

    My MacbookPro would not move past the Apple logo and spinning wheel for a number of hours.  After trying the numerous suggestions to solve the issue I eventually opted to erase and reinstall feeling confident my Time Machine backups would come to the rescue.  After a successful erase and reinstall I tried to restore all my data from my TIme Capsule using Command-R during start up and by using the Migration Assistant.  Neither worked and I have received messages to the effect that the backup volumes on my Time Capsule cannot be access because I have entered a wrong password or because the backup volume is damaged.
    When I open my Time Capsule in Finder and click on my sparsebundle I get an eror message saying that the disk image could not be opened and that the resource is temporarily unavailable.
    Desperate for some help and comfort that many years of personal data have not been lost.
    Thank you.
    M

    When I try to Verify option it says Unable to Verify - Resource temporarily unavailable.
    Here is the past of the log screen:
    2013-06-09 15:00:00 -0500: Disk Utility started.
    2013-06-09 15:09:01 -0500: Disk Utility started.
    2013-06-09 15:19:53 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:19:53 -0500:
    2013-06-09 15:20:00 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:20:00 -0500:
    2013-06-09 15:20:05 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:20:05 -0500:
    2013-06-09 15:20:13 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 15:20:14 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:20:14 -0500:
    2013-06-09 15:25:21 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 15:25:23 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:25:23 -0500:
    2013-06-09 15:25:27 -0500: Attach Image “Macajee’s MacBook Pro”
    2013-06-09 15:25:27 -0500: Initializing…
    2013-06-09 15:25:31 -0500: Attaching…
    2013-06-09 15:25:31 -0500: Finishing…
    2013-06-09 15:25:32 -0500: Unable to attach “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:25:32 -0500:
    2013-06-09 20:02:06 -0500: Disk Utility started.
    2013-06-09 20:05:22 -0500: Disk Utility started.
    2013-06-09 20:07:11 -0500: Disk Utility started.
    2013-06-09 20:18:34 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:18:34 -0500:
    2013-06-09 20:19:34 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:19:34 -0500:
    2013-06-09 20:19:36 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:19:36 -0500:
    2013-06-09 20:22:29 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:22:29 -0500:
    2013-06-09 20:22:33 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:22:33 -0500:
    2013-06-09 20:22:45 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 20:22:45 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 20:22:45 -0500:
    2013-06-09 20:34:53 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:34:53 -0500:
    2013-06-09 20:34:56 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:34:56 -0500:
    2013-06-09 20:38:17 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 20:38:17 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 20:38:17 -0500:
    2013-06-09 20:47:35 -0500: Disk Utility started.
    2013-06-09 20:53:06 -0500: Disk Utility started.
    2013-06-09 20:55:30 -0500: Disk Utility started.
    2013-06-09 20:56:40 -0500: Disk Utility started.
    2013-06-09 21:06:32 -0500: Verifying Image “macajee’s MacBook Pro”
    2013-06-09 21:06:32 -0500: Unable to verify “macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 21:06:32 -0500:
    2013-06-09 21:07:08 -0500: Verifying Image “macajee’s MacBook Pro”
    2013-06-09 21:07:08 -0500: Unable to verify “macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 21:07:08 -0500:

Maybe you are looking for