How to migrate all my data from one external ssd to another, but not the OS

[MichaelWV]

Hi. I hope to make this clear! I have been running my old, late-2102 iMac from an external SSD. The result has been rather spectacular. For a few months I was using OS Big Sur, courtesy of an OCLP installation. It's works very well and I love Big Sur. It's a little slow in booting up, but I can put up with that.

Now, I recently installed Monterey to another external SSD. That proved much more problematic. It took me a couple of weeks to succeed. I have no I idea why but it really was a bit of a nightmare. Eventually I did it, and now I want to transfer all my data from the Big Sur SSD to the new, "virgin" SSD of Monterey.

I tried Migration Assistant. Twice. It didn't work. I'm completely puzzled as to why it failed,as I pretty much sat there, for over two three-hour periods, watching as all the data was apparently being transferred from the older SSD to the new Monterey-loaded one. Each time, after completion, there was no data from the Big Sur SSD on the the new SSD! I mean nothing, other than the initial installation! It's as if I never did anything. How is this even possible?! I watched the stuff being transferred. So, where did it go? Where is it??! I'm speechless, frankly.

There should be roughly 1TB of data on the new Monterey SSD, after migration, but there's only 24 GB used! Crazy.

Can anyone offer any ideas as to what went wrong, and how to fix it it, please? I was thinking of trying Super Duper or Carbon Copy Cloner, but I'm unsure it they'll do what Migration Assistant is "supposed" to do. It's absolutely baffling.

So, to summarise: I want to migrate all my external SSD Big Sur contents (except the OS) over to the new, unused external SSD version of Monterey. I thought it should be easy, but I've failed twice, and I'm not a beginner with Macs. This has temporarily beaten me, though.

Thanks for any ideas as to solving this.

-M

EDIT: I attach a screenshot of a Super Duper setting that looks like it might work. Not sure....

 

[BrianBaughn]

Without going into details I'm wondering if it would work to clone the Big Sur SSD to the new SSD and then upgrade it to Monterey.

 

[MichaelWV]

Without going into details I'm wondering if it would work to clone the Big Sur SSD to the new SSD and then upgrade it to Monterey.

Thank you kindly for your contribution. I assume you mean just installing Monterey on top of the existing Big Sur.

In my trials and tribulations trying to install Monterey, I did use OCLP and performed a simple upgrade, on top of the Big Sur SSD, despite advice to not do such a thing. It failed, every time. By fail, I mean it would never boot up, but got "stuck" half way. I'm aware of others on the web with installation and boot up issues like this.

So, luckily, I've now have a bare bones OS of Monterey, that refuses to to yield to Migration Assistant's attempts to move over the Big Sur data. All of it. Interestingly, this Monterey SSD boots quicker than than the Big Sur, but I think that's just due to it only being the OS present.

For some reason, Monterey has been very problematic, whilst the OCLP install of Big Sur was easy. So, I don't think doing this again will suddenly succeed, after multiple attempts at an overwrite failed miserably. To clarify, I did clone the Big Sur disk, many times, and tried overwriting Monterey, to no avail.

And, respectfully, it still doesn't explain why, after two attempts with Migration Assistant, and sitting there for over two hours apiece, watching the data being copied over, why nothing ultimately happened. It simply evaporated into thin digital air, both times! Never experienced anything like this.I was incredulous.!

-m

 

[Mike Boreham]

Hi. I hope to make this clear! I have been running my old, late-2102 iMac from an external SSD. The result has been rather spectacular. For a few months I was using OS Big Sur, courtesy of an OCLP installation. It's works very well and I love Big Sur. It's a little slow in booting up, but I can put up with that.

Now, I recently installed Monterey to another external SSD. That proved much more problematic. It took me a couple of weeks to succeed. I have no I idea why but it really was a bit of a nightmare. Eventually I did it, and now I want to transfer all my data from the Big Sur SSD to the new, "virgin" SSD of Monterey.

I tried Migration Assistant. Twice. It didn't work. I'm completely puzzled as to why it failed,as I pretty much sat there, for over two three-hour periods, watching as all the data was apparently being transferred from the older SSD to the new Monterey-loaded one. Each time, after completion, there was no data from the Big Sur SSD on the the new SSD! I mean nothing, other than the initial installation! It's as if I never did anything. How is this even possible?! I watched the stuff being transferred. So, where did it go? Where is it??! I'm speechless, frankly.

