Can migrating from 2017 MBPro to new one corrupt the new one?

My 2017 13" Intel MBPro is on its last legs (won't charge past 79%, sticky keys, frequent lock-ups, Time Machine backups fail--when it even detects an external drive (WD MyPassport, WD G-Drive), which half the time it won't. Only place these show up is in Disk Utility (both passed First Aid), but can't properly unmount them. I fear the issue is that they're corrupted...because my computer itself is. (Disk Utility First Aid says it's OK). Just bought a new 2023 14" M2 MacBookPro and want to migrate my data to it--but I'm afraid doing so would just transfer my current computer's problems to the new one. Posted in a different thread, but the only advice I got from a Community member was to use Target Disk mode. I take it that requires a special Thunderbolt (not merely USB-C to USB-C) cable, which I don't have and which the Apple Store sales guy said I don't need if I use Migration Assistant hardwired rather than wirelessly. I don't want to screw up my new computer. If I bring it in to the Apple Store, they can do it for me--but I would have to surrender it for 24-48 hours and I don't know if even they would just transfer the old problems to the new computer. The 2017 one is way past warranty (they didn't offer the AppleCare+ renewal option back then), so it'd cost me an arm & a leg for them to diagnose it.


Thoughts?

MacBook Pro 13″, macOS 13.4

Posted on Jul 21, 2023 4:36 PM

Reply

Similar questions

8 replies

Jul 22, 2023 1:39 PM in response to Sandra Andina1

Not charging past 79% sounds like it may be the new battery management system stopping the charging at 80%. You can uncheck the "Optimized Charging" in the Battery System Preferences/Settings to see if this solves that particular problem.


Do you have the Touchbar or non-Touchbar model?


If an external hard drive is only intermittently seen, then I would suspect the USB-C ports on the laptop. Try rotating the USB-C connector for the hard drive 180 degrees upside down to see if the drive will mount in case the port is half bad. Also try using another USB-C port especially on the other side of the laptop.


Make sure to connect the drive directly to the laptop. Disconnect all other external devices in case one of them is causing a problem.


FYI, First Aid will lie to you so even if the summary result is "Ok", click "Show Details" and scroll back through the report to see if any unfixed errors are listed.


Keep in mind a 2017 model will only support Ventura....the new OS, Sonoma, being released later this year will not be supporting the 2017 model.

Jul 22, 2023 11:34 AM in response to Sandra Andina1

Thanks--you confirmed my suspicions. Think what I'll do is bring this 2017 MBPro into the AppleStore for them to diagnose and repair the hard drive (then erase the bad backups). Yeah, it'll cost me, but even so it's worth not screwing up my new computer. In the meantime, I can set up the new one w/o migrating anything yet) and use my iPad Pro w/Magic Keyboard folio as my computer for e-mails, etc. It's what I travel with anyway.

Jul 22, 2023 4:49 PM in response to Sandra Andina1

Here are the details:


Running First Aid on “Macintosh HD” (disk1s5s1)


Verifying the startup volume will cause this computer to stop responding.


Verifying file system.

Volume could not be unmounted.

Using live mode.

Performing fsck_apfs -n -l -x /dev/rdisk1s5

Checking the container superblock.

Checking the checkpoint with transaction ID 30054159.

Checking the EFI jumpstart record.

Checking the space manager.

Checking the space manager free queue trees.

Checking the object map.

Checking the encryption key structures.

Checking volume /dev/rdisk1s5.

Checking the APFS volume superblock.

The volume Macintosh HD was formatted by storagekitd (1677.50.1) and last modified by apfs_kext (2142.120.7).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking snapshot 1 of 1 (com.apple.os.update-3379F3DC95CFF07D9D49D5CE34EF1CCB1E66EF7D12A3055A5D1A0D2695C12EDE)

Checking the fsroot tree.

Checking the file extent tree.

Checking the extent ref tree.

Verifying volume object map space.

Verifying allocated space.

The volume /dev/rdisk1s5 appears to be OK.

File system check exit code is 0.

Restoring the original state found as mounted.


Operation successful.


Jul 22, 2023 4:52 PM in response to Sandra Andina1

And here's the scan of Macintosh HD Data:


Running First Aid on “Macintosh HD - Data” (disk1s1)


Verifying the startup volume will cause this computer to stop responding.


Verifying file system.

Volume could not be unmounted.

Using live mode.

Performing fsck_apfs -n -l -x /dev/rdisk1s1

Checking the container superblock.

Checking the checkpoint with transaction ID 30054182.

Checking the EFI jumpstart record.

Checking the space manager.

Checking the space manager free queue trees.

Checking the object map.

Checking the encryption key structures.

Checking volume /dev/rdisk1s1.

Checking the APFS volume superblock.

The volume Macintosh HD - Data was formatted by hfs_convert (748.21.6) and last modified by apfs_kext (2142.120.7).

Checking the object map.

Checking the snapshot metadata tree.

Checking the snapshot metadata.

Checking the document ID tree.

Checking the fsroot tree.

warning: inode (id 8682526146): dir-stats key xf does not exist, despite internal_flags (0x8412)

Checking the extent ref tree.

Verifying volume object map space.

Verifying allocated space.

The volume /dev/rdisk1s1 appears to be OK.

File system check exit code is 0.

Restoring the original state found as mounted.


Operation successful.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Can migrating from 2017 MBPro to new one corrupt the new one?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.