Time machine will not work after upgrade

Since I upgraded to Mavericks on Oct. 22, Time Machine will not run properly, or at all for that matter. It tells me that it is 'Preparing Backup', but it was said that for over 4 days now. Suggestions?

I had a strange issue with Time Machine and Mavericks. Time machine wouldn't recognise the external USB drive I was using for backups. There was nothing in the logs, no errors, the time for the backup would come along and then it would skip to the next hour with no backup being done. What I was doing was removing the drive from Time Machine Preferences and re-adding it, TM would then start a manual backup and from that point it would run fine.
I ended up doing a Disc Verify on the drive (all ok, no issues) and shut the machine down. Today I booted up and staright away the TM Icon for the drive is correct and the TM is running as it used to.
I have three macs, all with external USB drives, the other two macs have no issues with TM, only my main one. Having a look at other issues, my external drive is a Western Digital unit so maybe that has something to do with it, though it can see the drive fine from Finder.
Anyway, if you are having similar issues, just run the Disc Verify Utility (and repair if there are errors) and hopefully it'll fix up that particular issue.

Similar Messages

Time Machine will not work after installation of Mountain Lion

I installed Mountain Lion and currently can not set up Time Machine via my AirPort and Iomega HDD. I worked flawless prior to the Mountain Lion installation. Can anyone assist.

Your best bet is to call apple tech support at 800-694-7466 or go the the genius bar.
Allen

Why is Time machine backup not working after Mavericks upgrade?

Why is Time machine backup not working after Mavericks upgrade?

I had the same problem due to the Fire Wire port. Apple tested it told me it is OK!, I tried a new cable, and have tested both ports on my back up device. I find it strange that as soon as I installed Mavericks. The drive does work using USB. It could be a coincidence, I don't absolutely know at this point, my back up drive ports could stop working, but I doubt it!

Time Machine will NOT work with Airport Disks!

It looks like Time Machine will not work with Airport Disks after all. All references to Airport have been removed from the Time Machine page:
http://www.apple.com/macosx/features/timemachine.html
It also specifically says: "You can designate just about any HFS+ formatted FireWire or USB drive connected to a Mac as a Time Machine backup drive. Time Machine can also back up to another Mac running Leopard with Personal File Sharing, Leopard Server, or Xsan storage devices."
Surely, they would have included the Airport Extreme Base Station in this list if it was supported.
I really hope there will be another firmware update for the AEBS which will bring compatibility with Time Machine, because Time Machine was the only reason for me to buy an AEBS. (I only use it as a small backup server, I don't even have wireless networking enabled. There were other solutions, e.g. from Synology, which are faster and more reliable than AEBS disk sharing, but Synology stated their network drives would not be compatible with Time Machine.)

Here's how you can potentially use your AirDisk with TimeMachine (beware that YMMV), but it should work as it works with every other "unsupported" device.
1) Mount your AirDisk so it appears on your Mac
2) Open Terminal.app
3) change directories to the AirDisk's root folder located in "/Volumes"
ie: cd "/Volumes/AirDisk Name"
4) execute this command to "bless" the drive to be used with time machine:
touch .com.apple.timemachine.supported
5) Start TimeMachine and if all went well, it should recognize your AirDisk drive and use it for TM.
This should also work on NFS shares, SMB shares, AFP shares, basically anything. It has worked up until the last developer seed, so unless they yanked this at the last minute, it should still work.
Now, the reason why Apple removed this feature may be due to the unreliability of the AirDisk, so be cautious.

Facetime will not work after upgrade to io6 can anybody advise?

Facetime will not connect after upgrade to IO6 can anyone advise?

