I just lately acquired a 14″ MacBook Professional (M3 Professional, working macOS 14.3.1) and I have been making an attempt to switch my recordsdata over. I attempted utilizing Goal Disk Mode (with two totally different cables, one USB-C and the opposite an authorized 2ft Thunderbolt 3 cable from a Sonnet eGPU) nevertheless the M3 Mac’s drive doesn’t present up on the Intel Mac (2018 MacBook Professional working macOS 13.5.4). I attempted every part after which finally gave up.
So as an alternative I am copying every part to an exterior drive (which is a Samsung 970 EVO NVMe, encrypted, APFS) in a Thunderbolt 3 enclosure, utilizing the identical Thunderbolt 3 cable above.
Once I copy every part from the Intel Mac to the drive it copies lightning quick. Nevertheless, once I plug it into the M3 Mac and attempt to copy, this can be very sluggish. Over the previous hour it has transferred (13,000 recordsdata in whole with a dimension of seven.44 GB) at round 800KB/sec based on my math, and nonetheless estimates 2 hours to go. Copying these recordsdata onto the drive from the Intel Mac will need to have taken lower than a minute.
Any concept what is going on on right here? I’ll word that that is the primary time this drive has been related to this new Mac, if that would probably have something to do with it. It is a fairly recent Mac, I solely began setting it up yesterday; I’ve loaded Homebrew and a few packages, made some shell modifications, added just a few apps (Firefox, Visible Studio Code) and that is it.
EDIT: The issue exists with different exterior drives as properly. I’ve an exterior SATA SSD in a USB-A 3.0 case, utilizing a typical USB-A to USB-A cable with an Amazon Fundamentals USB-A to USB-C adapter. For a 2.95GB switch the primary 900MB goes in about 15 seconds, then slows to crawl, taking a pair minutes to succeed in 1.21 GB, then a pair extra to succeed in 1.54GB. The progress bar additionally stops shifting and counting slowly, it simply jumps between these values:
two minutes after reaching 900MB:
two minutes later:
UPDATE: So now I’ve spent all day with this. It handed Apple Offline Diagnostics, and I turned off Highlight indexing for the exterior drive (it could have already been listed by my different Mac) and booted in Protected Mode. Similar factor. Transfers take some time to “heat up”, i.e. the stripe within the standing bar strikes back and forth for a bit, then it often will get the primary 10% or so fairly fast, with frequent updates. Then it slows to a crawl, first estimating 1 minute, then an increasing number of relying on the dimensions of the switch. The CPU load is minimal and I did not see any Highlight processes working so far as I am conscious. The recordsdata get there, and there aren’t any issues with them, however…
There does appear to be a glitchy/laggy interplay with the drive (on the M3 Mac), it does not appear to wish to eject readily, saying it is in use by another course of. Cancelling a switch won’t work, and opening the drive within the Finder would possibly take a very long time to view the contents.
Additionally, watching a high-defintion video from the exterior drive is sort of seamless and I can scan ahead and reverse simply. However based on BlackMagic Disk Pace take a look at I solely get round 2.2 MB/sec from the drive. Similar to the file transfers it begins at 0 for some time, goes as much as 4 after a minute, goes right down to this after one other minute:
So there’s something unusual occurring…
UPDATE #2: I am pondering there’s one thing flawed with this Mac. This cannot be regular. I’ve a 240MB TIFF, 14787×5993 pixels. Opening in Preview on the 2018 13″ MBP beach-balls for five seconds, however then I can zoom in with Cmd+0 and scroll round instantly. On the recent 2023 14″ MBP it opens instantly, however then if I zoom with Cmd+0 it beach-balls for at the very least 25 seconds earlier than it slowly “unblurs” the picture to its precise decision. Scrolling round throughout the picture may be very laggy. That is with the 2023 working nothing and the 2018 working a number of functions, and there is nothing consuming up CPU within the background based on Exercise Monitor.
