Tinker Tool
Hello!
I downloaded the following: http://www.chip.de/downloads/TinkerTool_31872502.html
Now I have the problem that I cannot open or download any PDF-files in SAFARI or in FireFox.
What shall I do?
I deleted already the downloaded „Tinker“Programme, but the problem with the PDF-files is still present.
Thank you for your help!
And sorry for my bad English (I am much better in speaking/writing German) ;-)
I have changed a few of the different fonts section and it has done nothing
Looking at the TinkerTool window in your screen shot, it doesn't appear as though you've changed any of the font settings.
When you've changed them, relaunch Finder and they'll take effect.
Similar Messages
-
You don't have access to location for Screenshots (Tinker Tool location)?
I am getting a "You do not have permission to save files in the location where screen shots are stored" when I try a screenshot on the MacBook Pro.
I had set up a new folder called "Screenshots" using the Tinker Tool Utility on both my MacPro and MBP.
I tried setting it to Desktop in the pulldown and then going back to Custom and choosing the Screenshots_MBP folder again and got the same error.
So now I have changed the location on the MacBook Pro back to the Desktop and I am still getting this error.
Note: There was some issue with Mac mixing up my "Screenshots" folder on the MacBook Pro with the one on my Mac Pro. So I created a "Screenshots_MBP" on the MacBook Pro and set TinkerTool to put the screenshots there and I still got the error...Check the permissions for that folder - make sure your running account has write authority for it. To do that, do a Get Info on the folder, and check the settings at the bottom of the Get Info window.
-
Where do I go to download "tinker tools"? I'm new to Mac.
Where do I go to download " Tinker Tools"? I'm new to Mac.
If you're new to Mac, you actually may not need Tinkertool. New Mac owners, especially from the Windows world, tend to think their computers need more maintenance than it does.
But here's the link: http://bresink.de/osx/TinkerTool.html
Matt -
Time Machine - TROUBLESHOOTING
This article provides some troubleshooting tips for common Time Machine errors and problems.
It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
_*C o n t e n t s*_
*Section A. _TOOLS YOU MAY NEED*_
*A1. Time Machine Buddy widget*
*A2. Time Tracker*
*A3. Tinker Tool*
*Section B. _SET - UP PROBLEMS*_
|
*B1. I can't select my drive for use with Time Machine*
*B2. The Change Disk option doesn't work*
*B3. No last or oldest backup date shown*
*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
*Section C. _BACKUP FAILURES*_
|
*C1. Initial Backup Failed*
*C2. Other Backup Fails*
*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
*C4. "This backup is too large"*
*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*
*C6. The backup volume is read only*
*C7. "Error (12): Link of previous volume failed."*
*C8. Backup fails after Logic Board replacement*
*C9. "The back-up disk image could not be created."*
*C10. Error: (-50) Creating directory*
*C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
*Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
|
*D1. Stuck in Preparing*
*D2. Backup is Slow or "hung"*
*D3. TM is doing a full backup for no good reason*
*D4. My backups seem too large*
*Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
|
*E1. Backups were deleted unexpectedly*
*E2. I can't see some backups*
*E3. I can't see backups for a disk/partition that's no longer connected*
*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
*Section A. _TOOLS YOU MAY NEED*_
There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
_*A1. Time Machine Buddy widget*_
|
Click here to download the +*Time Machine Buddy*+ widget.
It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing CMD-C. This copies them to your "clipboard," so you can post them in a thread here (via CMD-V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /var/log for the other user.
Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
|
_*A2. Time Tracker*_
|
Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
|
_*A3. Tinker Tool*_
|
Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
Do not use any of the other options unless you know the possible consequences.
|
*Setcion B. _SET - UP PROBLEMS*_
_*B1. I can't select my drive for use with Time Machine*_
If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
|
_*B2. The Change Disk option doesn't work*_
If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
|
_*B3. No last or oldest backup date shown*_
|
If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
1. Do a +*Back Up Now.*+ That will often recover the info.
2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
3. A Log Out or Restart may fix it.
4. If they're still not shown, try a *"Full Reset:"*
|
a. Turn TM Off, de-select the drive (select "none"), note any exclusions in Options, quit System Preferences.
b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
d. Re-select your drive (and re-enter any exclusions).
e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
|
_*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
|
Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
Try a "Full Reset" as in item #B3.
|
*Section C. _BACKUP FAILURES*_
_*C1. Initial Backup Failed*_
The most common cause is the TM drive not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* should be GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be +Apple Partition Map+ for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
|
_*C2. Other Backup Fails*_
If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
*Messages that might indicate trouble:*
Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
. . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
These may indicate a problem with the first file referenced. See the next item.
If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
|
_*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock. If that backup completes normally, there's no real problem.
If the next one fails also, then there most likely is something wrong -- the question is, what?
Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
|
Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
|
If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
/Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
Go to TM's Preferences and click Options.
In the next panel, click the plus sign at the bottom.
In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
Select it, click Exclude, then Done.
Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
If the backup runs ok, then you need to figure out what's wrong with that file.
If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #B3).
If you get the same message for a different file, you may need stronger stuff:
a. Exclude your TM disk from any anti-virus scanning.
b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
c. Do a +*Repair Disk*+ (not permissions) on your TM drive/partition, via Disk Utility (in your Applications/Utilities folder).
d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
e. If the original file is on your internal HD, do a +*Verify Disk*+ (not permissions) on it. If that reports errors, you'll have to boot from your Leopard Install disc and use it's copy of Disk Utility to repair it:
1. Insert your Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
2. Select your language when prompted.
3. On the next screen select Utilities in the Menubar, then +*Disk Utility.*+
4. Do a +*Repair Disk*+ on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
5. Reboot normally.
If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
|
_*C4. "This backup is too large"*_
|
For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
There are some backups that Time Machine *will not delete,* however. It won't delete the most recent backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it won't delete any from the prior sequence, either.
Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
When this happens, you have a few options:
1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
2. Erase the TM disk/partition and let TM start over, with a new, full backup of your entire system.
3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
4. Get a different disk/partition for your Time Machine backups. Then either:
Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder. Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
|
_*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*_
|
Open the Terminal app (in your Applications/Utilities folder).
Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
(where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
<pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
|
_*C6. The backup volume is read only*_
First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
If that doesn't correct it,
If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
If you don't want to erase it, here's a workaround:
First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
If not, use the TinkerTool app (see #A3) to show hidden files.
In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet address). Copy or make a note of it.
Then follow the rest of the instructions in item #C5.
|
_*C7. "Error (12): Link of previous volume failed."*_
|
This usually happens when you replaced a drive with a different one, but with the same name as the original.
Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
|
_*C8. Backup fails after Logic Board replacement*_
The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or control-click (right-click) the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
|
_*C9. "The back-up disk image could not be created."*_
|
If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
|
_*C10. Error: (-50) Creating directory*_
|
This may indicate a problem with your TM drive. Use Disk Utility (in your Applications/Utilities folder) to do a +*Repair Disk*+ (not permissions) on it. If any errors are found that Disk Utility can't fix, run it again (and again) until they're all fixed or it can't fix any more.
If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #B3.
If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
|
_*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
|
If this happens after getting a new Logic Board, see item #C8.
This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
If that doesn't help, try a complete reset. See item #B3.
|
*Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
_*D1. Stuck in Preparing*_
|
See this Apple Support document: Time Machine may display "Preparing" for a longer time
Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
Also see the next topic:
|
_*D2. Backup is slow or "hung"*_
|
Get the Time Machine Buddy messages (see #A1).
If it shows Event store UUIDs don't match
and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
1. Exclude your TM disk/partition from any anti-virus scanning.
2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
_*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them.
4. Try moving the TC or AEBS and Mac closer together.
5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
6. Try repairing the Sparse Bundle with Disk Utility (in your Applications/Utilities folder). Mount the Sparse Bundle, then drag it into the Disk Utility sidebar, then use +*Repair Disk*+ (not permissions).
_*If backing up to an External hard drive:*_
7. Do a +*Repair Disk*+ (not permissions) on it via Disk Utility (in your Applications/Utilities folder).
8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard).
10. Try different port(s), cable(s).
11. See if your drive has an automatic sleep or "spin down" feature you can disable.
12. Check the maker's web site (support or forum) for any updates.
If nothing helps, your drive may be failing.
|
_*D3. TM is doing a full backup for no good reason*_
Time Machine may do a full backup after any of the following:
Using a new disk or partition for backups (always).
A full restore (probably).
Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
Changing your computer's name via System Preferences > Sharing (probably).
Renaming a disk/partition that's being backed-up (probably).
Going several days without a backup (probably; also seems to depend on the volume of changes).
Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
|
_*D4. My backups seem too large*_
|
Time Machine may be doing a full backup of your entire system. See item #D3.
Doing an OSX update can cause a large backup, as it may add or update several thousand files.
Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
|
*Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
_*E1. Backups were deleted unexpectedly*_
|
Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
Usually when this happens unexpectedly, it's because TM has done a new full backup, which of course requires a lot of space. See item #D3 for the common reasons.
If in doubt, get the widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
|
_*E2. I can't see some backups*_
|
TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your Dock.
You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
|
_*E3. I can't see backups for a disk/partition that's no longer connected*_
|
Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
Select the Finder window for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
|
_*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
|
Do a +*Repair Disk*+ (not permissions) on your TM drive, via Disk Utility (in your Applications/Utilities folder).
Re-select your TM drive via TM Preferences > Change Disk.
If you're using Spaces, try disabling it, at least temporarily.
If you have any sort of video out cable, especially HDMI, try disconnecting it, at least temporarily.
Do a "complete reset" of TM, as in item #B3.This article provides some troubleshooting tips for common Time Machine errors and problems.
It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
_*C o n t e n t s*_
|
*Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
|
*A1. Time Machine Buddy widget*
*A2. Time Tracker*
*A3. Tinker Tool*
*A4. Full Reset of Time Machine*
*A5. How to do a Repair or +Verify Disk+*
*Section B. _SET - UP PROBLEMS*_
|
*B1. I can't select my drive for use with Time Machine*
*B2. The +Change Disk+ button doesn't work*
*B3. No last or oldest backup date shown*
*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
*Section C. _BACKUP FAILURES*_
|
*C1. Initial Backup Failed*
*C2. Other Backup Fails*
*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
*C4. "This backup is too large"*
*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM drive>"*
*C6. The backup volume is read only*
*C7. "Error (12): Link of previous volume failed."*
*C8. Backup fails after Logic Board replacement*
*C9. "The back-up disk image could not be created."*
*C10. Error: (-50) Creating directory*
*C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
*Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
|
*D1. Stuck in "Preparing" or "Calculating changes"*
*D2. Backup is Slow or "hung"*
*D3. TM is doing a full backup for no good reason*
*D4. My backups seem too large*
*Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
|
*E1. Backups were deleted unexpectedly*
*E2. I can't see some backups*
*E3. I can't see or restore from backups for a disk/partition that's no longer connected*
*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
*Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
_*A1. Time Machine Buddy widget*_
|
Click here to download the +*Time Machine Buddy*+ widget.
It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing Cmd+C. This copies them to your "clipboard," so you can post them in a thread here (via Cmd+V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /private/var/log and it's contents for the other user.
Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
|
_*A2. Time Tracker*_
|
Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
|
_*A3. Tinker Tool*_
|
Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
Do not use any of the other options unless you know the possible consequences.
|
_*A4. Full Reset of Time Machine*_
|
a. Go to TM Preferences, turn TM Off, de-select the drive (select "none"), and click the Options button. Note any exclusions in the +Do Not Back Up+ box, and other option(s) on that panel. Then quit System Preferences.
b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
d. Go back to TM Preferences, re-select your drive, re-enter any exclusions and other options.
e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
|
_*A5. How to do a Repair or +Verify Disk+*_
|
This will Repair or Verify the +File System+ on a disk, partition, or sparse bundle (not the actual hardware). Use the +*Disk Utility+* app, in your Applications/Utilities folder. Do this when TM backups are turned-off, or at least not running.
To Repair an *external disk attached to an Airport Extreme,* disconnect it from the Airport, connect it directly to your Mac and select it in the Disk Utility Sidebar.
To Repair an external or *internal Time Machine* disk/partition, select it in the Disk Utility Sidebar.
To Repair the *sparse bundle* on a Time Capsule, connect via an Ethernet cable if you can; it will be much faster. Then mount the sparse bundle by opening the TC in the Finder and double-clicking on the sparse bundle. Drag the sparse bundle into Disk Utility's sidebar and select it.
With the desired partition or sparse bundle selected, click the +*Repair Disk+* (not permissions) button. This may take a while, especially on a Time Capsule. If errors are found, but not all of them were repaired, run the +*Repair Disk+* again, and again, until it either fixes all the errors or can't fix any more.
To Verify your internal (boot) drive/partition (since you can't Repair the one you're running from), select it in Disk Utility's sidebar and click the +*Verify Disk+* (not permissions) button. If it shows errors, you'll need to fix them via this procedure:
1. Insert your Leopard/Snow Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
2. Select your language when prompted.
3. On the next screen, select Utilities in the Menubar, then +*Disk Utility.*+
4. Do a +*Repair Disk*+ (not permissions) on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
5. Reboot normally.
|
*Section B. _SET - UP PROBLEMS*_
_*B1. I can't select my drive for use with Time Machine*_
If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
|
_*B2. The +Change Disk+ button doesn't work*_
If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
|
_*B3. No last or oldest backup date shown*_
|
If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
1. Do a +*Back Up Now.*+ That will often recover the info.
2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
3. A Log Out or Restart may fix it.
4. If they're still not shown, try a Full Reset (see #A4).
|
_*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
|
Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
Try a "Full Reset" as in item #A4.
|
*Section C. _BACKUP FAILURES*_
_*C1. Initial Backup Failed*_
The most common cause is the TM drive (but not a Time Capsule) not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* must be either GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be either +Apple Partition Map+ (preferred) or GUID for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
|
_*C2. Other Backup Fails*_
If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
*Messages that might indicate trouble:*
Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
. . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" (Leopard) or "Calculating changes" (Snow Leopard) phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
These may indicate a problem with the first file referenced. See the next item.
If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
|
_*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock. If that backup completes normally, there's no real problem.
If the next one fails also, then there most likely is something wrong -- the question is, what?
Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
|
Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
|
If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
/Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
Go to TM's Preferences and click Options.
In the next panel, click the plus sign at the bottom.
In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
Select it, click Exclude, then Done.
Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
If the backup runs ok, then you need to figure out what's wrong with that file.
If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #A4).
If you get the same message for a different file, you may need stronger stuff:
a. Exclude your TM disk from any anti-virus scanning.
b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
c. Do a +*Repair Disk*+ on your TM drive/partition. See #A5 above.
d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
e. If the original file is on your internal HD (your boot drive), do a +*Verify Disk*+ on it. See #A5 above.
If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
|
_*C4. "This backup is too large"*_
|
For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
There are some backups that Time Machine *will not delete,* however. It won't delete the last remaining backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it may not delete any from the prior sequence, either.
Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
When this happens, you have a few options:
1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
2. Erase the TM disk/partition with Disk Utility (in Applications/Utilities) and let TM start over with a new full backup.
3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
4. Get a different disk/partition for your Time Machine backups. Then either:
Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder (in Snow Leopard only, you can copy the Backups.backupdb folder via the Finder). Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
|
_*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM Drive>"*_
|
Open the Terminal app (in your Applications/Utilities folder).
Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
(where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
<pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
|
_*C6. The backup volume is read only*_
First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
If that doesn't correct it,
If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
If you don't want to erase it, here's a workaround:
First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
If not, use the TinkerTool app (see #A3) to show hidden files.
In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet Address). Copy or make a note of it.
Then follow the rest of the instructions in item #C5.
|
_*C7. "Error (12): Link of previous volume failed."*_
|
This usually happens when you replaced a drive with a different one, but with the same name as the original.
Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
|
_*C8. Backup fails after Logic Board replacement*_
The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or right-click the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
|
_*C9. "The back-up disk image could not be created."*_
|
If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
If that doesn't help, apply the same rules to the name of your Time Capsule.
|
_*C10. Error: (-50) Creating directory*_
|
This may indicate a problem with your TM drive. Do a +*Repair Disk*+ on it. See #A5 above.
If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #A4.
If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
|
_*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
|
If this happens after getting a new Logic Board, see item #C8.
This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
If that doesn't help, try a full reset. See item #A4.
|
*Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
_*D1. Stuck in "Preparing" or "Calculating changes"*_
|
See this Apple Support document: Time Machine may display "Preparing" for a longer time
Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
Also see the next topic:
|
_*D2. Backup is slow or "hung"*_
|
If this is your first backup under Snow Leopard after updating from Leopard, try cancelling the backup, doing a Restart, and trying again.
Otherwise, get the Time Machine Buddy messages (see #A1).
If it shows Event store UUIDs don't match
and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
1. Exclude your TM disk/partition from any anti-virus scanning.
2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
_*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them. Remove any punctuation and spaces. Do the same with the Time Capsule or Airport Extreme name.
4. Try moving the TC or AEBS and Mac closer together.
5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
6. Try repairing the TC's Sparse Bundle or AEBS drive's TM disk/partition. See #A5 above.
_*If backing up to an External hard drive:*_
7. Do a +*Repair Disk*+ on it. See #A5 above.
8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard, as some are USB 1.0).
10. Try different port(s), cable(s).
11. See if your drive has an automatic sleep or "spin down" feature you can disable.
12. Check the maker's web site (support or forum) for any driver or firmware updates.
If nothing helps, your drive may be failing (they all do, sooner or later).
|
_*D3. TM is doing a full backup for no good reason*_
If this is your first backup on Snow Leopard after upgrading from Leopard, try cancelling the backup, doing a Restart, and trying again.
Time Machine may do a full backup after any of the following:
Using a new disk or partition for backups (always).
A full restore (probably).
Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
Changing your computer's name via System Preferences > Sharing (maybe).
Renaming a disk/partition that's being backed-up (probably).
Going several days without a backup (probably; also seems to depend on the volume of changes).
Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
|
_*D4. My backups seem too large*_
|
Time Machine may be doing a full backup of your entire system. See #D3.
Doing an OSX update can cause a large backup, as it may add or update several thousand files.
Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
|
*Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
_*E1. Backups were deleted unexpectedly*_
|
Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
In addition, regardless of space, TM also routinely "thins" your backups. It keeps one per week for as long as there's room; one per day (the first) for a month; all others for 24 hours.
Usually when old weekly backups are deleted unexpectedly, it's because TM has done a new full or large backup, which of course requires a lot of space. See #D3 or D4 for common reasons.
If in doubt, get the +Time Machine Buddy+ widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
|
_*E2. I can't see some backups*_
|
If you can't see the backups for a disk/partition that's no longer connected, see #E3 below.
TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by right-clicking the TM icon in your Dock.
You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
|
_*E3. I can't see backups for a disk/partition that's no longer connected*_
|
Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
Select the Finder window or TimeLine entry for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
Also note that you cannot use the normal Restore button at the bottom of the screen to restore selected items, since they're from a different disk/partition. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
You can restore an entire disk/partition to a different one (erasing any previous contents) via the procedure in item #14 of the Frequently Asked Questions *User Tip* at the top of this forum.
|
_*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
|
This can be caused by any of a number of things. Try these fixes:
If you're using a Finder replacement (such as Pathfinder), be sure the Finder is running.
If you're using Spaces, turn it off temporarily.
If you have a second monitor, or anything plugged-in to a video-out port, disconnect it temporarily.
De-select your TM drive via TM Preferences > Change Disk (select "none"), then re-select the correct one.
Do a "complete reset" of TM, as in item #A4.
Do a +*Repair Disk+* on your TM drive. See #A5 above.
Try or create another user (System Preferences > Accounts). If it works ok from that user, delete the file:
+*<home folder of the user where it doesn't work>/Library/Preferences/com.Apple.Finder.plist+* -
My TM is often giving me the "You do not have appropriate access privileges to save file “.002332b7be8a” in folder “Time Machine Backups”" message when I go to select my backup drive. I've reviewed past archived discussions on this and, like many other people, gotten completely flummoxed trying to find a permanent solution. Tried the suggested fixes via Terminal and it didn't help because I couldn't get through the entire process without Terminal telling me it couldn't find a file or drive. When I can find the time, I'm going to try Tinker Tool to reveal where that numbered file actually is and give it another go.
In the meantime, for those who are desperate to get their TM working again to get at least one backup done, I can offer people a temporary solution that's worked for me.
I've found that restarting my iMac somehow resets TM and usually allows it to do at least one of its automatic backups, sometimes several, before it reverts back to failing and producing that same darn warning message. I only want a backup done once a day, so it's not that inconvenient to go this route.
There's another even quicker method (perhaps a little more risky but hasn't been a problem for me yet) that I've been using more recently, and that is to simply unplug the external while the iMac is on (I close system preferences first though, and make sure TM isn't actually doing anything at the time) then plugging it back in and choosing the backup drive again in the TM system preferences window once that drive has shown up again in the Mac's list of devices. I don't get that warning message when I do this. It works every time for me and so far it hasn't lost or corrupted any data on the external, despite the warning message you get on Macs when you unplug a USB device without ejecting it first. However, do this at your own risk--don't flame me if it backfires on you. If you're of the opinion that it's not wise to unplug the device this way, then fine, go ahead and state such in this thread, but be polite about it.
Hope this helps anyone who's frantic to make a backup without having to start from square one with a whole new complete initial backup (can take many hours to make one) on a fresh external drive.
By the way, I've read somewhere that this problem was fixed with Snow Leopard. Whether that's true is another matter. I'm not quite ready to update to 10.6 for other reasons, even though I bought it, and I figure some other people are also still using 10.5.8 out of fear and loathing around the unknowns of installing a new OS too, so that's why I thought I'd post this message (couldn't find a discussion around this that was still active and not archived).noodlenose wrote:
My TM is often giving me the "You do not have appropriate access privileges to save file “.002332b7be8a” in folder “Time Machine Backups”" message when I go to select my backup drive.
Wow, I haven't seen that in a looooong time!
Tried the suggested fixes via Terminal and it didn't help because I couldn't get through the entire process without Terminal telling me it couldn't find a file or drive.
Do you mean in #C5 of Time Machine - Troubleshooting?
When I can find the time, I'm going to try Tinker Tool to reveal where that numbered file actually is and give it another go.
It should be at the top level of the drive.
By the way, I've read somewhere that this problem was fixed with Snow Leopard.
Yes. I'm not sure if it was 10.6.0 or one of the early updates, but I haven't seen any reports of this in quite a while. -
Error message by periodic weekly: No output from the 1 file processed
Hi there,
since four weeks, I got a problem with the maintenance script periodic weekly. Up to December 22nd, the script did, what it should do: rebuilding the database of locate and whatis, rotating log-files. Since one week later, I got the error message: No output from the 1 file processed.
Normally, I use Anacron to do the job. When I noticed the problem, I tried to start the script with Tinker Tool System getting the same result. Another try using the Terminal (sudo periodic weekly) also failed. The commands locate and whatis are working, locate.updatedb and makewhatis also. I'm running 10.4.8; in the past, I did not have such problems. Anyone with an idea or solution?
Thanks
Klaus
MacBook Pro Mac OS X (10.4.8)Hi Gary,
here is the output you were asking for:
Last login: Thu Jan 25 20:03:55 on console
Welcome to Darwin!
DeepThought:~ dirk$ sudo /private/etc/periodic/weekly/500.weekly; echo $?
Password:
Sorry, try again.
Password:
Rebuilding locate database:
Rebuilding whatis database:
find: /usr/local/man: No such file or directory
makewhatis: /usr/share/man/man1/fetchmailconf.1.gz: No such file or directory
Rotating log files: ftp.log lpr.log mail.log netinfo.log ipfw.log ppp.log secure.log
access_log error_log
Running weekly.local:
Rotating psync log files:/etc/weekly.local: line 17: syntax error near unexpected token `)'
/etc/weekly.local: line 17: `if [ -f /var/run/syslog.pid ]; then kill -HUP 0 80 79 81 0cat /var/run/syslog.pid | head -1); fi'
2
DeepThought:~ dirk$ ls -loe /private/etc/periodic/weekly/500.weekly
-r-xr-xr-x 1 root wheel - 2532 Jan 13 2006 /private/etc/periodic/weekly/500.weekly
DeepThought:~ dirk$
It seems, Rogers idea, PsynX respectively the deficient uninstalling by me is responsible for my problems, is correct. Should I remove the whole file weekly.local or should I only remove the content? I prefer removing the whole file, because it was created while installing PsyncX. The date of creation is the same as the date of installing the app (December 25).
Klaus
By the way: it seems to me, the solution of my problem is in sight. So I want to thank you all for the amazing aid I got from you! -
Hello.
I would like your help on a software update issue.
I am running 10.9.1 on a retina Macbook Pro and I have disabled updates through the System Preferences - App Store option, where I have deselected all options for upgrading/updating.
For some reason - which I cannot understand - OSX decided to download 10.9.2 in the backround and preinstall tha initiall part (or whatever it does to prep it).
I realized it immediately because while I was working today a popup came up on the screen saying that it will reboot to install and I barely managed to press the later option...
Upon checking in the App Store I have the screen below...which leads me to believe that if I reboot it will install 10.9.2 and I will not be able to stop it, nor will I be able go back to 10.9.1.
I recently formated my time machine HDD, so I do not have any earlier backup to revert to and I do not want to upgrade to 10.9.2, as it ruins my whole font setup that I have going with Tinker Tool. Is there any way that I can cancel or rectify this. I can't avoid a reboot for ever.
Any help will be greatly appreciated.thanks for the swift reply Kapy!
As I said, I formatted my time machine a couple of days ago DOH and I don't have any other backups. The only backup I have is the full one that I took today (around 400gigs) after this happend...But I assume that even if I used it...it would lead to an install upon installing and rebooting, since it is a backup the state OSX is now.
As for the files that are in my /Library/Updates/ folder, here is a screenshot. If I delete something in here, will it prevent OSX from installing 10.9.2 upon rebooting? -
Disk permissions - "Error: No Valid Packages (-9997)"
Should I worry about this error? It shows up when I try to "verify permissions" via Disk Utility (booted from disk) and I also ran Tinker Tool System and it gave the same error.
Thanks for the help!
KenYou've either removed the /Library/Receipts/ folder or deleted its contents. Disk Utility will no longer work nor will Software Update.
Download a shareware utility called Pacifist 2.0. Use it to extract a fresh copy of the BaseSystem.pkg from the file archives on your Tiger DVD. Extract the new copy of BaseSystem.pkg to the /Library/Receipts/ folder. If you've deleted the folder simply make a new folder with that name. In the future do not delete the folder or its contents. They are needed for permissions repair and updating software with Software Update.
Why reward points?(Quoted from Discussions Terms of Use.)
The reward system helps to increase community participation. When a community member gives you (or another member) a reward for providing helpful advice or a solution to their question, your accumulated points will increase your status level within the community.
Members may reward you with 5 points if they deem that your reply is helpful and 10 points if you post a solution to their issue. Likewise, when you mark a reply as Helpful or Solved in your own created topic, you will be awarding the respondent with the same point values. -
Is there any way to change the default search parameters in Mail?
When I do a search it only checks "Today" instead of "Inbox." So then I have to select Inbox and reenter my search. Not a huge deal, but a bit bothersome. Any way to just set it to search "Inbox" by default instead of "Today?"
No. You will see many posts about tinker tool ,but that wont change Adobe Apps fonts, only apple applications.
-
I'm having this problem with iCal 5.0.1 and Lion on two different iMacs: a 2010 i7 and a 2008 Core 2 Duo. Both are up to date with system updates, etc.
The problem is this: each and every time I edit iCal -- new event, change an old event, edit a current event, etc -- iCal takes 10 to 30 seconds to update. I get the spinning beachball each time. Sometimes the menu bar title says 'iCal ... updating', sometimes not. Then the very NEXT mouse click in iCal, anywhere, gets me another spinning beachball for another 10 to 30 seconds.
This does NOT happen with iCal 5.0.1 on my brand-new MacBook Air running Lion (came installed). Both the iMacs were updated to Lion from SL, etc.
I can sync the calendars without problems between the three computers and with my iPhone 4 and iPad 2, all via iCloud. An event entered on one device shows up properly on the other devices.
The slow-down problem was happening when I was using MobileMe to sync but was not as bad; it's much worse now that I'm syncing with iCloud. Likewise, it occurred when the iMacs were running SL but not as bad; now much worse with Lion. On each iMac, I changed the 'refresh calendars' in the Accounts tab in preferences from 'push' to 'every five minutes' but that hasn't helped. I am syncing three calendars ('home', 'work', 'consulting') via iCloud, and one calendar on the Mac.
Each calendar has a number of events. I edited all the repeating events so that they all end at the end of 2012, wondering if perhaps repeating to infinity was a problem, but that hasn't helped.
On both iMacs, I have trashed the iCal.plist in my library preferences and then logged-out/logged-in, but that also hasn't helped.
Any suggestions? iCal is pretty much unusable on the iMacs.
Thanks in advance,
SteveI had the same issue, almost exactly. This worked for me:
https://discussions.apple.com/message/15676949#15676949
Application UI issues are in most cases, caused by a corrupt plist file.
Quit iCal, and try removing the com.apple.iCal.plist file from your Macintosh HD/Users/yourusername/Library/Preferences Folder. Since that Library is now hidden, you have to use the Finder>Go Menu>Depress the "Option" key>Library. Drag the .plist file to your desktop, and log out/in or restart and check iCal for functionality.
(Many thanks, Ferd II)
But in order to see the files and folders I used Tinker Tool:
http://download.cnet.com/TinkerTool/3000-18487_4-19260.html -
Freezing and resetting solution, playlists the culprit, take a look Apple
Hi there, I've had a major issue with my 160gb ipod classic from day 1.
I've got a 140g music library on my PC and I've not been able to sync it to the ipod because of freezing and resetting problems.. until today.
When I first tried to sync my whole music library the ipod crashed as soon as I disconnected it. I had to restore the ipod and soon learned to sync my music in 10gb chunks. Only trouble was the ipod would work fine as long as I only synced 70-80gb of music, which is half the ipod's capacity. If I tried to add any more music the ipod would eventually go into the freezing and resetting loop and I'd have to restore it and start again.
I know other users on here have had similar problems. Firmware 1.1 and itunes 7.6 did not fix the issue for me. I know that my mp3 files are not the problem because if I split my music library into two 70gb chunks I could sync either chunk without problems, it was only when I tried to sync them all...
Through lots of trial and error, such as reinstalling OS, reinstalling itunes, rebuilding library, scanning mp3 files for errors I have eventually found out what was causing my problem.
I have 100s of pretty complex smart playlists, they are heavily nested and dependant on other playlists. I've got them all organised into folders for easier navigating. This was one of the reasons I couldn't wait for the ipod classic to come out because my playlist folders would at last be recognised on the ipod. I recently added a pretty big playlist tree for playing songs from a given year and noticed that itunes got even more sluggish than usual!
I looked at my library file and it had grown to nearly 100mb. As an experiment I backed up my library file first than deleted all of my playlists. The size of the library file reduced to 34mb. I decided to try and sync more music onto my ipod without the playlists... and would you believe it I've been able to sync my whole music libary to my ipod for the first time - no freezing and no resetting!
I would hazard a guess that the ipod classic firmware currently has an issue syncing lots of complex, nested playlists. I've fed this back to apple and hope they can come up with a solution. I hope it's not an issue related to the reduced size of the RAM in the new ipods, otherwise there will never be a solution!
As it stands I'm gonna really simplify my playlists and keep my fingers crossed. I love playlists, they're a massive part of the whole ipod experience for me so scaling them back will be a real trade off but if it stops the resetting problems I'll have to do it. This is working for me so far so good luck to everyone else who has been having similar problems.
Message was edited by: DamenQDamenQ
thank you so much for this information. I can not tell you, how helpful your posting is.
I had exactly the same problem, and I did follow your instructions - and for the first time in almost 3 month (and after hours and hours spent on my computer to try to resolve this problem), I am able to utilize the full capacity of my 160 GB iPod Classic.
It is very unfortunate, that I am currently not able to utilize my Folders and Playlists (just like you, I have hundreds of them which are a huge part of the iPod Experience), but at one point, my iPod was no longer able to start up and got stuck in a 're-boot' loop. After removing my most complex smart playlists, the problem disappeared (I did not remove them from iTunes, but I no longer synch them to my iPod).
So again, thanks for posting this information, and thanks for contacting Apple. I really hope, that this issue will be resolved in the next Firmware release.
FYI for anybody else who might read this post : Using the Tinker Tool (free download) makes it very easy to monitor/view the hidden files on your iPod. -
Suddenly can't back-up with Time Machine
Time Machine has finally completely quit. I have followed most of the suggestions on various Apple forums, including reformatting the backup HD (several times), repairing both the back-up and main HD, settting spotlight to private, quitting Finder (using Tinker tool), etc. Followed Pondini's very useful steps repeatedly. I get different error messages from Time Machine Buddy most every time. The most consistent refers to indexing.
Below are the three most recent Buddy logs, in hopes somebody can help. Or suggest another backup solution.
Starting standard backup
Backing up to: /Volumes/Hitachi Orange/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Detected system migration from: /Volumes/Macintosh HD 1
Backup content size: 498.4 GB excluded items size: 460.7 GB for volume Macintosh HD
No pre-backup thinning needed: 45.22 GB requested (including padding), 930.58 GB available
Waiting for index to be ready (101)
Indexing a file failed. Returned 200 for: /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx-2 .8-mac-unicode/wx/lib/inspection.pyc, /Volumes/Hitachi Orange/Backups.backupdb/Galloway Desktop (3)/2011-07-08-190340.inProgress/F18A8582-E9F7-4D93-9BA0-07DEB1749449/Macintosh HD/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/wx -2.8-mac-unicode/wx/lib/inspection.pyc
Aborting backup because indexing of file failed.
Stopping backup.
Copied 60774 files (16.3 GB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11
The one before
Starting standard backup
Backing up to: /Volumes/Hitachi Orange/Backups.backupdb
Detected system migration from: /Volumes/Macintosh HD 1
No pre-backup thinning needed: 37.67 GB requested (including padding), 877.17 GB available
Indexer unavailable (200)
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0a4b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “info.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “keyedobjects.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1005312b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Copied 0 files (35 KB) from volume Macintosh HD.
Backup canceled.
And before that
Starting standard backup
Backing up to: /Volumes/Hitachi Orange/Backups.backupdb
Detected system migration from: /Volumes/Macintosh HD 1
No pre-backup thinning needed: 37.67 GB requested (including padding), 877.17 GB available
Indexer unavailable (200)
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0a4b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “info.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x102e0cf10 "The file “keyedobjects.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1005312b0 "The file “classes.nib” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x103004520 "The operation couldn’t be completed. Input/output error")
Copied 0 files (35 KB) from volume Macintosh HD.
Backup canceled.
Any help would be most appriciated.
This is my iMac (Late 2010) running OS X 10.6.8, backing up to a 1Tb Hitachi external HD, connected directly (no hub) via usb.It's possible that the system was keeping some piece of the I/O error in memory and, after the underlying cause of the I/O error went away, something you did juggled the system's brain back to a non-error condition.
You are absolutely correct to remain suspicious of your HD. While it's possible that changing USB cables or zeroing out the disk might have solved the underlying I/O problem it's equally possible that you have a failing drive on your hands that may only be showing ugly symptoms sporadically. There is a small risk that you will end up with two sets of damaged data if a drive fails during data transfer so it was very wise of you to order another drive.
You might want to consider using Carbon Copy Cloner or Super Duper! to make a clone to your new drive. Having a TM backup and one or more clones, all on separate physical drives, is a very effective backup solution. That's the combo I use.
When my Mini's internal drive failed it took about five minutes to boot from one of my clones, restore a few files from my TM backup, set TM to back up the clone, set SuperDuper to back up to my second clone. After that, I was fully back in business by booting from my clone which allowed me to get the Mini's HD repaired when it was convenient for me. -
How do I remove "Recent Items" Documents from the apple menu?
I've been searching for an answer to this question for the better part of 3 hours now. W
Several iterations of osx ago, there was the ability to separately limit how many recent items were shown for Applications, Documents and Servers. Over the years, I simply installed a newer version of osx on top, and surprisingly my recent items always eliminated the Documents from the list.
I've since done a clean install of mavericks after installing an SSD, and i've lost this small but important part of my work flow. No matter what I've tried to remove the documents from Recent Items, it always shows up. I can still boot into my old HDD (which is now installed as a supplementary drive and also updated and running mavericks 10.9.2), and see from clicking on the Apple Menu > Recent Items that it only displays Applications and Servers.
Try as hard as I can, I can't simply figure out how to remove the documents from the recent items menu. I've tried editing the com.apple.recentitems.plist file, to show 0 items for documnets, but this never seems to work. (I've since read that this file is simply rewritten on logout.) Strangely, if I go into the old setup System Preferences, Recent Items: it is showing as None. I also suspect that maybe I used Tinker Tools or some other utility to change some command line preference (using the gui) several years back. Not sure how I could investigate what would need to be done to compare files or otherwise figure out how to remove the documents section from the recent items menu.
It's starting to drive me crazy. Anyone?The Apple menu is at the top left hand corner of your screen, click on it and about this Mac is the first choice.
Click twice on Version to get serial number. -
Time Machine Back Up to WD My Book Stopped Working
I use Time Machine to Backup my iMac (OS X 10.6.6) to an external WD My Book. Suddenly all backups seem to complete, no error is shown, but the latest backup remains January 13, 2011. I am able to open Time Machine and see the January 13 backup and those from before. The SysLog shows the following:
Feb 20 08:43:01 Macintosh-5 mds[44]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/97C4146A-AB02-4C38-9A59-816F328E9B55)(E rror) IndexSDB in dbflushdatastore:/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/97C4146A-AB02-4C38-9A59-816F328E9B55/st ore.db : dbsyncdatastore: prior write-errors invalidate sync.
Feb 20 08:43:01 Macintosh-5 mds[44]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/97C4146A-AB02-4C38-9A59-816F328E9B55)(E rror) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
What does this mean, an how do I fix it?ab5689 wrote:
Feb 20 08:43:01 Macintosh-5 mds[44]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/97C4146A-AB02-4C38-9A59-816F328E9B55)(E rror) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
What does this mean, an how do I fix it?
That means the (hidden) Spotlight index on your backup drive is corrupted.
Download the free [Tinker Tool|http://www.bresink.com/osx/TinkerTool.html] app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
Very carefully, open your Time Machine drive with the Finder and delete the .Spotlight-V100 folder. Be very careful not to change, move, or delete anything else there.
If you're running any anti-virus software, exclude your TM drive from it (or, better, turn it off). -
Here's a cure for 'clunking' Hard Disks on MacBook Pro's..
I've had this problem with a 'clunking' (i.e. marble dropping onto a granite floor sound) coming from the hard disk area of my year old MacBook pro Core2Duo with a 120Gb Fujistu Drive. On my MBP it happened every 20 secs or so and was really annoying, in a quiet room you could here it and I was worried about the reduced lifespan on the drive. Many users have complained about this, not just MBP users but also on the Mac Mini, which I understand uses Seagate drives
There's lot of discussion on this; replacing the drive (if under Apple Warranty that is), running a utility that keeps the heads unparked by constantly writing data to the drive, or some users are told just to live with it because its normal. WRONG, HERE'S THE ANSWER THAT WORKED FOR ME!
*I downloaded a copy of the brilliant (and free!) utility: Onyx (my version 1.8.3) from www.titanium.free.fr*
It's a general 'housekeeping' MAC OS X program and I got it to do a full Permission Check; Optimize the system; clear cache on Safari, spotlight, font and kernel. Basically I set it to clear/reset everything on the download cache and temporary settings and reset the Spotlight Index also.
Since I've done this I'VE HAD NO NOISE (CLUNKS) FROM THE DRIVE.
So I guess it must have been some indexing routine that was causing the drive to go mad
Hope it works for you:
*Nick B, UK*okay, good point. I'm running Tiger still..
I seen that. I believe Cocktail and Tinker Tool have been updated and should work the same.
-Bmer
Mac Owners Support Group - Join us @ MacOSG.com
Mac611 Mobile Mac Support - about.Mac611.com
iTunes:MacOSG Podcast | YouTube.MacOSG.com
An Apple User Group
Have an iPhone or iPod touch? Enter Mac611.com in Safari on it for 'mobile Mac support.'
Note: I receive no compensation for product endorsements.
Maybe you are looking for
-
Invoice(which are complete already) grouping for just output purpose
Dear Experts, I have requirement to group the invoices which are complete through VF01 and VF04, and to create an output using the smart from that we have developed I understand VF21 actually to create Invoice list which are due for the payer. So I
-
Error Handling Inside BPM Process
Hi All, I have a scenario in which, when a BPM Process errors out due to any of the System Exception I'm catching it using a Event SubProcess activity and handling it. Problem: I want the control to get back to the next activity i.e Normal Process sh
-
does anyone have any suggestions on how to do the rest of this project import javax.swing.JOptionPane; public class Bank { private static char which; public static void main(String args[]) Account[] bankAcct = new Account[30]; int
-
after a disaster last night buying and trying to install lion i now need to do a factory reset on my imac. I have a 15 month old imac bought from john lewis who provide a 2 year warrany independent of apple. Last night i downloaded lion only to be me
-
Rollup in cube is taking very long time (BW 3.5)
Hi, Rollup in one of our cube is taking a long time from what it is expected. Previously this rollup was taking 2-3 hrs but now it is taking more than 8 hrs. To solve this I even tried compressing the cube till last month but of no use. (this worked