1

I've a 2012 MBP. I recently upgraded to mojave and everything was fine and dandy in terms of speed and everything. However, my hard drive failed. Luckily I had just done a time machine backup a few hours prior to HDD failing. After getting a new SSD and starting to recover I hit some issues:

  • it took several days to do the time machine recovery of 500GB
  • now my machine runs really really slow. As in it takes 30s to register one keyboard press etc.

any pointers/help would be much appreciated.

enter image description here enter image description here enter image description here

Improve this question
3
  • can you look in Activity Monitor is MDS and MDS_stores are using a lot of CPU, or who is using CPU ? In any case in order to understand what is your system doing, please post a screen shot of the Activity Monitor, CPU and memory usage.
    – Ruskes
    Oct 27, 2018 at 21:34
  • sorry, forgot to mention the activity monitor status. All "vitals" look good, meaning CPU is low, Memory usage is low, disk usage is low. Edited post with screenshots
    – PageUp
    Oct 28, 2018 at 23:06
  • 2012 ? is that original battery ?
    – Ruskes
    Oct 28, 2018 at 23:39

1 Answer 1

Reset to default
1

It may be a bad drive. Having this exact same problem, system extremely slow after Time Machine restore, all vitals check out fine, but I'm using a late 2015 iMac. Seems to be a pretty specific problem. It's important to note this is an APFS volume, as this seems to be somewhat common. I upgraded to Mojave about 3 months ago.

Opened console, and saw invalid btree errors constantly happening as files were trying to be accessed, I'm assuming that's the cause of the slowness. Disk Utility found errors but couldn't repair, booting in single user mode using fsck couldn't repair.

Decided to wipe the volume, and re-install the OS. 2 minutes before finishing the first step of the install, an error appeared saying there was a problem with the install, and to "try again." This was enough evidence to tell me this physical disk is bad.

One more thing to note about this, my Time Machine drive (external 3TB WD drive) went bad at the same time, cannot be repaired, doesn't show up when doing a recovery from a backup. Not sure what to make of that, as that's obviously too coincidental.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .