Why is time machine running slow?

I am suddendly experiencing problems with Time Machine. Time Machine seems to run very slow lately. Is there any reason for this? The disk I use is fine.

Similar Messages

Why does ext HDD / time machine run slow?

Apologies if this is answered else where, but I can't find any answers.
I have a MBP running OSX 10.6.8. Connected to it as a Time Machine is a Freecom 400GB 28147 uk, external hardrive connected over USB 2.0. I also have a Mac Mini running 10.6.8.
When connected to my MBP, I have found that it is extremely slow to read files. I gave up using it for Time Machine a while ago as I thought there was a problem Time Machine software causing it to run slow. I have also tried to read the time machine backups through finder and they are still slow to read.
Today (don't know why i didn't do it before now) I plugged it in to my Mac Mini with USB 2.0 and found that I can read all the time machine files at lightning speed, far quicker than my MBP which can take 2-3 mins to open a folder. I have noticed that the hard drive doesn't make its usual whurring noise when im trying to open a folder using the MBP, right up until the last minute before the folder opens.
Does any one have any idea about what might be causing the problem when the the ext HDD is connected to my MBP?
Any thoughts or suggestions greatly appreciated.

larryfromjackson wrote:
I'm backing up to a Drobo with four 2-Gig drives.
How are you connected to it? Network problems could explain at least some of what you're seeing.
More often then not I don't know how long the backups take because when it becomes to annoying I stop the backup.
That guarantees that Time Machine will have to do a "deep scan" the next time, comparing everything on your system to the backups. That does take a while, but if there are no other problems shouldn't have a major impact on performance.
All of that said, I can't say for certain that there isn't something else going on. Generally the way I notice the slowdown is when my keyboard inputs come out screwy -- ingB instead of Bring, pplAication for Applicaton for example. When I know that this is happening I can work "around" it by typing the first letter, pausing for a second or two, then typing the remander. Does any of this ring an bells?
I've not heard of that specifically, but if you're connected to the Drobo wirelessly, and using a Bluetooth keyboard, there are reports of interference between the two. Try a wired keyboard temporarily, and/or different WIFI channels.

Time machine running slow and slowing network access

I have had and continue to have issues with wifi on my MBP. Those are pretty well summarized in https://discussions.apple.com/thread/5535320?start=30&tstart=0. I've been able to make mt system usable with some of the less dodgy workarounds in that thread ( like keeping a ping on my router running )
That thread really doesn't mention the issues I've been having with time machine though, so I thought I'd bring this up here. Whenever time machine starts up, Safari and mail become unresponsive. It's worst when TM is "preparing" of "cleaningup", though barely usable during the actual backup. Mostly, I can work around that too, but occationally, TM will find GB of data to be backed up and lock up my mac for a day. Here's a recent example:
2/16/14 12:30:27.952 PM com.apple.backupd[11557]: Starting automatic backup
2/16/14 12:30:28.466 PM com.apple.backupd[11557]: Attempting to mount network destination URL: afp://;AUTH=No%20User%20Authent@MyBookLive._afpovertcp._tcp.local/TimeMachine
2/16/14 12:30:33.866 PM com.apple.backupd[11557]: Mounted network destination at mount point: /Volumes/TimeMachine using URL: afp://;AUTH=No%20User%20Authent@MyBookLive._afpovertcp._tcp.local/TimeMachine
2/16/14 12:31:44.678 PM com.apple.backupd[11557]: Disk image /Volumes/TimeMachine/sparky.sparsebundle mounted at: /Volumes/Time Machine Backups
2/16/14 12:31:46.613 PM com.apple.backupd[11557]: Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
2/16/14 12:34:07.904 PM com.apple.backupd[11557]: Will copy (1.66 GB) from Macintosh HD
2/16/14 12:34:08.004 PM com.apple.backupd[11557]: Found 83487 files (1.66 GB) needing backup
2/16/14 12:34:08.738 PM com.apple.backupd[11557]: 4.16 GB required (including padding), 445.21 GB available
2/16/14 1:32:33.579 PM com.apple.backupd[11557]: Copied 534.6 MB of 1.66 GB, 28317 of 83487 items
2/16/14 2:40:02.513 PM com.apple.backupd[11557]: Copied 564.1 MB of 1.66 GB, 30225 of 83487 items
2/16/14 3:46:20.853 PM com.apple.backupd[11557]: Copied 593.2 MB of 1.66 GB, 31631 of 83487 items
2/16/14 4:48:19.461 PM com.apple.backupd[11557]: Copied 621.8 MB of 1.66 GB, 33182 of 83487 items
2/16/14 5:00:31.968 PM com.apple.backupd[11557]: Bulk setting Spotlight attributes failed.
2/16/14 5:54:51.036 PM com.apple.backupd[11557]: Copied 658 MB of 1.66 GB, 34773 of 83487 items
2/16/14 6:17:20.839 PM com.apple.backupd[11557]: Bulk setting Spotlight attributes failed.
2/16/14 6:56:27.566 PM com.apple.backupd[11557]: Copied 688.2 MB of 1.66 GB, 36246 of 83487 items
2/16/14 7:57:07.076 PM com.apple.backupd[11557]: Copied 704.8 MB of 1.66 GB, 37267 of 83487 items
2/16/14 8:58:52.469 PM com.apple.backupd[11557]: Copied 730.7 MB of 1.66 GB, 38724 of 83487 items
2/16/14 10:09:42.807 PM com.apple.backupd[11557]: Copied 760.5 MB of 1.66 GB, 40291 of 83487 items
2/16/14 11:21:25.825 PM com.apple.backupd[11557]: Copied 803.8 MB of 1.66 GB, 42462 of 83487 items
2/17/14 12:30:58.322 AM com.apple.backupd[11557]: Copied 834.1 MB of 1.66 GB, 43513 of 83487 items
2/17/14 1:45:28.495 AM com.apple.backupd[11557]: Copied 846.1 MB of 1.66 GB, 44160 of 83487 items
2/17/14 2:45:36.010 AM com.apple.backupd[11557]: Copied 868.6 MB of 1.66 GB, 45485 of 83487 items
2/17/14 3:57:29.939 AM com.apple.backupd[11557]: Copied 890.6 MB of 1.66 GB, 46729 of 83487 items
2/17/14 5:07:30.971 AM com.apple.backupd[11557]: Copied 926.7 MB of 1.66 GB, 48695 of 83487 items
2/17/14 6:15:49.283 AM com.apple.backupd[11557]: Copied 963.7 MB of 1.66 GB, 50583 of 83487 items
This is on an AC router. My peak throughput shows 19 Mb/s on menu meters, so, not great, but not this slow. Mostly, the network activity is nothing with short bursts of higher throughput.
I'm hoping this will be addressed in 10.9.2. In the mean time, are there any workarounds to get past this issue short of turning off TM?
Thanks,
Horst

