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

Similar Messages

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.

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.

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!

Is the apple website not opening after installation of mountain lion?

is the apple website not opening after installation of mountain lion? because after i updated from lion, apple's webpage is like not opening from any browser..even from safari..

And other websites work? Do you mean http://apple.com, or a specific page within their website? The main page loads fine for me.

TrackPad physical click not working after upgrade to Mountain Lion

Does anybody know how to get my trackpad working again after upgrading to Mountain Lion?
I recently upgraded my MacBook (13-inch, Late 2009, Intel Core 2 Duo) from Snow Leopard to Mountain Lion. Everything seems to have gone well, except for trackpad behavior.
The primary problem is that the physical click of the trackpad is now erratic. Sometimes a physical click will work, and other times it will not work.
Note: The "tapping" of the trackpad DOES work consistently. I have confirmed that System Prefs > Trackpad > "Tap to Click" is enabled, and so tapping is not the problem. (The "tap to click" selector does exhibit a unique behavior however--if I DESELECT "tap to click," then the physical click no longer works at all. It looks like the "tap to click" selector can completely disable the physical click of the trackpad, but cannot enable the physical click completely.)
I have also checked the settings on System Prefs > Accessibility > Mouse & Trackpad, but none of those settings affect the physical click of the trackpad.
I tried zapping the PRAM, but that did not change the problem with physical clicking on the trackpad.
Grateful for any ideas...
Nertz

I ended up taking my MacBook to the Apple Genius Bar. The staff were very helpful.
The apple staff said that there is no known link between the upgrade to Mountain Lion and trackpad misbehavior. In my case, they made some hardware adjustments to the trackpad, and all is working properly again.
Bottom line: if you think that your trackpad misbehavior is related to Mountain Lion, you might want to take it to an Apple Genius Bar. If there really is no connection between Mountain Lion and trackpad behavior, then perhaps they can fix it for you (as happened to be true in my case). But if there IS a connection in some way, it would be helpful for Apple employees to see your evidence firsthand.
Best wishes to all...
Nertz

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

Time machine does not back up iPhoto in mountain lion ?

My Time Machine does not back up my iPhoto library. When I open Time Machine I get Desktop display going back to installation date.
All other applications respond correctly including Mail, Contacts, etc. My Seagate drive is not involved in the present programme of repair I have been told by Apple. Any ideas?

I'm now fixed and done (update to latest software and learn how to use it)
Thanks again Ivan for the article, it alerted me to otherwise incomprehensible changes in iPhoto/Time Machine operation such as in my case would transfer 3.8GB of data to restore a single photo, while apparently loosing all photos added after that backup time.
However the article says:
When using iPhoto ’11 (version 9.2 or later) and Time Machine with OS X Lion 10.7.2 (or later), iPhoto no longer has the Browse Backups option. This means that instead of restoring specific photos within your iPhoto Library, you must restore your entire iPhoto Library.
This may be practically true but it is technically false.
To restore a single photo in iPhoto '11 with Time Machine it goes something like this:
Start with your Time Machine hard drive and navigate many steps (including showing package contents where necessary) all the way through to the photo/date you want. Drag it to your desktop. (Do not make any edits in Time Machine!) Import to iPhoto. Click on last import in iPhoto. Right click the photo and change the event name, then look for it at the right date in iphoto with the new event name.
Hopefully those with more time and patience can check this out and see what it can do. I had to do it twice with Apple suport senior tech to get it. What a pain compared to iPhoto' 09 but at least now I can restore iPhoto library or a photo if necessary.
David

HT4798 username/password not working after upgrade to mountain lion

hello, on my imac after upgrading to mountain lion my computer password and/or username seems not to work anymore: when i want to install an update or search for updates on the app store the combination i used so far, does not work anymore. i tried to find out how to reset the computer password but without too much success, and i'm a bit confused, what can i do? thanks a lot

You went wrong at the very beginning by not erasing the hard drive of a used computer before starting to use it yourself. I suggest you do that now.
Back up all data to at least two different storage devices.
Boot into Recovery (command-R at startup), launch Disk Utility, and erase the startup volume. This operation will destroy all data on the volume, so you had be better be sure of your backups. Install OS X. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.
When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For a walkthrough, see here:
Using Setup Assistant
Don't transfer the Guest account, if it was enabled on the old system.
Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

Exchange Calendar availability not working after upgrading to Mountain Lion

After upgrading to Mountain Lion cannot longer see calendar availability on my Exchange account, before upgrading it worked ok - anyone has the same problem?

Had the same problem on 2 Macs (iMac and MBP) after downloading ML last night, could not access my Exchange calendar via iCal. Deleted the accounts from iCal, then reloaded them, now all seems to work

ISight is not working after upgrade to Mountain Lion.

Please help!
After upgrade to Mountain Lion, Skype, Photobooth and etc can't detect iSight.

I tried the SMC option for my Mac (version details below)...but this still didn't solve my problem.
Model Name:
MacBook
Model Identifier:
MacBook7,1
Processor Name:
Intel Core 2 Duo
Processor Speed:
2.4 GHz
Number of Processors:
1
Total Number of Cores:
2
L2 Cache:
3 MB
Memory:
4 GB
Bus Speed:
1.07 GHz
Boot ROM Version:
MB71.0039.B0E
SMC Version (system):
1.60f5
Sudden Motion Sensor:
State
Enabled
In fact when I check under "About this Mac ==> More Info ==> System Report ==> Hardware ==> USB"
this is what I see:
-> USB Bus
      -> BRCM2070 Hub
             Bluetooth Host USB Controller
          Apple Internal Keyboard/Trackpad
      -> USB Bus
      -> USB High-speed Bus
      -> USB High-speed Bus
I find it hard to beleieve that the OSX Mountain Lion upgrade (from OSX Lion) can conk the camera hardware. All softwares such as Skype, Facetime, Image Capture show "No camera detected" after the OSX Mountain Lion upgrade. All of these were working perfectly fine before the upgrade.
Any help in this regard would be highly appreciated.
Regards,
Vishy

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 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.

Time machine will not backup after maverick

This is a major problem, not addressed in the installation instrucitons. The disk runs eternally "preparing backup", I mean all night.
This happened to two machines on entirely separate backup disks. And if we are sacraficing the old data in reformating the drive, I would like to know about that before choosing to upgrade.

Update: Finally...
At least for the Promise Pegasus R4... but I noticed on other threads that WD drives are also acting up too so this might work with them too.
I turned off Time Machine, and deleted that pesky .plist file, again. I unplugged the R4, power and thunderbolt, then played whack the gopher with the drives swapping them around randomly. I reintalled Mavericks from a fresh download, yet again, then set Time Machine to backup on a fast USB 3TB drive (which it did in 6 hours or so). Then I turned off Time Machine, deleleted that .plist file again, rebooted the iMac, plugged in the R4, reformatted it again with Disk Utility, then hooked it to Time Machine, said a few slightly heretic prayers to whatever demons came with Maverick, and 2 minutes later Time Machine started to backup and report 1 hour to complete... the hour isn't up yet, but I'm crossing everything I have 2 of...
I've noticed a few other 'didn't copy over or mesh well' things with Maverick, but that's a different thread and 2 updates from now once we all suffer through this extended beta-test by Apple.
John Galt posted this on another thread... to find and delete that pesky .plist file:
or "error ... while creating the backup folder."
and follow that to:
http://pondini.org/TM/A4.html

Time Machine will not work after installation of Mountain Lion

Similar Messages

Maybe you are looking for