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.

Similar Messages

I cannot load Maverick on my iMac HD. It reports that my HD is used for Time Machine backups and will not load to that drive. I do not use this drive for backups. Help.

I cannot load Maverick on my iMac HD. It reports that my HD is used for Time Machine backups and will not load to that drive. I do not use this drive for backups. I use an external 1 TB WD My Book for backups as well as Super Duper Backups. Can anyone offer advice. Thanks.

Welcome to Apple Support Communities
You have got the "Backups.backupdb" folder in the root level of your hard drive. This is the folder used by Time Machine to save backups to, and the OS X Mavericks installer thought that your hard drive is being used to store Time Machine backups
To fix this, open a Finder window, select the Go menu (on the menu bar) > Go to Folder, and type:
Then, delete "Backups.backupdb" and empty the Trash. Finally, open the Mavericks installer from the Applications folder and follow the steps

Time Machine: Backup Volume Could not be Found

I recently upgraded to Leopard. I have a brand new Lacie external hard drive.
I have tried to use Time Machine with the Lacie HD, but it fails and gives me this message, "Backup volume could not be found."
I did some troubleshooting. I tried to reformat the HD, but that gave me errors as well, stating "Could not unmount disk"
The HD is currently formatted to Mac OS Extended.
I am not certain if this is a problem with the HD, or just user error! I also had problems with iTunes when I tried to move the Library to the HD. I got and error message stating "you don't have sufficient privileges"
I only have 2.5G left on my internal HD, so I am a bit concerned. Any guidance would be much appreciated!!

when you select the TM hard drive in disk utility (the model, not the name) look at the bottom of the DU window. Do you see the line
Partition Map Scheme : GUID Partition Table?
Also, I looked at your first post again and it says that you only have 2.5GB of space available on your main drive. I don't know how big your hard drive is but that's a tiny amount. You need to offload part of your data to a different drive ASAP. when free space gets that low, disk fragmentation becomes a very serious issue. system slows done and start behaving in unpredictable fashion. This can lead to all sorts of problems including directory damage. Run "verify disk" on your main drive and see if any errors are reported. I don't know for sure if this is related to your TM problems but it very well might be.

My old Time machine backup's will not restore after lion upgrade. Ugh!!!!!

I had old backups that were accessible while running snow lepoard. Aftering installing Lion, the backup are still there, but I can't restore from any of them. Do I have to change the file name? Or am I SOL!!