These instructions were taken from Mac OS X Hints at:
http://hints.macworld.com/article.php?story=20050302225659382
The Unix program dd is a disk copying util that you can use at the command line in order to make a disk image. It makes a bit-by-bit copy of the drive it's copying, caring nothing about filesystem type, files, or anything else. It's a great way to workaround the need for Norton Ghost.
Normally, in order to make a disk image, the disk you're copying from has to be able to spin up and talk -- in other words, it's OK to make a copy if the disk is healthy. But what happens when your disk is becoming a doorstop? As long as it continues to spin, even with physical damage on the drive, dd and Mac OS X will get you out of the fire.
We had a situation recently where a friend sent a disk to us that had hard physical errors on it. It would boot in Windows, but then it would hit one of these scratch marks and just die. We fired up dd, and it started OK, but stopped at the same physical error location -- complaining about a Hard Error.
So the workaround was to designate the dd mode as noerror -- which just slides over the hard stops, and to add the mode sync, which fills the image with nulls at that point. We did it on BSD Unix, but as long as you can get the hard drive attached to your Mac, the command is the same:
dd bs=512 if=/dev/rXX# of=/some_dir/foo.dmg conv=noerror,sync
The bs=512 designates block size, and the if=/dev/rXX# is the UNIX path to the actual disk device. Make sure that the chosen directory (some_dir) has enough room to take the entire disk image -- which will be equal to the size of the drive. Since dd doesn't care about the contents of the drive, it copies every bit on the thing, so you get an image equal to the disk's capacity. A really big file. One workaround is to put it on a RAID array.
Once you've established the disk image (in this example, foo.dmg), you're almost home. Here's where your Mac OS X box is far and away the best thing to have. In this example, the dd output file is foo.dmg. You have to realize that this is an exact copy of a busted drive, but the "holes" are filled with nulls. As long as the damage isn't to the boot sector, though, when you double-click on it, Mac OS X mounts it without breathing hard ... who cares if it's FAT32, NTFS, whatever.
Due to the size of the image that we were copying, we put it on a RAID array, and had to access the image over the network -- it still mounted fine. In straight UNIX, if you try to mount a disk image, it complains that there is "no block device" and fails. Once your image is mounted, it appears in your Finder, and then it's easy work to retrieve the critical files from the image -- usually things like .doc files and .xls files and the lot.
Finally, since your disk is actually dying, once you have your image, you can drop it to tape or something and you've not only recovered your files, you've made a viable backup as well. Once again, that which destroys a Windows box becomes a play thing to a Mac OS X box.

Time machine running slow

Not sure why my wireless setting are set up high connections.What happens if I put something into the wan port?

Ok, so I have had another play this morning. I have plugged the Mac into the router connecting at 100Mbps. I then added a file around 4GB to the Mac. I first transferred this to the WD drive which transferred at 95Mbps average continuously until the file was transferred. This tells me there is not issue with my network and equipment.
Secondly I started a time machine backup and it picked up this file as needing backing up. The transfer started quite quickly which was good compared to yesterday. It was a little choppy on the through put but was reaching peaks of 95Mbps. Great. I am just putting the choppy down to time machine copying and sorting or something of that sort.
Oh dear. 1GB transfered and the backup suddenly goes slow again without warning again. Then later on, a lot later, it speeds up again. I am seriously looking at my router as the problem here but require to swap it out to test it. It just seems so strange that it is up and down like this. Oh, and right now (while writing this) it is back at 72Kbps peak. This makes no sense that Time Machine itself would keep changing the transfer rates so dramatically.
Regards,
Adam.

