iMac Retina 17,1 OCLP HowTo from Catalina backup?

[Dr Lou]

Hello friends! I think I need some clarification on the correct path...
I've managed to get my old iMac 17,1 working - a 27" Retina - and have formatted the drive.
OCLP 2.4.1 has been built, and have achieved a 'clean' Sonoma install as a test. Machine works great this way! SUPER work, OCLP Guys!

GOAL: would be the newest reasonable macOS (Sonoma?), after restoring from a Time Machine Backup.

Backup, however, is from my original machine - a now dead dosDude'd Catalina box. (does this use HPFS Journaled?) TM Backup is running from a disk attached to another machine on network - running an OCLP 2.4.1 patched Sonoma, and this foodchain also seems suspect, probably because of the incompatible filesystems?

I understand there are some gotchas in the install path - based on newer OSes needing APFS if I recall? - which requires some removal, then reinstall of root patches, but cannot find a clear recipe. Could someone point me to one? How and when am I amble to uninstall, then re-install root patches?

 

[Bigwaff]

How and when am I amble to uninstall, then re-install root patches?

OCLP application should have been installed in Sonoma by default. Launch app, remove patches. Reboot.

MrMacintosh has a guide

 

[Dr Lou]

OCLP application should have been installed in Sonoma by default. Launch app, remove patches. Reboot.

MrMacintosh has a guide

Thanks for your reply - I'm generally following exactly what he's doing... I just never get to a 'desktop' which has been 'booted from the USB', at which I can boot the OCLP app.

Will Sonoma even see my Catalina (Extended; Journaled) backup?

OK; gotta keep trying...

 

[Bigwaff]

Will Sonoma even see my Catalina (Extended; Journaled) backup?

Yes.

 

[Dr Lou]

Yes.

Time Machine First Backup never completes...

OK; many thanks. Little by little, I've gotten to a working, restored (Ventura) system on 17,1. Fabulous! Working great. Goal is to migrate upward after full backup of the new setup. First, though, a new problem...

Have reformatted my (old) Time Machine drive with APFS; it's 4 TB with about 100 GB carved out for test volumes of Sonoma, Sequoia. The Time Machine first backup will never complete:

Time Machine runs to a significant percentage of the 1.8 TB of the system drive - 20-ish % - of backup, then quits, and disconnects all volumes on the Time Machine drive.
There is an IOTest file produced on the Time Machine...
I never see any filesystem structure produced on it.
TM log likely contains clues, but have no idea how to pull meaningful intelligence from it.

Obviously, I don't want to move upward in OS updates until the backup is secure.

So far, I've tried:
Deleting all snapshots on Ventura drive, then producing one.
Running Caffeine to be sure machine is not sleeping. Seems to have no impact.

What am I missing?

 

[Bigwaff]

For OCLP macOS installs, you need to revert root patches before running TM backup.

1. Open the OpenCore-Patcher application and revert root patches and reboot. When rebooting, hold down Option key.
2. This Apple Boot Picker screen. Pick your OCLP EFI (Ventura) disk (typically internal disk).
3. Next will be OC Boot Picker screen. Pick your OCLP macOS disk (typically internal disk). Boot will continue.
4. Login and wait for desktop to appear.
5. OCLP should prompt that you are running w/out root patches. Don't install root patches; cancel this dialog.
6. Plug in your TM drive. Follow the instructions to set up the TM drive. Make sure to set the backup frequency to manual.
7. Perform the backup. Once the back up is complete, eject the TM drive.
8. Open the OpenCore-Patcher application and install root patches. Reboot following the same sequence as before. System is now running with root patches.

You will need to do these steps every time you want to run TM backups as you do not want to backup w/ root patches installed. If you do, you will not be able to use the TM backup to restore to a fresh macOS install.

 

[Dr Lou]

Fantastic, @Bigwaff! And thank you for your quick reply - have been struggling with this. OK, testing it now; letting it run overnight. (Any suggestions for a USB3 or Thunderbolt-to SATA speedier solution for backup is welcomed!)

Assuming backup goes well - and I know it will! - with the root patches now removed, am I now safe to attempt install of Sonoma; dare I say Sequoia? Would I boot from an OCLP installer USB stick (as I installed Ventura)?, or would a direct install from Apple Installer work? (Or, how could it, without the patches in place...?)

My logic needs testing. Trying to do this safely, having come this far.

Thanks Again!

 

[Bigwaff]

Assuming backup goes well - and I know it will! - with the root patches now removed, am I now safe to attempt install of Sonoma; dare I say Sequoia? Would I boot from an OCLP installer USB stick (as I installed Ventura)?, or would a direct install from Apple Installer work? (Or, how could it, without the patches in place...?)

