Hi,

I've posted before on the up and down path to switching from one older MBP to an identical unit — trying to navigate a failing SSD, etc.

I just tried to do a TM backup on a clean external drive, and it failed halfway through. However...

In looking at the files that were backed up, it seems it got the main drive (what I wanted), then hiccuped when it tried to go to the second internal drive. Keep in mind that TM failed.

So, I connected that external to the new MBP, and launched Migration Assistant. It's just spinning at the point, "Looking for Source." Been doing that for several minutes.

Question. For the drive to show up in Migration Assistant, does it require a "successful" backup, so all the ones and zeroes are somehow lined up?

Or, does it have to read that entire drive before it reports it as recognized?

The backup drive mounts on the source MBP, which it just tried to copy. Don't see the activity light flickering on the drive, while it's connected to the target computer.

You guys know this stuff, and I can't find it in search, so I'm asking.

Thanks.

Backing up from a mid-2012 MBP with latest Catalina...to same model MBP, with same version Catalina.



Edited 2 time(s). Last edit at 05/23/2021 11:50PM by dmag.

By the way, when I connect the external, it mounts to the desktop. Just isn't seen by the migration assistant.

I only see two options remaining.

1. Delete the second internal (already backed up elsewhere), and take a second run the TM backup. That way, if the error was related to that, maybe TM will complete as normal and then migration assistant will recognize it.

2. Manually copy the backed up contents of the Library, system, and applications over to the new Catalina install on the target machine. Maybe that's not a great idea, but if the TM backup and migration can't happen, I'd have 25+ apps to download and install, purchased font libraries, etc.

Lots of work.

Please give me any other ideas you may have. Thanks.



Edited 1 time(s). Last edit at 05/24/2021 03:16AM by dmag.

CCC will clone the Data on the source drive to the target drive, including ALL of the 3rd party apps and inner workings. I just discovered this this weekend when Migration Assistant would co-operate with Big Sur drives. I ended up just installing the OS and then using CCC to move the rest over. So far I have not had any regrets. During the Data cloning, CCC copies all non-system files, including ALL User accounts.

---

Ed (modelamac)

I think I will just put an OUT OF ORDER
sticker on my head and call it a day.



Edited 1 time(s). Last edit at 05/24/2021 08:15AM by modelamac.

Quote
modelamac
CCC will clone the Data on the source drive to the target drive, including ALL of the 3rd party apps and inner workings. I just discovered this this weekend when Migration Assistant would co-operate with Big Sur drives. I ended up just installing the OS and then using CCC to move the rest over. So far I have not had any regrets. During the Data cloning, CCC copies all non-system files, including ALL User accounts.

Yes, just do this.

I recommend downloading and using CCC 5 right now. CCC 6 is brand new and we just fixed a bug related to corrupt source data, but haven't pushed out the update yet (still testing it). Since you might have corrupt data on your dying drive, stick with 5.

Hey dmag!
Another vote on the clone, but I think your 1 and 2 options are on the right path.
I would do #3, DL and install everything fresh, but I understand your reluctance.
Don’t lose sight though, that your data seems to come from a corrupted source.
By the way, I think if TM didn’t complete satisfactorily, MigAss wouldn’t touch it.



Good luck!!

Previous thread:

[forums.macresource.com]


Yes, keep in mind that you most likely have corrupted files.

You said that you were manually backing up some important files in that other thread. How did that go?

You also mentioned an older clone. How old, and how much new stuff do you have that wouldn’t be on it?

If it were me, I’d manually migrate to a fresh system install. That would give me the most confidence that I’d left any file corruption behind; most times corrupted data files would reveal themselves as you transferred stuff. I also have found that manually migrating results in good performance, especially when you’ve kept the old system going for a long time, or one that has been on several system versions or multiple Macs.

My Plan B might be to manually migrate the newer files to the older clone (if I read the old thread correctly). You might try an incremental backup from the problem drive to a copy of said old clone using CCC.

Fonts are pretty easy to transfer, and reinstalling apps would give you a chance to rethink their usefulness.

Good Luck!



Edited 1 time(s). Last edit at 05/24/2021 12:15PM by btfc.