Why is time machine so slow?

My time machine is so slow and allways back up every thing again, not only the new files or changes.

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.
Select "system.log" from the file list. Enter "backupd" (without the quotes) in the String Matching text field. Post the messages from the last backup, beginning with "Starting standard backup."
Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Do not post many repetitions of the same message.
Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

Why does Time Machine run continually?

I moved from Snow Leopard to Lion last week, and also converted my MobileMe account to iCloud. It has now been seven days and Time Machine appears to have never stopped backing up. To be more precise, it appears that as soon as it completes one back up, it immediately starts on a new one. My Time Machine drive is an external 750 GB connected by FW800. Time Machine estimates the size of a full backup at 132.66 GB. The Bootcamp partition on my 320 GB internal drive and the external Time Machine drive are excluded from the backups. Looking at the Star Wars screen in Time Machine shows that it has made two backups per day since the move, so I don't think it is still making the initial full back up due to the OS upgrade.
Is this normal? If not, what may be causing Time Machine to run continually? It did not behave in this way with Snow Leopard and previous versions of OS X.
Thanks for any advice.

Hi, and welcome to the forums.
It sounds like you may have either or both of the following:
Your backups are too large. Something is being backed-up often, or every time, that is taking a lot of time and disk space. See #D4 in the Time Machine - Troubleshooting *User Tip* at the top of this forum.
Your backups are running too slowly, for one or more reasons. See #D2 in the Troubleshooting Tip.

Why is my Time Machine running so slow?

I am curious why my Time Machine backup is running so slow. I am trying to backup 52.85 GB. I am currently at 17.65 GB and it has taken about 6 hours. The Time Machine "meter" that shows how long it is going to take to finish the backup is telling me it estimates about 14 hours. Thirty minutes it was telling me it was going to take about 12 hours. Now 14? What's the deal? It seems to me the backup is taking way too long. What is puzzling was that the first 15 GBs or so were prett fast. You could actually see the download happening. Now it seems like the meter is stuck and not moving. Inerimittently, the meter will change the number of files yet to be backed up. Can anyone shed some light as to what might be happening.
Thanks!
Edward