Hey Linc,
Here's what happens: I log in TM, I can scroll through my old backups, I can choose the folders I want to restore, I can click on the folder, but when the systems tries to restore it, it stops saying that I don't have the privileges to access file A in the folder (and then all the procedure is stopped).
Oddly (at least for me) if I try to restore just that same file A (and not the whole folder) that I should have no privileges for, from the same old backup, I can do it, but I have to give the system my password: It pops up a window saying something "Finder is willing to make some modification, can you authorize?" (forgive i'm translating the alert from another language) and then I can restore it.
Many thanks
Ps: I did a simple upgrade on Lion, no partition, no blank disk, and never changed anything in my user preferences, it's always the same, administrator
Pps: Before Lion I could restore easily exactly the same folders and files I tried to restore with Lion

Due to NAS issues, when I started a new time machine backup it did not have the old backups available. My question is do I need to delete them or will time machine automatically reclaim the space? Only one Sparse Bundle, same name.

Due to NAS issues, when I started a new time machine backup it did not have the old backups available. My question is do I need to delete them or will time machine automatically reclaim the space? There is only one sparse bundle but when I enter time machine I don't see my historic backups. I use a synology DS212 for my time machine. Started a new backup which is 218gb but it says 618 gb is occupied therefore it looks like 2 or 3 backups are still on the disk. Before my NAS issues the last backup was in 2014. As you can see there is a second sparse bundle from 2012. Not sure what that is.

This is an old message now, but what happened to me similarly was:
I had a major computer crash and through complicated pathways ended up reinstalling (Mavericks) as a new user (long story).
At least I had good Time Machine backups on an NAS drive (Synology DS212j), or so I thought - when I started Time Machine up again, the old backup file was gone, replaced by a new one using my "new computer" name. The old file was gone both by directly mounting the NAS drive and by clicking "Enter Time Machine".
It's like I had {OldShareName}.sparsebundle and then it was replaced by {NewShareName}.sparsebundle, all of the old info vanished.
(I have spent a week finding old files elsewhere and have completed a satisfactory self-restore. It pays to "archive" [my own variation of] as well as "back-up".)
My belief is that if this were a wired-netword-drive, e.g. plugged right into my iMac with a USB cable, then the old file would have remained.
But this is an NAS drive, connected directly to my Airport wireless router, and I don't know the significance of the fact that it stores its Time Machine backups as "sparsebundle" files rather than simply as plain(er) files.
As usual when things get complicated with computers (not just Apple computers) there was never a warning message. Something like "YOU'RE ABOUT TO DELETE A TIME MACHINE BACK-UP FILE!!!" would have made my life a lot simpler.
BTW, I did try a "restore from Time Machine" option the first thing I had my "new computer" (old hardware, 2009 iMac) up and running, using Migration Assistant, and it ran for many hours and then failed in the wee hours - what that has to do with anything I'm not sure.
I'm not sure that I have a question about this other than "why do these things happen to me?", but it's a warning. Apart from that I've been very happy with the stability and reliability (but not the cost or set-up complexity) of NAS vs. directly-cabled external drives.
Charles

"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

Migrating content from an encrypted Time Machine external disk (will not easily work)

I recently purchased an SSHD to upgrade my Mac. I preferred not to completely restore from Time Machine, but rather to install a new copy of Mavericks on the new disk and then migrate my TM content afterwards. At the end of installation, Mavericks proposed the option to migrate data from a TM backup, which I chose.
It turns out that the Migration Assistant did not recognize any disk, perhaps because it was encrypted, nor displayed any way to select the volume and unlock it by entering its password. Despite what Pondini says the Time Machine backups disk was not seen by the Mac: as workaround I had to create a fictitious user, log in, unlock the disk (that was immediately recognized by the system) and then run the Migration Assistant from there (by the way, after 4 hours I finally logged into my migrated account and found out that apps were not imported at all!)
I find all this quite not…applish! I could have preferred to unencrypt the TM disk rather than
Is there anyone facing this same experience? Hope that this, if it's a bug, will be fixed, otherwise I'll have to make a TM backup on a secondary disk (which I don't own so big).

Well a google search would appear that disk utility will show you the disk regardless if it's mounted or unmounted. you're best bet would be to unmount the disk in finder, shut down the computer completely, unplug it from a power source, and then unplug the firewire...
I think this is your safest bet but then again, I'm not that worried about ejecting my disks.
you get no error messages when you right click and eject the disk in in disk utilty? you said you have a my disk, do you mean My Book by western digital? I know that they load software onto the machine for encryption purposes. have you tried ejecting the disk from there? I uninstalled said software so I can't tell you if there is an option for that or not.

If I do a clean install on my MacBook Pro will I be able to re-install apps (FCP, Aperture, MS Office etc.) from a Time Machine backup, or will I need the original install DVDs with authorization codes?

I have two questions...
1) If I do a clean install on my MacBook Pro will I be able to re-install apps (FCP, Aperture, MS Office etc.) from a Time Machine backup, or will I need the original install DVDs with authorization codes? (because I don't have them)
2) Has anyone ever seen anything like this before on their computers?
The Apple Genius' were stumped by my laptop issues and said they'd never seen anything like it before and recommended I did a clean install. Below you can see my trash bin, and if you look at the "Empty" button it reads "N201" and then there's the "N39" to the left of it. You can also see these numbers over by the folder area--"SD5, SD6, SD7." But that's not all...
When I right click on items I see the numbers again. Instead of "Open with" I get "N152" and there's an "N35" and "LB1" towards the bottom.
I have no idea what's going on so I'm just going to do a clean install on my machine but I don't want to lose my apps. I don't have the original install DVDs for them anymore. If you have any suggestions please let me know. Thanks!

You don't lose them. You can always redownload them from the app store after you log back in with your Apple ID.
"Buy, download, and even redownload.
You can install apps on every Mac you use and even download them again. This is especially convenient when you buy a new Mac and want to load it with apps you already own."

TS3423 Mac book pro stops responding after Maverick OS restart. Currently have a circle with a line through it after 20+ hours. Tried to shut it down and use the Time Machine to restore but no response. How can I restore with Time Machine if it will not s

Mac book pro stops responding after Maverick OS restart. Currently have a circle with a line through it after 20+ hours. Tried to shut it down and use the Time Machine to restore but no response. How can I restore with Time Machine if it will not start?

sonjadg,
you can purchase a replacement pair of grey installation DVDs for your MacBook Pro from either Apple or iFixit. If Startup Manager is only showing an OS X Installer volume, then it sounds like the Mavericks installer had a problem midway through its installation process. To fix this, you’re going to need to erase your internal disk and reïnstall your original version of OS X from the grey Mac OS X Install DVD, use Software Update to get it back to 10.6.8 (presuming that your MacBook Pro originally came with Snow Leopard), and then restore from Time Machine.

Finder "Open With..." Menus Seeing Time Machine Backup Volumes

The "Open With..." context menu that is available if you right-click a file in the Finder has gone crazy on my Mac. The list is about a mile long and includes literally dozens of versions of each app.
One clue is that a similar "Open Page With..." menu that is available under Safari's Debug menu includes paths, and each redundant version of the applications that appear there are all located in the Time Machine backup volume.
It's hard to imagine that Time Machine doesn't auto-configure this, but my question to the group is if there's a way to make the Finder (and Safari) ignore the Time Machine backup database? Clearly, I would never, ever want to open a file with an app located in the Time Machine database.
Thanks,
Steve

I have excluded my external USB drive where Time Machine backups reside, and I still get a context menu full of backed up applications.
It's not just plain wrong, it makes the context menu very slow.
MacOS must look for this information elsewhere.

Volume will NOT mount

We have much the same issue as others here in other threads have spoken about - after a reboot a raid volume will not mount.
Disk Utility can 'see' the drive and array, but will not mount it. RAID Admin reports no problems. I tried updating the firmware to no avail.
Then I tried a new FC card in the server, a different controller card in the xRAID, different cables and connecting the FC cable to a different XServe. No mount with any of these attempts.
XServe 2 ea 2.3Ghz G5, 2GB RAM, 1 80GB drive (cluster node config)
OSX Server 10.3.9
7 ea 180GB drives, RAID5; 1 TB array
RAID Admin 1.5 (controller firmware - now: 1.5/1.50f)
Any ideas what to try next? And no we don't have 100% backups, close but no... ;-( so any ideas worth trying appreciated!
Tks, Mark

Mark,
We recently had a similar problem. We have an XServe RAID fully populated -- split into 2 volumes. One volume would mount the other would not (after a reboot). Tried swapping fibre channel cables, re-seating fibre channel cards, etc. Our solution was replacing the PCI-Fibre card in the XServe.
Another thing we have had happen is, after reboot, one volume mounts and the other mounts about 15 mins later -- after completing fsck.
Hope this helps.
--Bonnie

I need to restore my music via time machine but it will not as my mac mini says I don't have permission access iTunes. Any help would be great. Thanks

I need to restore my music via time machine but it will not as my mac mini says I don't have permission access iTunes. Any help would be great. Thanks

Have you looked at the previous discussions listed on the right side of this page under the heading "More Like This"?

HT201250 I selected old mail in time machine and it will not open. How can I open it?

I selected old mail in time machine and it will not open. How can I open it?

Have a read here https://discussions.apple.com/message/15701309#15701309
Seems that you have to update Logic to the latest version (9.0.15) to get it to work in Lion.
Stefan

How can I delete a Time Machine backup which did not complete?

I was running a Time Machine backup when the disc got unmounted. Therefore I know all of the data is not backed up.
I would like to delete that entry and rerun "Back Up Now" to start over.
I tried deleting the folder with the latest time stamp on the drive and ran "Back Up Now". There was a very small amount of data that it then backed up.
Obviously there is a large gap in manually managing this process and I would like to know the best fix.
Thanks in advance.

Please triple-click anywhere in the line below on this page to select it:
tmutil compare | open -ef
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
Wait for a new line ending in a dollar sign (“$”) to appear below what you entered.
A TextEdit window will open with the output of the command. Each line that begins with a plus sign (“+”) represents a file that has been added to the source volume since the last snapshot was taken. These files have not been backed up yet.
Each line that begins with an exclamation point (“!”) represents a file that has changed on the source volume. These files have been backed up, but not in their present state.
Each line that begins with a minus sign (“-“) represents a file that has been removed from the source volume.
Files that you’ve excluded from backup, or that are excluded automatically, are ignored.
At the end of the output, you’ll get some lines like the following:
Added:
Removed:
Changed:
These lines show the total amount of data added, removed, or changed on the source(s) since the last snapshot.
Caution: Under some conditions, tmutil may falsely flag files as not having been backed up when in fact they have been. It can be confused by multi-linked files, or by files with a modification date earlier than the one in the snapshot. This will not be an issue for most users. If the results of the above procedure surprise you, inspect your snapshots directly.

Airport Extreme/Time Capsule backup volume could not be found?

I am having problem with Time Machine. When I try to backup using Time Machine, I get an error message, " The backup volume could not be found." Strangely, Time Machine recognized the drive when setting the Time Machine preferences, but not when I backup.
If i select from the 'select disk' again and try again i get Keychain Access error 25299 and have to delete that in the Keychain for it to even get to the point of counting down to start back up
I have erased my Time Capsule recently and was starting fresh but now i cannot get time machine running again...
In the shared section of the finder the time machine backup is only appearing in the network area rather than directly there...
Any ideas?
Many thanks.

Hi there.
I would suggest First Aid of your Keychain, but that hardly ever works (especially in this situation).
What I would do first, is go to ~/Library/Keychains/, grab the login.keychain and move it to the desktop. Log out, and log back in again. If that fixes it, then get the old login.keychain from the desktop and put it in the trash. (You will lose all your saved passwords for networks etc.)
If that doesn't work, unfortunately the only option would be to do an Archive & Install.
So you just need to put your 10.6 disk in again and install over the system.
Your personal data/files should still remain intact. Although I would still suggest making a backup (ironic considering the situation)
Cheers
Taylor

Time Machine backup volume will not mount

Similar Messages

Maybe you are looking for