Quote
btfc
Previous thread:

[forums.macresource.com]


Yes, keep in mind that you most likely have corrupted files.

You said that you were manually backing up some important files in that other thread. How did that go?

You also mentioned an older clone. How old, and how much new stuff do you have that wouldn’t be on it?

If it were me, I’d manually migrate to a fresh system install. That would give me the most confidence that I’d left any file corruption behind; most times corrupted data files would reveal themselves as you transferred stuff. I also have found that manually migrating results in good performance, especially when you’ve kept the old system going for a long time, or one that has been on several system versions or multiple Macs.

My Plan B might be to manually migrate the newer files to the older clone (if I read the old thread correctly). You might try an incremental backup from the problem drive to a copy of said old clone using CCC.

Fonts are pretty easy to transfer, and reinstalling apps would give you a chance to rethink their usefulness.

Good Luck!

Thanks.

I've had a handful of library/system files not copy, and that, of course, stops the process each time. Not a big deal.

Today, I'll delete the second drive and try for the TM backup again, which would be the simplest way out of this mess.

The target computer has a fresh install, so I'm hoping migration assistant will play nice, putting all the pieces where they need to be.

If not, then I can do the manual process with apps and fonts, etc. It's just unhappy labor, but I can do a little to start with the more import apps and fonts, and then the rest over time.

Good advice. Thanks again

Quote
FormerlySaleenl
I recommend downloading and using CCC 5 right now. CCC 6 is brand new and we just fixed a bug related to corrupt source data, but haven't pushed out the update yet (still testing it). Since you might have corrupt data on your dying drive, stick with 5.

I have CCC 5. It failed on a subtask several times. However, maybe with some of the files now cleaned out, it will work. Thanks

Quote
rich in distress
Hey dmag!
Another vote on the clone, but I think your 1 and 2 options are on the right path.
I would do #3, DL and install everything fresh, but I understand your reluctance.
Don’t lose sight though, that your data seems to come from a corrupted source.
By the way, I think if TM didn’t complete satisfactorily, MigAss wouldn’t touch it.



Good luck!!

Guessing you're absolutely right. Thanks.

Quote
modelamac
CCC will clone the Data on the source drive to the target drive, including ALL of the 3rd party apps and inner workings. I just discovered this this weekend when Migration Assistant would co-operate with Big Sur drives. I ended up just installing the OS and then using CCC to move the rest over. So far I have not had any regrets. During the Data cloning, CCC copies all non-system files, including ALL User accounts.

Thanks for this. Hopefully, it will work this time. Failed the last time, which sort of pushed me into all this activity.

Quote
dmag

Quote
FormerlySaleenl
I recommend downloading and using CCC 5 right now. CCC 6 is brand new and we just fixed a bug related to corrupt source data, but haven't pushed out the update yet (still testing it). Since you might have corrupt data on your dying drive, stick with 5.

I have CCC 5. It failed on a subtask several times. However, maybe with some of the files now cleaned out, it will work. Thanks

If it's failing on particular files/folders sitting on bad sectors, you can use the "Copy Some Files" option to exclude those files. Then re-run the clone-job.

More often than not, it's just cache files or temp files sitting on bad sectors (at least in the initial stages of failure) since those types of files are the most common ones being written on your Mac.

---

Edited 1 time(s). Last edit at 05/24/2021 03:53PM by Sarcany.

Quote
Sarcany

Quote
dmag

Quote
FormerlySaleenl
I recommend downloading and using CCC 5 right now. CCC 6 is brand new and we just fixed a bug related to corrupt source data, but haven't pushed out the update yet (still testing it). Since you might have corrupt data on your dying drive, stick with 5.

I have CCC 5. It failed on a subtask several times. However, maybe with some of the files now cleaned out, it will work. Thanks

If it's failing on particular files/folders sitting on bad sectors, you can use the "Copy Some Files" option to exclude those files. Then re-run the clone-job.

More often than not, it's just cache files or temp files sitting on bad sectors (at least in the initial stages of failure) since those types of files are the most common ones being written on your Mac.

That's great info to know. I'll try that. Thanks.