There should be roughly 1TB of data on the new Monterey SSD, after migration, but there's only 24 GB used! Crazy.

Can anyone offer any ideas as to what went wrong, and how to fix it it, please? I was thinking of trying Super Duper or Carbon Copy Cloner, but I'm unsure it they'll do what Migration Assistant is "supposed" to do. It's absolutely baffling.

So, to summarise: I want to migrate all my external SSD Big Sur contents (except the OS) over to the new, unused external SSD version of Monterey. I thought it should be easy, but I've failed twice, and I'm not a beginner with Macs. This has temporarily beaten me, though.

Thanks for any ideas as to solving this.

-M

EDIT: I attach a screenshot of a Super Duper setting that looks like it might work. Not sure....
View attachment 2294778

I don’t have any answers because as far as I can see what you did with MA ought to have worked. So can only assume it is something to do with OCLP.

You could try using a bootable Monterey installer to install a Monterey System volume onto the -Data volume you want to use. I know you said installing Monterey was difficult but did you try using bootable installer?

 

[reppresident]

Just try the migration before root patching with oclp at the final steps of the install. It should work this way.

 

[MichaelWV]

I don’t have any answers because as far as I can see what you did with MA ought to have worked. So can only assume it is something to do with OCLP.

You could try using a bootable Monterey installer to install a Monterey System volume onto the -Data volume you want to use. I know you said installing Monterey was difficult but did you try using bootable installer?

Thank you for contributing.

If by that you mean an installer on a USB stick, then yes, absolutely. That's standard. In this case, though, it was formatted from OCLP, with an EFI installed. As far as I know,and because we are dealing with an unsupported Mac here) OCLP is the only way to do this.

Reading between the lines, I don't think the OCLP methodology is strictly aimed at external drives. It's intended for internal drive use. If you look at the excellent Mr. Macintosh tutorials, they only feature internal drive installation. Having said that, my Big Sur is running well, and very reliable.

-m

 

[MichaelWV]

Just try the migration before root patching with oclp at the final steps of the install. It should work this way.

Thank you for that, but it's too late. The installation is complete and the OCLP Patcher was installed to the Monterey SSD.

I guess I would have to start all over again, in that case, and the installation was tortuous enough. I'm not actually sure how to implement what you suggest, frankly. My technical knowledge is fair, but not comprehensive.

-m

 

[reppresident]

Thank you for that, but it's too late. The installation is complete and the OCLP Patcher was installed to the Monterey SSD.

I guess I would have to start all over again, in that case, and the installation was tortuous enough. I'm not actually sure how to implement what you suggest, frankly. My technical knowledge is fair, but not comprehensive.

-m

Try revert patches and then do the migration assistent. Might work this way too.

 

[MichaelWV]

Try revert patches and then do the migration assistent. Might work this way too.

Not sure what that is. Sorry. My present installation of Monterey is, as I said "virgin". Actually, that's not quite true. There is copy of the Open-Core patcher on there, which had to go in as part of the OCLP installation. Do you think deleting it would solve this? I'm thinking if i delete it, the SSD won't show up in the EFI, on boot up ...

Thanks.

-m

 

[Fnord]

Do you have a Time Machine backup of the Big Sur drive? When I’ve used Migration Assistant it’s been from Time Machine backups.

 

[MichaelWV]

Hi. Thank you. No, I never use Time Machine. Maybe I should! I use either Super Duper or Carbon Copy Cloner to back up my things, regularly.

-m

 

[MichaelWV]

Try revert patches and then do the migration assistent. Might work this way too.

Ah, I just looked at the Patcher. You mean revert root patches, I think. I will give that a go, when I get time. Probably over the weekend. If it works I will report back. I can always revert. Thank you for the suggestion. Let's see...

-m

 

[cipherneo]

EDIT: I attach a screenshot of a Super Duper setting that looks like it might work. Not sure....

I would be careful with that 'Backup - all files' SuperDuper! script since I believe it's going to copy everything including the macOS installation since the what's it's going to do subtext states it will make the target identical to the source.

 

[MichaelWV]

I would be careful with that 'Backup - all files' SuperDuper! script since I believe it's going to copy everything including the macOS installation since the what's it's going to do subtext states it will make the target identical to the source.

Hi. Thank you. Yes, that's exactly what I subsequently thought! That's a can of worms I don't care to open....

