I have a 3 year old iMac (21.5-inch, Late 2013) running OS X 10.13.5 with 8 GB RAM and 1TB HDD.
It's been running very slow (takes minutes to open an Application, about 30 seconds to open a folder, etc). I've checked for viruses and malware but found nothing. I've scanned through log files in Console but also found nothing.
I decided to re-install OS X and was performing a backup. There's 650GB of files and Carbon Copy Cloner has taken 7.5 hours to backup 595 GB. Activity Monitor is running and on the Disk tab reports Data read/sec at 577KB and Data written/sec at 311KB.
This seems slow. No evidence of any resource problem (CPU is mostly idle, RAM fine, no network I/O at the moment).
Is the backup time normal? 8 hours to copy 600 GB seems slow to me but maybe not?
If the slow backup time is not normal, how can I diagnose if there's a hardware I/O problem?
Best Answer
Backups that take 16 hours are certainly normal if you have lots of small files top update and copy (lots been 200,000 or so). Diagnosing failing / failed drives is generally easy for a technician since the system logs IO errors to the system log and hangs to Library/Logs. On the end user level, you won't be able to run a filesystem check / repair disk / erase disk using Disk Utility without errors when a drive is failed or failing. (Unfortunately you may get no warning other than a slowdown before it fails, so good on you for having a backup now)
For backups, the HDD access time is what limits things - doubly so if your source and destination are spinning drives or worse, a remote network volume. HDD might handle several hundred IOPS (input and output per second) best case and the backup process throttles IO usage to not impact the running system so if the backup ran in the foreground what might take an hour might stretch to dozens since it's throttled.
Now that your backup is done, how long does it take to make a backup if you quit all the apps running, and don't have any launch when you log in and then perform this test.
The command for that is:
On a 2015 MacBook with SSD backing up to a new USB 3.0 HD, you might see this for a very small change in data from the last backup interval on a smoothly running system:
If you post a couple of these with actual times we can discuss if it's worth erasing the drive and repartitioning it and running some speed benchmark tests or if you just need an SSD instead of HDD or if this is a sign the drive is failing and you'll be super glad you have a backup to restore once you replace that drive with a new HDD that runs at full speed.