Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[sckn]

Is this on Big Sur?


Which WiFi/BT card do you have? Or are you using OpenIntelWireless drivers?

Sorry.
I’ve updated the system.

I’ve now onboard card. And also my keyboard is not working. Also lost wifi too. I’m not sure what happened.

Just wanted to migrate. And I followed the steps you wrote.

 

[CaseySJ]

...
Now I did use the legacy boot option, but it failed. Mike pointed out why, but clearly reminded me that soon there won't be a legacy boot option anyway, because that is what Apple wants.
...

Because System files and User/Home files have been separated into separate APFS volumes since Big Sur, it somewhat makes sense to change the way backups are done. This is because:

• System volume is read-only in Big Sur.
• System volume is both read-only and crytographically sealed in Monterey.

This means that System volume is less likely to be corrupted from malicious applications, accidents, and user negligence. System volume can still fail due to hardware reasons.

Because the User or Home volume is distinct from the System volume, it means that macOS compartmentalizes the two:

• System volume is one compartment
• User or Home volume is another compartment

We can therefore backup our User or Home compartment, which is guaranteed to preserve everything that we produce and own. The System volume will contain only that which Apple produces.

So in the event of the System volume crashing, we could use the Recovery process to reinstall macOS on that volume.

But if the whole disk crashes and we lose even the Recovery partition, then we would need to install macOS from scratch. But just restoring our User or Home volume to the new disk might not be enough -- we may need a post-recovery procedure to make macOS recognize the "user ID" of the recovered volume.

Now that the release version of Monterey is installed on my system, I'll see if bootable backups are still working... Will update this post shortly.

Update: Bootable backups are still working with Legacy Bootable Backup Assistant. To ensure that the System volume is backed up, it's necessary to erase the APFS volume ahead of time.

 

[CaseySJ]

Sorry.
I’ve updated the system.

I’ve now onboard card. And also my keyboard is not working. Also lost wifi too. I’m not sure what happened.

Just wanted to migrate. And I followed the steps you wrote.

Because you're using OpenIntelWireless drivers, please post screenshot of OpenCore Configurator --> Kernel.

What is the make/model of your keyboard? Is it a Bluetooth keyboard?

 

[mm2margaret]

Because System files and User/Home files have been separated into separate APFS volumes since Big Sur, it somewhat makes sense to change the way backups are done. This is because:

• System volume is read-only in Big Sur.
• System volume is both read-only and crytographically sealed in Monterey.

This means that System volume is less likely to be corrupted from malicious applications, accidents, and user negligence. System volume can still fail due to hardware reasons.

Because the User or Home volume is distinct from the System volume, it means that macOS compartmentalizes the two:

• System volume is one compartment
• User or Home volume is another compartment

We can therefore backup our User or Home compartment, which is guaranteed to preserve everything that we produce and own. The System volume will contain only that which Apple produces.

So in the event of the System volume crashing, we could use the Recovery process to reinstall macOS on that volume.

But if the whole disk crashes and we lose even the Recovery partition, then we would need to install macOS from scratch. But just restoring our User or Home volume to the new disk might not be enough -- we may need a post-recovery procedure to make macOS recognize the "user ID" of the recovered volume.

Now that the release version of Monterey is installed on my system, I'll see if bootable backups are still working... Will update this post shortly.

Well, it (the legacy boot option) may work, but for me it did not. That really doesn't matter, because bootable backups are done - sooner or later. The "legacy" boot option is absolutely legacy, and it will be soon done entirely.

I don't see your logic. Restoring via the Recovery partition is difficult and very very slow. I know, I just did it. All my data is not on the Home and User directories exclusively. And the Application directory is massive. So, for me, that doesn't work either.

But really, typically, and particularly in SSDs, its the whole disk that just stops responding. And in that scenario, you're in exactly the situation that I detailed in my post.

