- Nov 11, 2018
- Asus ProArt Z690-Creator
- RX 6800 XT
- Classic Mac
- Mobile Phone
Before posting, please check for any time stamp gaps in the boot log, like this:last boot was between normal and slow. It was 55 secs from open core picker to apple password login. While it’s loading the screen went black midway and come back with a apple login even I tried to force the screen to stay awake. I am going to post more bootleg files.
log show --last boot > ~/Documents/full-boot-log.txt
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.
That’s cool, whatever works for you.Well, I just use Clonezilla now. As long as I have access, or some way to connect a drive and boot clonezilla, I can clone a bootable drive just fine. There's even a gui version of Clonezilla called rescuezilla available.
I just don't use Carbon Copy Cloner anymore. I've tried the legacy backup method and sometimes it works and sometimes it doesn't. Too unreliable for me. And, you have to keep in mind that its going to end soon, probably with the next version of macOS. That's a shame, because I like CCC but it just doesn't do what I need anymore. I won't be upgrading it anymore.
The problem I see with the method you identify above is, for me, the Applications directory. Creating a separate volume to me seems like a stretch and a lot of extra work, but if it works for you, great. For me, clonezilla works and works well enough, at least for now.
Hi fellow vision-g user, I have question:Thank you all, I have update my system OpenCore 0.7.4 from Big Sur 11.6 to Monterey 12.0.1, any issues and about 40 min. 4 reboots. All working really fine! Waiting to resolve the Ethernet issue for Monterey.
That’s cool, whatever works for you.
I just made a bootable backup of a Monterey install using the legacy approach. I moved from a Samsung drive (with slow macOS boot times) to a WD SN750 NVME ssd (in a thunderbolt enclosure). And it worked just fine. My boot time dropped from over 90 seconds to 8 seconds. You just have to let it erase the destination disk fist.
I also used CCC yesterday to transfer my user directory (on an old MacBook Pro) to another disk temporarily so I could fresh install Big Sur 11.6.1. CCC can copy whole drives or just certain folders. Your choice.
I’m using open core legacy patcher on my old MacBook since Apple cut it off at Catalina! I never thought I’d be using OC on a real MacBook, but Big Sur is running beautifully. Wifi Bluetooth intel hd 4000 acceleration all working. I needed to use CCC to copy my files because the built in macOS Finder wouldn’t transfer my 400,000+ files that I accumulated since 2012.
I haven’t had any problems with CCC and I’ve been using it for years.
All of this. If my machine goes down, it’s one thing to do an OS install. Another thing entirely to do an OS + all of my software and libraries. It’s literal 100s of gigs of download software. It takes over a day to accomplish a full install.Well all, it happened: bootable backup clones with CCC are gone. At least for me with CCC 6.0.4 and Monterey.
I just had a long and not very pleasant email dialogue with Mike Bombich about my recent attempt to clone my Monterey install. It failed, and Mike pointed out that this will happen much more in the future as many of us knew - because this is what Apple wants.
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.
His recommendation was try plan B: Plan B for a simple bootable backup is kind of a nightmare, which, if you read below, he fullly admits. First, you install your OS on your projected clone. (In my case, that took a LONG time on a very fast NVME drive). Then your best bet is to use migration assistant to migrate all your settings to your bootable backup clone. Again, that takes a dreadful amount of time.
Now I have done this and I'm looking at about three hours. And remember, every time Apple upgrades its code, you will have to upgrade this way. Imagine that....
How do you quickly recover from a failure? Well, he actually has no answer for that.....
More from our dialogue:
MIKE: "No, I'm actually suggesting that you stop doing that."
MIKE: "I agree! Please, stop doing it this way! Don't make bootable backups, make Standard Backups instead (i.e. the "default settings"). This is precisely the experience that I'm trying to have people avoid, this is why I'm trying to convince people to stop trying to make the backup bootable. What do you have when this is complete? Is the bootable backup substantively better than a Standard (non-bootable) backup? No, it's marginally better at best, and given the hassle that you have to go through to make and keep it bootable, I think it's now worse."
The problem that Mike deftly avoids is the situation wherein you need to complete a project and you can't because of disk failure. If you could boot your backup, you could do what's needed to complete it.
But sure, if you have multiple Macs sitting around doing nothing and you have the backup of the project you could just move the project over to your excess machine (Well, sure I have a couple of Mac Pros just sitting around waiting for me to use them). You do too, right?
You know this sounds like a ploy by Apple to make sure they can sell more hardware. Because if you've got a critical project, you have to have two Mac Pros (or two of any Mac hardware). And they have to be mirrored and exactly the same. Then and only then can you trust that if you move a project from a failed Mac to another Mac, you can count on being able to continue uninterrupted.
Hi Juan, my issue with Ethernet is this: no network! the driver is installed but don't works correctly! see the pictures.Hi fellow vision-g user, I have question:
How the ethernet issue looks like? no ethernet at all or is it just a downgrade from 2.5Gbit to 1Gbit?