I've followed many of the suggestions on this thread (except upgrading to Mountain Lion). My Time Machine and computer has been going for eight days straight backing up 580 gigs and last night there were 30 gigs to go! Something happened and in the middle of the night the computer crashed. I restarted the computer and external harddrive that I use for my Time Machine this morning and continued the backing up of 35.24 gigs. Except now the status window tells me it will take 9,624 days to back up!
I ran the diagnostic command prompt:
sudo tmdiagnose
And here are some of the results (I did not include the lines that identify my computer name and self-identifying info; also a zip file was generated by I did not include it because it is almost 3 megs):
2013-11-09 09:27:43.038 tmdiagnose[864:2303] Executing '/usr/bin/fs_usage -w'...
2013-11-09 09:27:53.069 tmdiagnose[864:2303] Executing '/usr/bin/top -l 10'...
2013-11-09 09:28:04.859 tmdiagnose[864:2303] Sampling 'backupd'...
2013-11-09 09:28:11.385 tmdiagnose[864:2303] Sampling 'mtmd'...
2013-11-09 09:28:11.451 tmdiagnose[864:2303] Sampling 'mtmfs'...
2013-11-09 09:28:11.517 tmdiagnose[864:2303] Sampling 'Finder'...
2013-11-09 09:28:20.769 tmdiagnose[864:2303] Executing '/bin/ls -la /Volumes/'...
2013-11-09 09:28:20.898 tmdiagnose[864:2303] Executing '/bin/df -H'...
2013-11-09 09:28:20.964 tmdiagnose[864:2303] Executing '/sbin/mount'...
2013-11-09 09:28:21.030 tmdiagnose[864:2303] Executing '/usr/sbin/diskutil list'...
2013-11-09 09:28:21.288 tmdiagnose[864:2303] Executing '/usr/sbin/diskutil cs list'...
2013-11-09 09:28:21.354 tmdiagnose[864:2303] Executing '/bin/bash -c /usr/sbin/diskutil list | /usr/bin/awk '/disk/ {system("/usr/sbin/diskutil info "$NF); print "*********************"}''...
2013-11-09 09:28:29.019 tmdiagnose[864:2303] Executing '/usr/bin/hdiutil info'...
2013-11-09 09:28:29.284 tmdiagnose[864:2303] Executing '/usr/sbin/netstat -aW -p tcp'...
2013-11-09 09:28:47.321 tmdiagnose[864:2303] Executing '/bin/bash -c /bin/ps auxc | /usr/bin/awk '/mtmd/ {system("lsof -p "$2); print("\n\n")}''...
2013-11-09 09:28:47.478 tmdiagnose[864:2303] Executing '/bin/bash -c /bin/ps auxc | /usr/bin/awk '/mtmfs/ {system("lsof -p "$2); print("\n\n")}''...
2013-11-09 09:28:47.570 tmdiagnose[864:2303] Executing '/usr/sbin/ioreg -ls -w 0'...
2013-11-09 09:28:56.096 tmdiagnose[864:2303] Gathering system diagnostic logs for 'backupd'...
2013-11-09 09:28:56.103 tmdiagnose[864:2303] Gathering system diagnostic logs for 'mtmd'...
2013-11-09 09:28:56.104 tmdiagnose[864:2303] Gathering system diagnostic logs for 'mtmfs'...
2013-11-09 09:28:56.105 tmdiagnose[864:2303] Gathering system diagnostic logs for 'mds'...
2013-11-09 09:28:56.111 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Locum'...
2013-11-09 09:28:56.112 tmdiagnose[864:2303] Gathering system diagnostic logs for 'diskimages-helper'...
2013-11-09 09:28:56.113 tmdiagnose[864:2303] Gathering system diagnostic logs for 'newfs_hfs'...
2013-11-09 09:28:56.114 tmdiagnose[864:2303] Gathering system diagnostic logs for 'NetAuthSysAgent'...
2013-11-09 09:28:56.115 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Finder'...
2013-11-09 09:28:56.116 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Locum'...
2013-11-09 09:28:56.117 tmdiagnose[864:2303] Gathering system diagnostic logs for 'System Preferences'...
2013-11-09 09:28:56.126 tmdiagnose[864:2303] Gathering system diagnostic logs for 'SystemUIServer'...
2013-11-09 09:28:56.127 tmdiagnose[864:2303] Gathering system diagnostic logs for 'iPhoto'...
2013-11-09 09:28:56.128 tmdiagnose[864:2303] Gathering system diagnostic logs for 'MailTimeMachineHelper'...
2013-11-09 09:28:56.129 tmdiagnose[864:2303] Gathering system diagnostic logs for 'Address Book'...
2013-11-09 09:28:56.130 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'Finder'...
2013-11-09 09:28:56.294 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'Locum'...
2013-11-09 09:28:56.318 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'System Preferences'...
2013-11-09 09:28:56.343 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'SystemUIServer'...
2013-11-09 09:28:56.366 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'iPhoto'...
2013-11-09 09:28:56.391 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'MailTimeMachineHelper'...
2013-11-09 09:28:56.416 tmdiagnose[864:2303] Gathering recent user diagnostic logs for 'Address Book'...
2013-11-09 09:28:58.687 tmdiagnose[864:4303] Executing '/usr/sbin/system_profiler -xml SPParallelATADataType SPAirPortDataType SPBluetoothDataType SPDiagnosticsDataType SPEthernetDataType SPFibreChannelDataType SPFireWireDataType SPFirewallDataType SPHardwareDataType SPHardwareRAIDDataType SPNetworkLocationDataType SPManagedClientDataType SPMemoryDataType SPNetworkDataType SPPowerDataType SPSerialATADataType SPSoftwareDataType SPUSBDataType'...
2013-11-09 09:29:14.646 tmdiagnose[864:4303] Gathering host information...
2013-11-09 09:29:14.649 tmdiagnose[864:4303] Getting Time Machine configuration...
2013-11-09 09:29:14.984 tmdiagnose[864:4303] Executing '/bin/bash -c /bin/launchctl list | /usr/bin/grep -e 'PID' -e 'com.apple.mtm' -e 'com.apple.backup' -e 'com.apple.TMLaunchAgent''...
2013-11-09 09:29:15.052 tmdiagnose[864:2303] Making backup disk available...
2013-11-09 09:29:15.086 tmdiagnose[864:4303] Building classic Time Machine snapshot skeletons...
2013-11-09 09:29:16.675 tmdiagnose[864:4303] Executing '/bin/ls -lde /Volumes/TimeMachine/Backups.backupdb/.spotlight_repair'...
2013-11-09 09:29:16.741 tmdiagnose[864:4303] Executing '/usr/bin/xattr -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_repair'...
2013-11-09 09:29:17.523 tmdiagnose[864:4303] Executing '/bin/ls -lde /Volumes/TimeMachine/Backups.backupdb/.spotlight_temp'...
2013-11-09 09:29:17.589 tmdiagnose[864:4303] Executing '/usr/bin/xattr -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_temp'...
013-11-09 09:29:17.788 tmdiagnose[864:4303] Executing '/bin/ls -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_repair'...
2013-11-09 09:29:18.614 tmdiagnose[864:4303] Executing '/bin/ls -l /Volumes/TimeMachine/Backups.backupdb/.spotlight_temp'...
2013-11-09 09:29:19.392 tmdiagnose[864:4303] Building Mobile Time Machine overlay snapshot skeletons...
2013-11-09 09:29:19.393 tmdiagnose[864:4303] Building Mobile Time Machine delta store snapshot skeletons...
2013-11-09 09:29:19.505 tmdiagnose[864:2303] Gathering information about reachable AirPort devices...
2013-11-09 09:29:49.509 tmdiagnose[864:2303] unable to locate any Bonjour services within 30 seconds
2013-11-09 09:29:49.540 tmdiagnose[864:2303] Executing '/usr/bin/mddiagnose -h'...
2013-11-09 09:29:49.708 mddiagnose[974:707] Executing '/usr/bin/sw_vers'...
2013-11-09 09:29:49.776 mddiagnose[974:707] Getting system version...
2013-11-09 09:29:49.778 mddiagnose[974:707] Executing '/usr/bin/arch'...
2013-11-09 09:29:49.865 mddiagnose[974:707] Executing '/usr/bin/what /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mds'...
2013-11-09 09:29:49.866 mddiagnose[974:707] Executing '/usr/bin/what /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Metadata'...
2013-11-09 09:29:49.867 mddiagnose[974:707] Executing '/usr/bin/top -l 2 -s 2'...
2013-11-09 09:29:54.050 mddiagnose[974:707] Executing '/bin/df -H'...
2013-11-09 09:29:54.117 mddiagnose[974:707] Executing '/bin/ls -la /Volumes/'...
2013-11-09 09:29:54.184 mddiagnose[974:707] Executing '/sbin/mount'...
2013-11-09 09:29:54.251 mddiagnose[974:707] Executing '/usr/bin/vmmap -resident -w mds'...
2013-11-09 09:29:54.761 mddiagnose[974:707] Executing '/usr/bin/heap mds'...
2013-11-09 09:29:55.018 mddiagnose[974:707] Executing '/usr/local/bin/ddt mds'...
2013-11-09 09:29:55.166 mddiagnose[974:707] Sampling 'mds'...
2013-11-09 09:30:01.114 mddiagnose[974:707] Spindumping 'mds'...
2013-11-09 09:30:08.686 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/Backups.backupdb/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:08.753 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/Backups.backupdb/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:08.823 mddiagnose[974:707] Executing '/usr/bin/find /.MobileBackups/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:08.890 mddiagnose[974:707] Executing '/usr/bin/find /.MobileBackups/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:08.958 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.311 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/TimeMachine/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:23.570 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.MobileBackups/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.637 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.MobileBackups/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:23.705 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/IPOD/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.772 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/IPOD/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:23.841 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:23.971 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Video/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:24.041 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:24.297 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'..
2013-11-09 09:30:24.816 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:24.946 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:25.077 mddiagnose[974:707] Executing '/usr/bin/find //.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:25.207 mddiagnose[974:707] Executing '/usr/bin/find //.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:35.454 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/Backups.backupdb/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:35.520 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Audio/Backups.backupdb/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:35.587 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.MobileBackups/.Spotlight-V100 ( -type d -and ( ! -name Cache -or -prune ) ) ! -name Cache -exec echo ; -print -execdir ls -l {} ;'...
2013-11-09 09:30:35.654 mddiagnose[974:707] Executing '/usr/bin/find /Volumes/Photo/.MobileBackups/.Spotlight-V100 -name *.plist -exec echo ; -print -exec echo ; -exec /bin/cat {} ;'...
2013-11-09 09:30:35.951 mddiagnose[974:707] Executing '/usr/bin/find / -name .metadata_never_index -maxdepth 1'...
2013-11-09 09:30:36.018 mddiagnose[974:707] Executing '/usr/bin/find /Volumes -name .metadata_never_index -maxdepth 2'...
2013-11-09 09:30:36.590 mddiagnose[974:707] Getting crash logs for 'mds'...
2013-11-09 09:30:36.651 mddiagnose[974:707] Getting crash logs for 'mdworker'...
2013-11-09 09:30:36.652 mddiagnose[974:707] Getting crash logs for 'Spotlight'...