-m

 

[MichaelWV]

Try revert patches and then do the migration assistent. Might work this way too.

Hi again. Right, I just booted up into the Monterey SSD and reverted the root patches. Two things happened. I had to restart (of course) for it to kick in.

1. the boot up was a lot slower.
2. I lost both of my 23" Apple displays that I have connected to my iMac. No matter, I can get them back when I reactivate the root patcher.

So, Now it's kind of ready to try the Migration again, which I cannot do right now. Will let everyone interested know how that pans out. In the meantime, if anyone has further thoughts please let me know. Thank you all for your time.

I'm still puzzled as to why I could clearly see all the files being copied over to the Monterey drive on both attempts. Perhaps it only appeared that they were being migrated, but actually not. Well that's me clutching at straws...

-m

 

[reppresident]

Hi again. Right, I just booted up into the Monterey SSD and reverted the root patches. Two things happened. I had to restart (of course) for it to kick in.

1. the boot up was a lot slower.
2. I lost both of my 23" Apple displays that I have connected to my iMac. No matter, I can get them back when I reactivate the root patcher.

So, Now it's kind of ready to try the Migration again, which I cannot do right now. Will let everyone interested know how that pans out. In the meantime, if anyone has further thoughts please let me know. Thank you all for your time.

I'm still puzzled as to why I could clearly see all the files being copied over to the Monterey drive on both attempts. Perhaps it only appeared that they were being migrated, but actually not. Well that's me clutching at straws...

-m

sorry to heard that. to me, it worked at the final step of the Monterey install process, but my config doesnt need any root patches, but i was instructed to do before the root patches install anyway if my machine does needed them. Maybe try make a new volume and do a clean install and try migrate before the root patches install

 

[MichaelWV]

sorry to heard that. to me, it worked at the final step of the Monterey install process, but my config doesnt need any root patches, but i was instructed to do before the root patches install anyway if my machine does needed them. Maybe try make a new volume and do a clean install and try migrate before the root patches install

I didn't receive such a prompt to Migrate. This is what I get, as default, with OCLP app. Attached, from the Big Sur SSD, but it's the same in Monterey.

 

[reppresident]

Im not using the same oclp version you do. Maybe its a lil diferent this version as mine 0.4.11 prompts. But i dont know if this is the best version for your machine.

 

[MichaelWV]

Im not using the same oclp version you do. Maybe its a lil diferent this version as mine 0.4.11 prompts. But i dont know if this is the best version for your machine.

Good point!

-m

 

[reppresident]

Im just tryin to help. Sooner or later you will figure it out. For sure.

 

[Fishrrman]

I'm thinking that the OCLP stuff is interfering with migration assistant.
Perhaps it also interferes with SuperDuper and CarbonCopyCloner.
(I've never used OCLP, so I don't know enough about how it works).

In that case, you might consider a "fully manual migration".
This is a lot of work and it takes time.
But you may not have another easy choice.

By "fully manual migration" I mean that you copy folders and files "by hand" from the old drive to the new one.

This will include folders/files that are outside of your home folder (on the old drive) and inside it, too.

