|
#1
|
||||
|
||||
That's not going to work - the user info held in the hidden volumes won't match what's in the data. You'd have to migrate for that...or you might be able to force a sync.
Can't you install your Ventura version from Recovery? That's the way to do it, typically, not by using an installer.
__________________
--Dave Nanian |
#2
|
|||
|
|||
(Talking about idea #2: erase-then-copy followed by a macOS update to get the dyld cache fixed...)
The macOS downgrade issue is a moot point now since Apple posted Ventura 13.6.3 to the App Store. But I'd think I'd better apply the 13.6.3 update to the internal drive first, in case running the 13.6.3 full installer also does a firmware update. What do you mean by "force a sync"? I'll try the reinstall from macOS Recovery. Note: based on previous experience, I'm not sure this will even work. That is, I think it will make the clone bootable, but then won't allow turning on FileVault. |
#3
|
|||
|
|||
Did another erase-then-copy, tried to startup from it, but it goes through the same authorize users, set owner loop as previously described. Which is weird, since this worked the first time I tried an erase-then-copy.
Do I need to completely erase (repartition) the drive to clear out whatever hidden data is there? What I did was erase the APFS container in that partition, changing it to HFS+, then erase that and create as APFS. |
#4
|
||||
|
||||
There's no need to change things to HFS+. I would erase the whole drive, from the hardware (top), and format as APFS from the get-go.
__________________
--Dave Nanian |
#5
|
|||
|
|||
FWIW I had no problem creating a bootable clone on an m3 iMac. I created an APFS volume on an external SSD, then did an erase and copy all files with SD. Upon completion, I booted to the volume, turned on FileVault, let it run for a while and then booted back to the internal drive.
|
#6
|
|||
|
|||
Quote:
Did it ask you to authorize a user and select an owner? |
#7
|
|||
|
|||
Quote:
|
#8
|
|||
|
|||
Same authorize/owner loop as before.
I did this:
|
#9
|
||||
|
||||
Maybe your users on the internal drive are bad? You may want to consider reinstalling the OS to the internal (pretty basic and non-destructive) from Recovery.
__________________
--Dave Nanian |
#10
|
|||
|
|||
I got past the authorize/owner loop. I did two things differently:
This time it didn't ask me to set an owner, only to authorize a user account. The restart crashed (dyld cache), so I used macOS Recovery to reinstall Ventura on the backup drive. And it worked! It booted from the backup SSD (Ventura 13.6.2, same as on internal drive), and I could start FileVault encryption -- when I got that far once before with the HD backup, FileVault gave an error. This does make me wonder: if the authentication/owners loop was due to either needing to reboot or wait for Spotlight, what would have happened when I did the SuperDuper! Smart Update on top of the clean macOS install, if I had rebooted and waited? Same error or something else? Anyway, next milestone will be if it survives a Smart Update. I'd think it will. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Bootable Intel backups on Apple Silicon? | revans | General | 1 | 06-20-2023 06:52 PM |
Windows equivalent to SuperDuper!? | jreffner | General | 21 | 08-13-2009 05:36 PM |
inner vs. outer partition; bootable clone partition size; Why not back up Sandbox? | LearningUser | General | 1 | 06-22-2009 07:01 AM |
Clone Not Bootable | slickmrick | General | 11 | 08-12-2006 12:08 PM |
Creating a pristine clone | 2stepbay | General | 4 | 03-13-2006 08:40 AM |