Why is my machine so slow I feel the hd all- ways running

Why is my machine so slow I feel the hd all- ways running?

Re: Why is my machine so slow I feel the hd all- ways running
Apr 16, 2014 9:05 PM (in response to stevejobsfan0123)
Hardware Information:
          iMac (27-inch, Mid 2011)
          iMac - model: iMac12,2
          1 3.1 GHz Intel Core i5 CPU: 4 cores
          4 GB RAM
Video Information:
          AMD Radeon HD 6970M - VRAM: 1024 MB
System Software:
          OS X 10.9.2 (13C64) - Uptime: 0 days 0:31:35
Disk Information:
          WDC WD1001FALS-403AA0 disk0 : (1 TB)
                    EFI (disk0s1) <not mounted>: 209,7 MB
                    disk0s2 (disk0s2) <not mounted>: 999,35 GB
                    Recovery HD (disk0s3) <not mounted>: 650 MB
          OPTIARC DVD RW AD-5690H
USB Information:
          Apple Computer, Inc. IR Receiver
          Apple Internal Memory Card Reader
          HP Deskjet 3050 J610 series
          Apple Inc. BRCM2046 Hub
                    Apple Inc. Bluetooth USB Host Controller
          Apple Inc. FaceTime HD Camera (Built-in)
FireWire Information:
Thunderbolt Information:
          Apple Inc. thunderbolt_bus