At this point, follow the steps in MrMacintosh video. Pick up from where he installs fresh OCLP macOS from USB flash drive and restores from TM.

 

[Dr Lou]

OK; looks like I'm still in trouble. Per your suggestion, I've removed root patches and re-started the backup.

It gets to a point of reporting about 20% done, even that ~74 GB have been 'copied'.
And, running overnight, something(?) has unmounted all three volumes - including Time Machine one - on the backup drive. They are then remounted - presumably by the Time Machine restart? - and the process begins again.

But I see no directory structure or files being written to the Time Machine volume.
There is the 'IOCheck' file being written, but it is only about 20 MB.
(does TM write a vast number of invisible files?)
Time Machine format is APFS Case-Sensitive Encrypted
The source drive is an Apple hybrid Fusion Drive.
- is any of this critical?

Should I be considering other backup tools at this point, or would those just be reproducing the same problem? ChronoSync? Carbon Copy Cloner?

I'd be nervous about continuing without a solid backup.

 

[Bigwaff]

And you have ruled out failing internal Fusion drive?

 

[Dr Lou]

Can't say that I've ruled out the possibility, with any definitive diagnostic tests. Have run DiskUtil checks, which pass fully. Same is true of the Time Machine disk/volume. What would be a definitive diagnostic?

In general, though, the machine runs really great. It's been a not-very-heavy use desktop machine. This Time Machine backup is literally its only problem.

 

[Bigwaff]

With the TM disk attached, open Terminal and post/screenshot of the output of diskutil list

 

[Dr Lou]

With the TM disk attached, open Terminal and post/screenshot of the output of diskutil list

% diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 2.0 TB disk0s2

/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_APFS Container disk2 121.1 GB disk1s2

/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.1 TB disk2
Physical Stores disk1s2, disk0s2
1: APFS Volume Macintosh HD 9.3 GB disk2s1
2: APFS Snapshot com.apple.os.update-... 9.3 GB disk2s1s1
3: APFS Volume Preboot 2.1 GB disk2s2
4: APFS Volume Recovery 1.2 GB disk2s3
5: APFS Volume Macintosh HD - Data 2.0 TB disk2s4
6: APFS Volume VM 1.1 MB disk2s5

/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *4.0 TB disk3
1: EFI EFI 314.6 MB disk3s1
2: Apple_APFS Container disk5 4.0 TB disk3s2

/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +4.0 TB disk5
Physical Store disk3s2
1: APFS Volume OCLP Sonoma 50.0 GB disk5s2
2: APFS Volume OCLP Sequoia 50.0 GB disk5s3
3: APFS Volume Time Machine 619.1 GB disk5s4

Output from DriveDx on the NVMe - looks OK, right?;

 

[Bigwaff]

When the TM disks mounts, the OCLP Sonoma and OCLP Sequioa volumes mount as well? In TM settings, are these volumes excluded from backups? If not, add them to the exclusion list.

 

[Dr Lou]

When the TM disks mounts, the OCLP Sonoma and OCLP Sequioa volumes mount as well? In TM settings, are these volumes excluded from backups? If not, add them to the exclusion list.

Yes, they both mount simultaneously. I should probably disable that auto mounting, but I'd rather not futz with an fstab at this point.

Yes, both Sonoma and Sequoia volumes are excluded from backups - which Time Machine(?) somehow did automatically, perhaps because they're on the same disk? I didn't exclude them manually, fwiw.

All three of those volumes are encrypted, with passwords stored in my keychain for the moment just to make this whole process smoother.

Finally, in installing DriveDx, I was prompted to install a kernel extension for DriveDx to be able to diagnose USB-connected drives (which this Time Machine disk is). I have not rebooted the machine since this install, so have not run DriveDx against Time Machine. Should I be concerned about this new kernel extension from The Wilds? Could it do any damage to the OCLP setup, when I re-enable OCLP's Root Patches?

 

[Dr Lou]

OK, I was concerned about the DriveDx-installed extension, given the underlying OCLP install. No need to worry; all was AOK after reboot...
However, DriveDx indicated many non-relocatable errors on the Time Machine drive - something to be aware of, as I had been using this drive for backups right up until a few weeks ago...
So, I'm retiring this drive as 'dead'.
Have now managed to get a good TM backup, though on a (for the moment) much-too-small drive.
Again, @Bigwaff, many thanks for your brainstorming and help on this.

 

[Dr Lou]