So, Bombich recommends the Migration Assitant to make sure all of your settings are restored. Again, I just did it and I know how long it takes. Its not fast. (and I'm working on a very fast machine - I did this not on my Z490, which is fast, but not as fast as the machine I just did this on).

Better buy two (and mirror them)!

 

[CaseySJ]

Well, it (the legacy boot option) may work, but for me it did not. That really doesn't matter, because bootable backups are done - sooner or later. The "legacy" boot option is absolutely legacy, and it will be soon done entirely.

The Legacy Bootable Backup feature is still working. This is being posted after booting entirely from a backup disk I just created with CCC 6.0.4 that is connected via USB 3.0 to SATA adapter. Any time we want to back up the System volume, we have to erase the entire destination volume group (not necessarily the whole disk), which will delete both the System and User/Home member volumes. Then we backup everything from scratch. So having two backup disks is a good idea here so that at any given time a backup is available.

I don't see your logic. Restoring via the Recovery partition is difficult and very very slow. I know, I just did it. All my data is not on the Home and User directories exclusively. And the Application directory is massive. So, for me, that doesn't work either.

I was referring to reinstalling macOS from Recovery. I've never done this because I've never needed to do it. But for the time being, the Legacy Bootable Backup feature is still working.

But really, typically, and particularly in SSDs, its the whole disk that just stops responding. And in that scenario, you're in exactly the situation what I detailed in my post.

So, Bombich recommends the Migration Assitant to make sure all of your settings are restored. Again, I just did it and I know how long it takes. Its not fast. (and I'm working on a very fast machine - I did this not on my Z490, which is fast, but not as fast as the machine I just did this on).

Mike Bombich does not have a particularly congenial demeanor. Probably understandable if he fields a large number of customer issues daily. I tend to lose my patience more easily now than I used to... Years of responding to issues does that.

The bottom line is this: Bootable Backups are still working so we can cross this bridge when we come to it.

 

[mm2margaret]

Probably understandable if he fields a large number of customer issues daily. I tend to lose my patience more easily now than I used to... Years of responding to issues does that.

Really? How about 30 years of doing that????

 

[avtor]

Because you reported two issues, which of the following is still a problem?

1. OCB: LoadImage Failed
2. Cannot see macOS volume names in OpenCore Picker

Are you able to compress and post your EFI folder (with serial numbers removed from PlatformInfo --> DataHub)?

Thanks @CaseySJ , please see in the attached. The issue with graphical presentation has been resolved. However I still have both issues listed below:

1. OCB: LoadImage Failed
2. Cannot see macOS volume names in OpenCore Picker, except for USB volume with Catalina install.

 

[CaseySJ]

Thanks @CaseySJ , please see in the attached. The issue with graphical presentation has been resolved. However I still have both issues listed below:

1. OCB: LoadImage Failed
2. Cannot see macOS volume names in OpenCore Picker, except for USB volume with Catalina install.

Please try attached EFI folder, but copy serial numbers back into PlatformInfo --> DataHub before use.

Also, we should use iMac19,1 instead of iMac14,2.

 

[dehjomz]

Because System files and User/Home files have been separated into separate APFS volumes since Big Sur, it somewhat makes sense to change the way backups are done. This is because:

• System volume is read-only in Big Sur.
• System volume is both read-only and crytographically sealed in Monterey.

This means that System volume is less likely to be corrupted from malicious applications, accidents, and user negligence. System volume can still fail due to hardware reasons.

Because the User or Home volume is distinct from the System volume, it means that macOS compartmentalizes the two:

• System volume is one compartment
• User or Home volume is another compartment

We can therefore backup our User or Home compartment, which is guaranteed to preserve everything that we produce and own. The System volume will contain only that which Apple produces.

So in the event of the System volume crashing, we could use the Recovery process to reinstall macOS on that volume.

But if the whole disk crashes and we lose even the Recovery partition, then we would need to install macOS from scratch. But just restoring our User or Home volume to the new disk might not be enough -- we may need a post-recovery procedure to make macOS recognize the "user ID" of the recovered volume.

Now that the release version of Monterey is installed on my system, I'll see if bootable backups are still working... Will update this post shortly.

Update: Bootable backups are still working with Legacy Bootable Backup Assistant. To ensure that the System volume is backed up, it's necessary to erase the APFS volume ahead of time.

Ever since APFS was developed, I've just been using a separate APFS volume for my User Directory... this has saved me countless times when I needed to reinstall macOS. Whenever I need to reinstall, I can format the installation volume just fine, no data loss (except perhaps for the apps in the /Applications folder, but one could theoretically make that it's own Volume as well).

Then when I reinstall macOS, and I create a user, I just go to System Preference->Users and Groups->Advanced Options, and point the newly created user's home directory to my existing directory on the safe APFS volume.

Restart and boom, I pick up exactly where I left off, sometimes I may have to re-login to iCloud, sometimes not.

 

[avtor]

Please try attached EFI folder, but copy serial numbers back into PlatformInfo --> DataHub before use.

Also, we should use iMac19,1 instead of iMac14,2.

View attachment 531992

Really appreciate your help @CaseySJ ! Did you change anything else in the folder? Otherwise I will just change to iMac19,1