Launch Daemons:
          [System] com.adobe.fpsaud.plist 3rd-Party support link
          [System] com.google.keystone.daemon.plist 3rd-Party support link
          [System] com.microsoft.office.licensing.helper.plist 3rd-Party support link
          [System] com.oracle.java.Helper-Tool.plist 3rd-Party support link
          [System] com.oracle.java.JavaUpdateHelper.plist 3rd-Party support link
Launch Agents:
          [System] com.google.keystone.agent.plist 3rd-Party support link
          [System] com.oracle.java.Java-Updater.plist 3rd-Party support link
User Launch Agents:
          [not loaded] com.adobe.ARM.[...].plist 3rd-Party support link
          [not loaded] com.microsoft.LaunchAgent.SyncServicesAgent.plist 3rd-Party support link
User Login Items:
          Moveslink2
          iTunesHelper
          VLCStreamer
          Google Drev
          MenuTab for Facebook
          Garmin ANT Agent
          RemoteMouse
          AdobeResourceSynchronizer
Internet Plug-ins:
          o1dbrowserplugin: Version: 5.2.4.18058 3rd-Party support link
          OVSHelper: Version: 1.1 3rd-Party support link
          Default Browser: Version: 537 - SDK 10.9
          Flip4Mac WMV Plugin: Version: 2.4.0.11 3rd-Party support link
          AdobePDFViewerNPAPI: Version: 11.0.06 - SDK 10.6 3rd-Party support link
          FlashPlayer-10.6: Version: 12.0.0.77 - SDK 10.6 3rd-Party support link
          Silverlight: Version: 5.1.20913.0 - SDK 10.6 3rd-Party support link
          Flash Player: Version: 12.0.0.77 - SDK 10.6 Outdated! Update
          QuickTime Plugin: Version: 7.7.3
          googletalkbrowserplugin: Version: 5.2.4.18058 3rd-Party support link
          SharePointBrowserPlugin: Version: 14.3.6 - SDK 10.6 3rd-Party support link
          AdobePDFViewer: Version: 11.0.06 - SDK 10.6 3rd-Party support link
          GarminGpsControl: Version: 4.0.4.0 Release - SDK 10.6 3rd-Party support link
          JavaAppletPlugin: Version: Java 7 Update 51 Outdated! Update
Safari Extensions:
          Pinterest: Version: 1.0
          Add To Amazon Wish List: Version: 1.8
          LinguaLeo: Version: 1.0.5
          MLB.com Toolbar: Version: 1.1
Audio Plug-ins:
          BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
          AirPlay: Version: 2.0 - SDK 10.9
          AppleAVBAudio: Version: 203.2 - SDK 10.9
          iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
          Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
3rd Party Preference Panes:
          DivX 3rd-Party support link
          Flash Player 3rd-Party support link
          Flip4Mac WMV 3rd-Party support link
          Java 3rd-Party support link
          VLC Streamer 3rd-Party support link
Old Applications:
          /Library/Application Support/Microsoft/MERP2.0
                    Microsoft Fejlrapportering:          Version: 2.2.9 - SDK 10.4 3rd-Party support link
                    Microsoft Ship Asserts:          Version: 1.1.4 - SDK 10.4 3rd-Party support link
          SLLauncher:          Version: 1.0 - SDK 10.5 3rd-Party support link
                    /Library/Application Support/Microsoft/Silverlight/OutOfBrowser/SLLauncher.app
          /Applications/Microsoft Office 2011/Office
                    Microsoft Graph:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Database Utility:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Office Overførselscenter:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Office Påmindelser:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    My Day:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    SyncServicesAgent:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Open XML for Excel:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Alerts Daemon:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Database Daemon:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Chart Converter:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Clip Gallery:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
          /Applications/Microsoft Office 2011
                    Microsoft PowerPoint:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Excel:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Outlook:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Word:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
                    Microsoft Document Connection:          Version: 14.3.6 - SDK 10.5 3rd-Party support link
          Microsoft AutoUpdate:          Version: 2.3.6 - SDK 10.4 3rd-Party support link
                    /Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app
          Solver:          Version: 1.0 - SDK 10.5 3rd-Party support link
                    /Applications/Microsoft Office 2011/Office/Tilføjelsesprogrammer/Solver.app
          Wondershare Video Converter Ultimate:          Version: 1.5.4 - SDK 10.5 3rd-Party support link