OK - Having gotten a nice, working install of Ventura, thought I might try the update to Sequoia. Please note: I'm reading about problems with Tahoe on Apple Fusion Drives, so am not goin' there...

Install of Sequoia goes smoothly, and machine runs great - as long as I boot from the USB OCLP Installer...

I've installed OCLP onto the SSD 'volume' of the Fusion Drive, can select it in boot picker, but it will not boot the 'spinning' Macintosh HD.

I've verified that the EFI and System structures are being written to the SSD - I can see it in Clover Configurator. As a test, I've deleted these and reinstalled OCLP. No Joy!

Got a feeling I'm in for a journey here. What can you suggest?

 

[Bigwaff]

I've installed OCLP onto the SSD 'volume' of the Fusion Drive, can select it in boot picker, but it will not boot the 'spinning' Macintosh HD.

Suspect you have split Fusion Drive into separate component drives. Boot supported macOS Recovery, open Terminal, and post output of diskutil list again. If you have split Fusion Drive, you will need to recombine following this article

How to fix a split Fusion Drive - Apple Support

If your Fusion Drive appears as two drives instead of one in the Finder, it's no longer working as a Fusion Drive. Here's how to fix it.

support.apple.com

Then try OCLP macOS install again.

 

[Dr Lou]

Suspect you have split Fusion Drive into separate component drives. Boot supported macOS Recovery, open Terminal, and post output of diskutil list again. If you have split Fusion Drive, you will need to recombine following this article

How to fix a split Fusion Drive - Apple Support

If your Fusion Drive appears as two drives instead of one in the Finder, it's no longer working as a Fusion Drive. Here's how to fix it.

support.apple.com

Then try OCLP macOS install again.

Will try your suggestion later this morning. Thanks for getting back...

I didn't do anything to actively split the drive - what would I have done? the logical melding of the two devices must be software-mediated(?) How would one have disrupted this? All interesting...

 

[Dr Lou]

(this output is while the installed Sequoia is running; is it important that diskutil output come from Recovery state?)
Shows up as Fusion single drive in Disk Utility GUI, but two devices in System/Storage output:

(Yes; USB and Seagate media are extraneous to the discussion - apologies. Except that system is booted from USB OCLP EFI picker...)

% diskUtil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 121.1 GB disk0s2

/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_APFS Container disk2 2.0 TB disk1s2

/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.1 TB disk2
Physical Stores disk1s2, disk0s2
1: APFS Volume Macintosh HD 13.2 GB disk2s1
2: APFS Snapshot com.apple.bless.C955... 13.2 GB disk2s1s1
3: APFS Volume Preboot 2.5 GB disk2s2
4: APFS Volume Recovery 1.3 GB disk2s3
5: APFS Volume Macintosh HD - Data 2.0 TB disk2s4
6: APFS Volume VM 1.1 GB disk2s5

/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *31.2 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS Install macOS Sequoia 30.9 GB disk3s2

/dev/disk4 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_APFS Container disk5 2.0 TB disk4s2

/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk5
Physical Store disk4s2
1: APFS Volume Time Machine 1.9 TB disk5s2

 

[Dr Lou]

@Bigwaff - Many thanks! With your help, I now have a nice, running Sequoia on my 17,1 iMac! Though it wasn't clear the Fusion Drive had been split, I did start over from scratch, being sure to Re-Fuse it, then to reinstall from scratch. All running great now, with Post-Install patches, etc. Have not yet run a backup, though...

Please let me verify, though, what I believe you advised(?) - that I should not(?) allow Time Machine to back up with patches running, as this will produce a non-usable backup? Did I get this right?

Finally, is it still safe to over-the-air update incremental OS updates and 'security' updates, even with patches running? - I want to be sure I'm in step with latest OCLP 'rules'!!

Overall, Many Thanks to the OCLP Wizards! Really great work. You're breathing life into perfectly good machines...

 

[Bigwaff]

Please let me verify, though, what I believe you advised(?) - that I should not(?) allow Time Machine to back up with patches running, as this will produce a non-usable backup? Did I get this right?

That is correct.

Finally, is it still safe to over-the-air update incremental OS updates and 'security' updates, even with patches running? - I want to be sure I'm in step with latest OCLP 'rules'!!

Should be safe. OCLP will detect macOS update installation is launched and prompt to uninstall patches. Then update can proceed. Because OCLP adjusts SIP settings and breaks SSV in order to work, macOS updates on OCLP Macs will be full-sized installers. Because of this, many decide to create OCLP macOS USB install media of update, boot from USB, and install macOS full to perform an "update".