You MUST take steps to overcome permissions problems (I won't detail these here, yet).
You SHOULD keep HANDWRITTEN notes as you go along, so you don't "go in circles".

There may be an easier way that other users have found.
But if nothing else works, a manual migration should do the job.

 

[MichaelWV]

Im just tryin to help. Sooner or later you will figure it out. For sure.

SUCCESS! Thank you so much, Sir, for your suggestion. It worked. The migration was 100% successful. BUT.....

Now Monterey will not boot up.I kid you not. This is becoming like a Rubik Cube. I get one side right and another side screws up. It's been an interesting day. The Migration Assistant worked, as per your advice. I'm very, very grateful. But now I'm back to this stuck boot up, which was happening previously to me. And others, I understand.

I'm not sure if this is the case, but it seems to be something to do with introducing Big Sur into the equation, because my "virgin" Monterey booted up fine, and pretty quickly. Dunno. It's beyond a dumbass like me, lol.

So, right now, I've had enough, and I feel this issue is veering off-topic, as I'm moving into a stuck boot issue. Going to need a break from this over the weekend, but it's a professional necessity that I get Monterey working. I intend to purchase a Mac Studio. As as a pro composer, using Macs, it's well-known that one steers clear of the latest OS's. So, I need a working external SSD version of Monterey, because I'm going nowhere near "Sonoma", or even Ventura, for some time to come.

Cannot understand why all this is so difficult with Monterey, when Big Sur was a delight to install. It boots up slowly, though, but it works.

Once again, thank you, reppresident, for your time and help. I feel I'm close. Very close.

-m

 

[MichaelWV]

I'm thinking that the OCLP stuff is interfering with migration assistant.
Perhaps it also interferes with SuperDuper and CarbonCopyCloner.
(I've never used OCLP, so I don't know enough about how it works).

In that case, you might consider a "fully manual migration".
This is a lot of work and it takes time.
But you may not have another easy choice.

By "fully manual migration" I mean that you copy folders and files "by hand" from the old drive to the new one.

This will include folders/files that are outside of your home folder (on the old drive) and inside it, too.

You MUST take steps to overcome permissions problems (I won't detail these here, yet).
You SHOULD keep HANDWRITTEN notes as you go along, so you don't "go in circles".

There may be an easier way that other users have found.
But if nothing else works, a manual migration should do the job.

Thank you for taking the trouble with your good advice. I concur with your theory re: OCLP, but they are doing an incredible service, for free, trying to cover all contingencies, as I'm sure you appreciate. It's amazing.

Oh, absolutely: manual transference is on my list, but it's at the bottom. My appetite for attempting such an endeavour is... muted; but I note your advice well.

Keeping notes. Great idea. You know what? I'm actually pretty meticulous and thorough. I do (on occasion) keeps notes, but, for some reason, even though I'm quite tech-stupid, I have a very good memory for procedural stuff like this, and can recall quite complex operational orders. Weird. Cannot solve this stuck boot-up yet, though.

I agree, OCLP might be the issue. It's a necessary,um, evil. I vigourously resist using that word, actually; it sounds disrespectful. I don't mean it in that way. The team behind it are outstanding (heroes), and Mr. Macintosh is wonderful, but, well, I'm just a stupid composer, who has no real interest in tech stuff. It's hard enough writing the music. A lot of the OCLP finesse is lost on a tech dullard like myself. I just want Monterey to obey. No, I'm not a lyricist.

Anyway, thank you again, and send my best wishes to Kernow. I'm half-Cornish, and intend to relocate there next year, after 16 years in Canada.

-m

 

[reppresident]

SUCCESS! Thank you so much, Sir, for your suggestion. It worked. The migration was 100% successful. BUT.....

Now Monterey will not boot up.I kid you not. This is becoming like a Rubik Cube. I get one side right and another side screws up. It's been an interesting day. The Migration Assistant worked, as per your advice. I'm very, very grateful. But now I'm back to this stuck boot up, which was happening previously to me. And others, I understand.

I'm not sure if this is the case, but it seems to be something to do with introducing Big Sur into the equation, because my "virgin" Monterey booted up fine, and pretty quickly. Dunno. It's beyond a dumbass like me, lol.

So, right now, I've had enough, and I feel this issue is veering off-topic, as I'm moving into a stuck boot issue. Going to need a break from this over the weekend, but it's a professional necessity that I get Monterey working. I intend to purchase a Mac Studio. As as a pro composer, using Macs, it's well-known that one steers clear of the latest OS's. So, I need a working external SSD version of Monterey, because I'm going nowhere near "Sonoma", or even Ventura, for some time to come.

Cannot understand why all this is so difficult with Monterey, when Big Sur was a delight to install. It boots up slowly, though, but it works.

Once again, thank you, reppresident, for your time and help. I feel I'm close. Very close.

-m


View attachment 2295759 View attachment 2295760

Do an nvram clean. Then try to boot from the usb efi on boot picker holding option key at boot, probably then monterey will boot normaly. from the mac preferences, select the monterey vol as next boot disk and reboot ( without the usb ). it might work this way.

 

[MichaelWV]

Do an nvram clean. Then try to boot from the usb efi on boot picker holding option key at boot, probably then monterey will boot normaly. from the mac preferences, select the monterey vol as next boot disk and reboot ( without the usb ). it might work this way.

Thanks. I just checked the boot preferences and saw that the Monterey disk was selected. I'll try the nvram and other and get back.

What I don't understand is, when selecting option on the startup, there is no EFI for the Monterey SSD, but there is for the Big Sur SSD and the USN installer.

-m