Time Machine:
          Skip System Files: NO
          Mobile backups: OFF
          Auto backup: YES
          Volumes being backed up:
          Destinations:
                    Data [Network] (Last used)
                    Total size: 2
                    Total number of backups: 54
                    Oldest backup: 2013-09-16 11:44:43 +0000
                    Last backup: 2014-04-16 17:42:09 +0000
                    Size of backup disk: Excellent
                              Backup size 2 > (Disk size 0 B X 3)
          Time Machine details may not be accurate.
          All volumes being backed up may not be listed.
Top Processes by CPU:
              10%          mds
               1%          EtreCheck
               1%          WindowServer
               0%          Safari
               0%          Moveslink2
Top Processes by Memory:
          213 MB          Finder
          209 MB          Safari
          193 MB          MenuTab for Facebook
          143 MB          com.apple.WebKit.WebContent
          119 MB          com.apple.IconServicesAgent
Virtual Memory Information:
          311 MB          Free RAM
          1.59 GB          Active RAM
          1.30 GB          Inactive RAM
          823 MB          Wired RAM
          602 MB          Page-ins
          0 B          Page-outs

I'm running OS X 10.6.8-Why is Time Machine all of a sudden backing up 225GB of data after 2 years of perfect service? I have not added, deleted, or upgraded anything, Help!

I'm running OS X 10.6.8-Why is Time Machine all of a sudden backing up 250GB of data after 2 years of perfect service? I have not added, deleted, or upgraded anything.

USB 3.0 drives work on USB 2.0 but you do get 2.0 speed. They are cheaper because they are popular PC drives. If you get a new computer you'll get the bump to 3.0 speed.
I like the Seagate USB 3.0 Backup plus drives. They come formatted for PC but easy to format in Disk Utility. Seagate Backup Plus Right now the 1T is more than the 2 & 3T drives
This Western Digital drive has good reviews: WD My Book Hard Drive for Mac 2 TB $99.
Locally, Best Buy seems to have the best prices.
USB 3.0 is 10x faster than USB 2.0
Thunderbolt is 12 times faster than FireWire 800 and up to 20 times faster than USB 2.0.
Format new drives with Apple's Disk Utility rather than the software that come with the drive.
My plan was to rid a lot of the stuff I have on my computer (to a hard drive) anyhow once it had backed up.
I wound't necessarily backup those files to Time Machine. I would copy to the external drive then delete from computer. Only backup to Time Machine the data you would want to restore to your Mac if there was a problem. The backup will go much faster this way. Time Machine backup is slower than just copying data in my experience.

Do you have any ideas why Motion 5 would run slow on a computer? I have an Imac with 8Gigs of ram, and plenty of hard drive space, but it still gives me the beach ball when I add a few lights and effects. I'm at the end of my rope.

Do you have any ideas why Motion 5 would run slow on a computer? I have an Imac with 8Gigs of ram, and plenty of hard drive space, but it still gives me the beach ball when I add a few lights and effects. I'm at the end of my rope.

You probably don't really need 1080 at 60 for your finished projects but since you're just starting out with Motion, you need to lower your expectations. A long way. 1080 is about 2 million pixels per frame, DV is only about 400,000. That's not just five times as many pixels for the Mac to track; everything in video is exponential.
Explore the training tutorials available by Mark Spencer. You will get an idea of how his super powerful machine reacts with the software.
Adding a light roughly doubles the processing time over flat scenes. Two lights increases processing again. Reflections require processing the lights and then calculating the reflections so add another quarter of the time required for flat scenes. Add camera movement, motion blur, and depth of field and you need exponentially more processing time for every frame. The preload of renders into RAM is one of the cooler features of Motion, as comapred to After Effects, but that takes tons of time, to.
Try working in ye olde DV resolution for a few days. Get to know the software's limitations and what gets imposed by your Macintosh. Step up to 720p/30 and see how things slow down.

Time Machine Runs All Night...Every Night.