Hey there,
Maybe start here
[Troubleshooting Automatic Software Update in Mac OS X|http://support.apple.com/kb/HT1569].
Otherwise, try deleting this file. com.apple.SoftwareUpdate.plist located at /Users/YourName/Library/Preferences. Drag that .plist file from the Preferences folder to the Trash, empty the Trash and restart your Mac.
Have you tried resetting your widgets by hitting Command-R? If that doesn't, work trying trashing the two dashboard preference files.
The two dashboard preference files are in the following directory:
yourusername -> Library -> Preferences ->
The file names are:
com.apple.dashboard.client.plist
com.apple.dashboard.plist
Hope this helps.
B-rock

Time Machine has not worked since upgrade to Lion

Hello,
I've noticed that my Mac Mini's Time Machine will no longer perform a backup - I keep receiving a "could not create the backup folder" error message. This problem only started after I upgraded my Mac Mini (2010 Model) to Lion, Time Machine had worked perfectly when I use to use Snow Leopard. I have both formatted and partitioned my Time Machine drives (the first drive was a Seagate Barracuda 7,200 RPM 1TB drive, the 2nd drive is a 2TB Porsche Drive I bought at my local Apple Store). Both drives, when I was partitioning them, were set to use the GUID Partition Scheme. The Seagate Drive is an Internal Hard Drive that is sitting in a ThermalTake 2-Bay Drive Dock which is connected by a USB Cord, the Porsche drive is an External Drive that is connected via a USB cord. I have also tried unmounting/remounting each drive, deleting the Time Machine "plist" file from my Library folder and restarting, and finally re-installing Lion from the recovery drive I made using the instructions on support.apple.com. Unfortunately, nothing I've done so far has solved the issue.
I checked my Console log for Time Machine and this is what I found:
Initial Time Machine Backup
9/16/11 1:24:03.918 AM com.apple.backupd: Backing up to: /Volumes/Backup/Backups.backupdb
9/16/11 1:24:07.255 AM postfix/master: master exit time has arrived
9/16/11 1:24:07.277 AM postfix/master: daemon started -- version 2.8.3, configuration /etc/postfix
9/16/11 1:24:07.000 AM kernel: nstat_lookup_entry failed: 2
9/16/11 1:24:13.344 AM com.apple.backupd: 571.1 MB required (including padding), 1.70 TB available
9/16/11 1:24:19.677 AM com.apple.backupd: Copied 1601 files (10.3 MB) from volume Macintosh HD.
9/16/11 1:24:19.765 AM com.apple.backupd: 558.7 MB required (including padding), 1.70 TB available
9/16/11 1:24:20.346 AM com.apple.backupd: Copied 100 files (93 bytes) from volume Macintosh HD.
9/16/11 1:24:20.413 AM mds: (Error) Volume: Could not find requested backup type:2 for volume
9/16/11 1:24:20.427 AM com.apple.backupd: Starting post-backup thinning
9/16/11 1:24:20.427 AM com.apple.backupd: No post-back up thinning needed: no expired backups exist
9/16/11 1:24:20.442 AM com.apple.backupd: Backup completed successfully.
Second Backup (1 Hour Later)
9/16/11 2:24:05.102 AM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Backup/Backups.backupdb/Abraham size:37
9/16/11 2:24:08.685 AM postfix/master: master exit time has arrived
9/16/11 2:24:08.726 AM postfix/master: daemon started -- version 2.8.3, configuration /etc/postfix
9/16/11 2:24:09.000 AM kernel: nstat_lookup_entry failed: 2
9/16/11 2:24:15.143 AM com.apple.backupd: Backup failed with error: 2
Being a relatively new Mac User (I only knew about the above "fixes" after doing several Google Searches) I have no idea what the Console Log is trying to tell me or how to fix whatever is being referred to. I will be very grateful for any assistance that can be offerred.

I installed, and ran, the Time Machine Buddy Widgit and it displayed this message:
Starting standard backup
Backing up to: /Volumes/Backup/Backups.backupdb
Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Backup/Backups.backupdb/Abraham size:37
Backup failed with error: 2

Time Machine will not backup after Snow Leopard.

Pertinent information:
Macbook Pro pre-aluminum body
Time Machine backing up over network to a ppc mini with 500 gb external drive.
This worked fine with Leopard for over a year. I installed Snow Leopard last week and this is the first time I got a chance to try a Time Machine backup. Doesn't see to want to backup no matter what I do.
I tried:
- Renaming the sparsebundle
- Disconnecting/reconnecting the external drive.
- Re-selecting disk in Time Machine config and nothing works.
- Even ran Verify Disk and Repair Disk on the external drive. Found a header error, but Disk Utility said it was minor and fixed it.
It seems that Time Machine isn't even trying to figure out what needs to be backed up. Here is the log. Below this snippet of the log I will post some of the other things I see...
09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Starting standard backup
09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Attempting to mount network destination using URL: afp://[email protected]/Backup
09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Mounted network destination using URL: afp://[email protected]/Backup
09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Warning: Destination /Volumes/Backup does not support TM Lock Stealing
09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Warning: Destination /Volumes/Backup does not support Server Reply Cache
09/12/2009 - 7:01PM Sep 12 2009 7:01:33 PM com.apple.backupd[5688] Disk image /Volumes/Backup/mbphome_001ec2038641.sparsebundle mounted at: /Volumes/Backup of mbphome
09/12/2009 - 7:01PM Sep 12 2009 7:01:34 PM com.apple.backupd[5688] Backing up to: /Volumes/Backup of mbphome/Backups.backupdb
09/12/2009 - 7:01PM Sep 12 2009 7:01:36 PM com.apple.backupd[5688] Event store UUIDs don't match for volume: Macintosh HD
09/12/2009 - 7:01PM Sep 12 2009 7:01:38 PM com.apple.backupd[5688] Node requires deep traversal:/ reason:must scan subdirs|new event db|
09/12/2009 - 7:01PM Sep 12 2009 7:01:47 PM com.apple.backupd[5688] Stopping backupd to allow ejection of backup destination disk!
09/12/2009 - 7:01PM Sep 12 2009 7:01:47 PM com.apple.backupd[5688] Backup canceled.
09/12/2009 - 7:01PM Sep 12 2009 7:01:47 PM com.apple.backupd[5688] Failed to eject volume (null) (FSVolumeRefNum: -138; status: -36; dissenting pid: -1)
09/12/2009 - 7:01PM Sep 12 2009 7:01:48 PM com.apple.backupd[5688] Ejected Time Machine network volume.
Notice the:
Destination /Volumes/Backup does not support TM Lock Stealing
and:
Destination /Volumes/Backup does not support Server Reply Cache
Does anybody know what that means?
I also see this maybe every third time I try a manual backup. There are many more lines, I'll post a few for you to get the gist:
09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-08-16-173353
09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-08-20-192750
09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-08-27-220252
09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-09-09-013744
Can't really find any info on any of these errors. I search through discussions and it doesn't seem that anybody is having the same problems as I'm having, seems they are having different problems.
Thanks in advance for any kind of information you can provide on this problem.

Unfortunately a "full reset" didn't do it. The log looks almost exactly the same...
09/12/2009 - 11:26PM Sep 12 2009 11:26:47 PM com.apple.backupd[1141] Starting standard backup
09/12/2009 - 11:26PM Sep 12 2009 11:26:47 PM com.apple.backupd[1141] Attempting to mount network destination using URL: afp://[email protected]/Backup
09/12/2009 - 11:26PM Sep 12 2009 11:26:48 PM com.apple.backupd[1141] Mounted network destination using URL: afp://[email protected]/Backup
09/12/2009 - 11:26PM Sep 12 2009 11:26:48 PM com.apple.backupd[1141] Warning: Destination /Volumes/Backup-1 does not support TM Lock Stealing
09/12/2009 - 11:26PM Sep 12 2009 11:26:48 PM com.apple.backupd[1141] Warning: Destination /Volumes/Backup-1 does not support Server Reply Cache
09/12/2009 - 11:26PM Sep 12 2009 11:26:50 PM com.apple.backupd[1141] Disk image /Volumes/Backup-1/mbphome_001ec2038641.sparsebundle mounted at: /Volumes/Backup of mbphome
09/12/2009 - 11:26PM Sep 12 2009 11:26:50 PM com.apple.backupd[1141] Backing up to: /Volumes/Backup of mbphome/Backups.backupdb
09/12/2009 - 11:26PM Sep 12 2009 11:26:52 PM com.apple.backupd[1141] Event store UUIDs don't match for volume: Macintosh HD
09/12/2009 - 11:26PM Sep 12 2009 11:26:54 PM com.apple.backupd[1141] Stopping backupd to allow ejection of backup destination disk!
09/12/2009 - 11:26PM Sep 12 2009 11:26:54 PM com.apple.backupd[1141] Node requires deep traversal:/ reason:must scan subdirs|new event db|
09/12/2009 - 11:26PM Sep 12 2009 11:26:54 PM com.apple.backupd[1141] Backup canceled.
09/12/2009 - 11:26PM Sep 12 2009 11:26:55 PM com.apple.backupd[1141] Ejected Time Machine disk image.
09/12/2009 - 11:26PM Sep 12 2009 11:26:55 PM com.apple.backupd[1141] Ejected Time Machine network volume.
Still confused over the "does not support TM Lock Stealing" and "does not support Server Reply Cache"? Are those the possible causes? I'm really at a loss cause like I said in my reply before, Time Machine just always worked.

Im using a network drive with time machine and im getting error 45. Time machine will not work now. Why?

I bought a seagate goflex home 2TB network drive. It worked with time machine for a couple of weeks than now it wont. It just says ERROR 45 now and will not back up. Why?

Welcome to Apple Support Communities.
According to several related Time Machine Error 45 threads in these forums, Time Machine is not well suited to backups on most non-Apple network drives.
https://discussions.apple.com/message/10744727#10744727
https://discussions.apple.com/message/15643759#15643759
https://discussions.apple.com/message/11929252#11929252
https://discussions.apple.com/message/13164522#13164522
One of the discussions provides an off-site link to these suggestions:
http://web.me.com/pondini/Time_Machine/Troubleshooting.html

My HP LaserJet 1536 Scanner will not work after upgrading to Windows 10

I just upgraded to Windows 10, and now the scanner will not work, although I can still print. I downloaded the latest driver, but this does not seem to help. The error message I get states that scanner communication cannot be established. Please let me know if you have any suggestions. Thanks!

Greetings , I saw your post regarding the problems you are having with scanning after upgrading to windows 10.
I would start with the simple, have you tried just restarting the computer? Have you made sure your computer has all of it's windows updates? How can I tell if my computer is up to date? Most products do have updated software available for Windows 10, did you install the correct driver?HP LaserJet Full Feature Software and Driver I've also seen a few posts that say the Windows 8.1 driver will work for Windows 10 as well, so you could try that too.  HP provides a free tool called HP Print and Scan Doctor to diagnose and resolve printing and scanning problems. I recommend downloading and running the HP Print and Scan Doctor, if it doesn't fix it automatically let me know what errors or messages you receive.  Do you know if you are able to scan using Paint? To Scan from Paint: HP Multifunction Printers - How to Scan: Windows 8
(It's the same for Windows 10, from what I've been told)Right-click the Start button () in the lower left corner of the screen, click Search, and then type ...Click Paint in the results.Click File, and then click From scanner or camera.Select your printer, click OK, and then click Scan.  Have you tried just using the New Scanner app in Windows 10? It's the same as the one for Windows 8. Here are some resources;New Scanner app in Windows 10Scan app for Windows: FAQ
And a Video link...    Please let me know if any of these steps resolved your issue, or if there is anything else I can do to help.  I look forward to hearing from you!  Thanks,

External drive, Time machine don't work after upgrade

On Wed, Feb. 1 I connected my external drive, did a back-up on Time Machine, everything was fine. Then I download the most recent update for my MacBook Pro, OS X Lion 10.7.3 On Saturday, Feb. 4, I again connected my external drive to back-up and the icon for the external drive never showed up on the desktop and Time Machine did not automatically start. This morning I put this question out there and it was suggested that I reinstall OS X Lion 10.7.3 (Client Combo), which is what I did tonight when I got home. It didn't work. The external drive is running, I clicked on Time Machine in the utilities and it says it is backing up now, but the external drive still is not on the desk top and I have at least two years of back up documents and thousands of photos stored there. The external drive holds 1 terrabyte and I am very sure it is not full. Time Machine is not reading all the other back-ups I have done over the past year or so.
Please any other suggestions?

Others here wouldnt recommend it, but on a new OS install, since I have a giant pile of HD, ...i just grab another HD and create a new fresh Time Machine backup
after its complete, I take the original HD with the OLD backup and format/erase it.
Im a tad too lazy to wait, as you yourself mentioned, 1 hour for TM just to PREPARE to backup. Nope, no,...not gonna do it.
I updated 4 Macs to Mavericks and id rather make a wholly NEW Time Machine backup on another HD and erase the original.
Since I keep about 12+ redundant archives of my important data, I have no worry on earth of ever losing data.
Time machine is a backup, NOT an archive for vital data.
Methodology to protect your data. Backups vs. Archives. Long-term data protection

Time Machine does not work after Lion Upgrade

Hi all.
I upgraded my iMac to Lion yesterday. I used to run Time Machine through my airport extreme to an external hdd.
After the upgrade to Lion I'm unable to do this. When I try to setup Time Machine again, it is not possible to connect to the HDD throught the Airport Extreme. I do find the external HDD in Finder, but not able to access it.
The HDD is a Samsung 1 TB.
Is this a known issue and is it any possible fixes in the near future?
Thanks!

Hi
It probably doesn't help you directly but I have Lion performing time machine backups onto an external disk via airport extreme. Have you upgraded the firmware on the airport extreme recently?
Cheers
Tom

Time Machine does not work after installing mavericks

After I installed maverick on my imac, my time machine backups don't work anymore!!!!
I have a normal portable HDD attached to my Imac with time capsule backup from before mavericks was installed.
I also has a Buffalo NAS as a second Time Machine Backup.
TIme capsule does not recognise my Buffalo NAS and tells me that it is not available. It has previous backups from Mountain Lion for sure!
My portable HDD keeps saying "Preparing for backup" for eternity.
Please, APPLE, what is going on with mavericks? Regretted upgrading.
My backup is 31 days behind because of this! Unacceptable!
But what is strange is that I can connect to my portable HDD and Buffalo NAS as a drive. What I have been doing is to copy and paste the important stuff into the drives. But it really defeats the purpose of time machine, right?

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Machine authenticatiion not working after upgrade to ISE 1.2

After upgrading to ISE 1.2.0.899 patch 14 we have a problem running machine authentication for a few hosts (30 of about 3000).
Although we can see on the switch that the host presents the hostname, in ISE Operations all we get is the MAC address (for both the Identity and Endpoint ID fields).
On the switch:
show auth sessions int FastEthernet0/1
Interface: FastEthernet0/1
MAC Address: 3c97.0eed.afbc
IP Address: Unknown
User-Name: host/xxxxxxxxxx
Status: Running
Domain: UNKNOWN
Oper host mode: multi-auth
Oper control dir: both
Session timeout: N/A
Idle timeout: N/A
Common Session ID: 0AF19F16000138DC11B59C9D
Acct Session ID: 0x000292EA
Handle: 0x01000BCA
Runnable methods list:
Method State
mab Failed over
dot1x Running
In ISE we see the contents of the attached file.
The workaround we found was to move the host in a different switch, where it will authenticate, and then move it back on the initial switch where it will work now. I know it doesn't make sense but it worked...
Shut / no shut on the switch port or clearing the auth session doesn't work.
Does anybody have any idea about this problem?
Thanks in advance!
Update:
The issue seems to be related with how the policy servers cache the sessions/auth requests from the network devices. If we point the network device that hosts the problematic machines to another radius server the auth runs as expected. A number of machines have problems with a certain policy server (not always the same) while most machines authenticate correctly. The problem is that if, for whatever reason,a machine fails to auth, that policy server could "decide" to hang to that failed auth result for susequent tries.

On which switch does the reauthentication work?
Either way, it looks like you need to update the switch software:
This is from the ISE 1.2 Compatibility Matrix which can be found here:
https://supportforums.cisco.com/sites/default/files/attachments/discussion/4500.png
Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question. Otherwise, feel free to post follow-up questions.
Charles Moreton

Kodak printer will not work after upgrading to Yosemite.. Please Help

I have uninstalled and re installed my kodak 5250 more than once and it still does not work. I have carried out a clean install of my Yosemite OS and still no joy. How do i fix this?

I've got the 7250 as well -- same exact issue. I sent an e-mail to Kodak support on Friday last week -- haven't heard anything, but they did ask for 2 business days time to respond.
I've been running the Yosemite Beta on one of my machines for a few months now and my printer stopped working on that one after the upgrade. I kept Mavericks on my other Mac until this weekend, and printing still worked from that machine until I upgraded to Yosemite over the weekend.
I've got Linux and Windows virtual machines that can print to the ESP 7250, so I can still print, albeit with the hassle of firing up a VM and printing from there... I sure hope Kodak responds! I offered to help them test any beta-quality drivers they may have, so -- we'll see what they say!
I've been planning to ditch the printer and get a new one, but I'd rather not have to do it right this minute just for a driver issue :-/

Time Machine Will Not Work - Onyx Broke it and I Can't Fix It!

Background
The external drive is a western digital my book 500 GB drive(black with round button on front) connected with fire wire, with three partitions, 200/200/what ever is left. One has super duper bootable clone/time machine/extra store space. I am using about 80GB of 320GB on my internal.
I used onxy utility on my old TiBook with good results so last week I though oh let me down load that and use it on my new MBP. I run the utility and the next day notice that TM is not working(Onyx has been uninstalled and should have a big warning this will F-U TM). Try to figure it out no luck, call support the guy points out he did a search and there are a bunch of people who say onyx broke their TM. The TM buddy message was along the lines of deep traversal needed and the UUID don't match. I run disk repair and do the regular stuff still no luck.
After reviewing the trouble shooting guide above and trying some of the fixes with out results, I decide to erase the partition as I only have a few weeks of data on there and I keep a super duper backup twice a week on another partition.
Now that I am trying to start it new the problem seems to be that the backup hangs after evaluating between 1.5 and 3.5 GB it makes not further progress after hours. Example, I tried a new backup this morning its hung at 1.64GB, I will check at lunch time and it will probably still be there.
Things I have tried and reviewed
All drives internal/external formated correctly
All external drives added to spotlight privacy
Trashed time machine preference file and restarted (twice!)
Checked to see if there is a firmware update for external drive and I don't think there is
I think this is from my try this morning, I need to double check...
Time Machine Buddy Message:
Starting standard backup Backing up to: /Volumes/BackUp TM/Backups.backupdb Ownership is disabled on the backup destination volume. Enabling. Event store UUIDs don't match for volume: Macintosh HD Backup content size: 81.0 GB excluded items size: 128 KB for volume Macintosh HD No pre-backup thinning needed: 97.17 GB requested (including padding), 199.33 GB available Waiting for index to be ready (909 > 0)
My frustration level has been rising since I noticed this on Saturday and have not been able to resolve it or make any progress, your help is appreciated.
Jerome

C. Jerome wrote:
Onyx has been uninstalled and should have a big warning this will F-U TM).
No. You're jumping to conclusions. Many folks (including me) have run OnyX for a long time with no ill effects on TM.
Try to figure it out no luck, call support the guy points out he did a search and there are a bunch of people who say onyx broke their TM.
What "support guy?" There are no such posts in this forum.
The TM buddy message was along the lines of deep traversal needed and the UUID don't match. I run disk repair and do the regular stuff still no luck.
Those are completely normal in some situations, such as your first backup, and the first backup after installing an OSX update. The "deep traversal" does mean there will be a long "preparing" phase.
After reviewing the trouble shooting guide above and trying some of the fixes with out results, I decide to erase the partition
That means you will continue to get the UUID and +deep traversal+ messages, and lengthy preparing phase, until TM can complete a backup.
All drives internal/external formated correctly
Double-check this, via the instructions in item #C1 of the Troubleshooting tip. Please post the results.
All external drives added to spotlight privacy
And excluded from any anti-virus scanning?
Checked to see if there is a firmware update for external drive and I don't think there is
They have released some fairly recently, and have fixed some similar problems. It's probably worth your time to double-check to be sure.
Time Machine Buddy Message:
Starting standard backup
Backing up to: /Volumes/BackUp TM/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 81.0 GB excluded items size: 128 KB for volume Macintosh HD
No pre-backup thinning needed: 97.17 GB requested (including padding), 199.33 GB available
All normal.
Waiting for index to be ready (909 > 0)
As you see in item #D2 of the Troubleshooting tip, this can indicate a problem with the drive, or communicating with it. Have you tried all the other things in item #D2?
Also, there are some recent reports that seem to indicate a couple of other possibilities:
Reduced WIFI power when running on battery, since the 10.5.8 update. Are you running on utility power or battery power when this happens?
Some sort of conflict with Mozy version 1.4.0. So far, this appears to be related only to wireless backups, but if you're running Mozy, it might be worth investigating.
You might also want to use the Console app (in your Applications/Utilities folder) to see if there are other messages indicating a conflict with your backups.
When it starts, click +Show Log List+ in the toolbar, then navigate in the sidebar that opens up to your system.log and select it. Navigate to the +Starting standard backup+ message that you noted above, then see what follows that might indicate some sort of *error, failure, throttling respawn, termination, exit,* etc. (many of the messages there are info for developers, etc.). If in doubt post (a reasonable amount of) the log here.
Finally, how old is your disk drive? They do fail, sometimes sooner rather than later, and often exhibit just this sort of behavior.

Time machine will not work after upgrade

Similar Messages

Maybe you are looking for