Ove the past month or so I've noticed Time Machine seems to be running (especially at night) any time I'm not actively using my MacBook. (When I'm using the MB it seemed to operate normally backing up every hour or so.)
I initally thought that after a year's worth of accumulated back ups, the Time Machine file was getting too large to efficiently manage. So, not needing all those backups I wiped the hard disk that contained the back ups and started from scratch. (I back up to a hard drive, via wifi, through an Airport Extreme.)
I also Verified/Repaired the disk through Disk Utility.
This seemed to help for a coupe of days, but eventually it was back to the same, Time Machine chugging along seemingly all night. And now, the MB was getting warm when it really should be mostly idle.
So, I did some more research and found this webpage below that suggested if all else fails do a "Full Reset of Time Machine". The proceedure involves deleting the Time Machine ".plist" file and resetting your preferences. Your back up files will stay intact.
http://pondini.org/TM/A4.html
Wow! This really did the trick! Time Machine no longer runs all night long, and even the hourly backups during the day seem to process much quicker. So, if your Time Machine seems to just constantly chug along when you think it should be idle - give this a try.
Thanks to Pondin for putting the info out there that really helped me......
As an aside.....
I'm fairly new to the world of "Mac". I've had this MacBook a little over a year. In that time I've had 3 issues with: IPhoto, Mail, and Time Machine. (The programs just started acting "wonky".)
All these issues were fixed by deleting a ".plist" file (or a group of ".plist" files).
What are these ".plist" files and why are they always getting corrupted? Is this common? Am I doing something wrong? Is there anything I can do to make the files a little more roubust and keep them from getting corrupted?
Seems like one goes bad every 4-months and takes the app down with it.
Q.

Noelle Buscher wrote:
I dont recall this problem a month ago when I first got the Time Capsule. I do remember seeing the Time Machine running quite a bit, but it didnt affect my performance (at least not to the degree that I was going up and turning it off all the time)
Opening a webpage...takes about 10-15 seconds. Of course, I look up at the Time Machine and it is running. Opening a file takes forever...ESPECIALLY a Photoshop or other large file. Time Machine is running.
I will STOP the back-up so I can get something accomplishes...but ultimately have to go up and just turn it off completely, as it starts running again shortly.
Is there a setting for only running a backup once a day? I cant find it.
No, as Time Machine is designed to run hourly, and ordinarily works best that way.
You've clearly got something else going on here. I'd recommend starting by doing a +*Repair Disk+* on the sparse bundle. See #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of the +Time Machine+ forum.
If that doesn't help, try all the things in #D2 there.
Once you get it doing regular backups, see if the size makes sense considering the amount of changes you think you've made. If the backups seem too large, see #D4 in the Troubleshooting Tip. You may have an app that's causing extra-large (and therefore lengthy) backups.

Time machine running unrealistically large backups

Ever since I upgraded to Mavericks, backing up using Time Machine has been acting a little wonky. It can be summarized by this evening's back up, which took ten minutes to get past the "Preparing to Back Up" sequence and then backed up a huge, whopping 50gb of information. After only a week, this is an unrealisitcally large back up - I've not edited nor created that much data on my computer. Back ups after a week's time while on Mountain Lion were around 8gb at most for me. This is also not the first back up I've done since upgrading to Mavericks (the others were also unusually large). Why does Time Machine insist on backing up so much additional information?

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

HT1430 Why does my iPad run slow

Why is my iPad running slow and closes a page when I'm on it?

Some general troubleshooting steps in order:
Terminate the Safari Application and restart it. Click the Home button to return to App screen. Double click Home to bring up the App tray. Touch and hold the Safari icon until “-” appears. Touch the “-” to terminate Safari. Terminate all other Apps listed as well. Then restart Safari.
Use Settings > Safari > Clear History and Clear Cookies and Data
Restart iPad: Press and hold the Sleep/Wake button until the red slider appears. Slide your finger across the slider to turn off the device. To turn it back on, press and hold the Sleep/Wake until the Apple logo appears.
Reset iPad: Press and hold the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears. Ignore the "Slide to power off".
Restore iPad: Connect to iTunes on a PC/Mac and do a restore.

Why does Time Machine disappear?

Why does Time Machine disappear each restart?

Suggest that you power cycle the entire network, as things are likely out of sequence
Power every device off on the network, order is not important
Wait a few moments, then start the modem first and let it run by itself for 2-3 minutes
Start the Time Capsule the same way
Start each network device one at a time about a minute apart
Check for proper operation

HT1277 Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Ok; I'm not sure what you're doing. 36 hours is rather long. Seems like a new migration. Not what I intended.
Here's what I intended: from the newly-migrated and apparently-corrupt environment, create a new user, not related to any existing user, nor any migration-created user, or any other user for that matter. That is, use  > System Preferences > Users and Groups, authenticate yourself by clicking on the padlock, and then click the + and create a wholly new user. Then log in under that user and establish the mail access.
36 hours? I'm wondering if there's an error or an exceedingly slow network here? Or a really, really slow disk? Or a sick backup? (WiFi isn't the path I'd usually choose, either.)
Failing the attempted second migration, I'd try a different tactic. Does your existing (old) system work? If so, I'd bypass the backup and connect an external (scratch) USB disk drive to the (old) sstem and then boot and use Disk Utility booted from the installer DVD disk or boot and use Disk Utility from the recovery partition or booted from a recovery partition created on some other external storage (details here vary by the OS X version and what hardware you have), and perform a full-disk backup of your original internal disk to (scratch) external storage. (Make sure you get the source and target disks chosen correctly here; copying the wrong way — from the scratch disk to your existing disk — will clobber your data!) In esssence, this will clone your existing boot disk. Then dismount the (formerly-scratch) external disk, transfer it over to the new system, and use it as the source of the migration, by performing a fresh OS X installation on the new system.
Target Disk Mode is also sometimes an option for accessing the disk for a migration, but that requires the right cable, and requires systems that have the same external connection; newer MacBook Pro systems use Thunderbolt for this, and older systems tend to use FireWire. And I'm guessing you don't have compatible hardware.
The details here can and do vary by your OS X versions and your particular Mac systems — if you'll identify the specific models and hardware, somebody might be able to better tailor the above (fairly generic) sequence to your particular configuration.

Why is time machine running slow?

Similar Messages

Maybe you are looking for