Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Error 49244 during using of ASR or Disk Utility
- Thread starter bobak
- Start date
-
- Tags
- asr
- Sort by reaction score
No, I've not tried these. And I'm not interested in using of 3rd part utilities. I need to use only built-in ones
macOS Big Sur and later uses a Signed System Volume to protect most system content. This is implemented as a sealed snapshot on the system volume. In order for the clone to boot successfully, this snapshot must be copied over exactly as is. I am not sure wether Disk Utility actually allows for access to the sealed snapshot (name and UUID)?.
The good news: ASR can do it.
Make sure to have…
- Replace
- Replace
You can do this from macOS Recovery too - then the “sudo” from the start of the command sequence above isn’t needed.
Or… you simply use e.g. CCC or SD - which offer a GUI wrapper to AST - recommended and pointed out by @Fishrrman 😎
The good news: ASR can do it.
Make sure to have…
- sufficient space on the destination disk.
- you have full disk access permissions for Terminal. This is required for ASR to successfully clone the running macOS system, at least in macOS Ventura and later.
- identified correctly your source and target using diskutil - importantly the startup snapshot and UUID.
- your destination is a Apple File System (APFS) Container that will hold your new clone on the external SSD. You can clone your source system to the same drive that holds it, but you'll likely need macOS Recovery's Terminal for that.
- assembled in the Terminal the specific ASR command that you’ll use. Something along the lines of:
sudo asr restore --source /dev/sysvol --target /dev/yourTarget --toSnapshot sysSnap --no-personalization --erase.
sysvol with the source system volume’s disk ID- Replace
yourTarget with the disk ID for the target volume or container.- Replace
sysSnap with the UUID or name of the source system snapshot.You can do this from macOS Recovery too - then the “sudo” from the start of the command sequence above isn’t needed.
Or… you simply use e.g. CCC or SD - which offer a GUI wrapper to AST - recommended and pointed out by @Fishrrman 😎
Last edited:
slart observed:
"Or… you simply use e.g. CCC or SD - which offer a GUI wrapper to AST - recommended and pointed out by @Fishrrman"
The guy seems to have some beef with using 3rd party applications.
He could download SuperDuper and have the job done in five minutes -- FOR FREE.
"Or… you simply use e.g. CCC or SD - which offer a GUI wrapper to AST - recommended and pointed out by @Fishrrman"
The guy seems to have some beef with using 3rd party applications.
He could download SuperDuper and have the job done in five minutes -- FOR FREE.
"Create a bootable external hard drive using ASR via terminal on macOS Monterey"
https://www.prosofteng.com/blog/how-to-create-a-bootable-external-hard-drive-clone-on-macos
https://www.prosofteng.com/blog/how-to-create-a-bootable-external-hard-drive-clone-on-macos
For free? Yeaahh, of course. "Smart update, copy newer, copy different modes are only available in the registered version"
Yes, SuperDuper IS free, if you wish to clone THE ENTIRE DRIVE.
It will do this over and over again, and you don't have to register.
However...
If you wish to do "incremental" backups, then you have to register.
Why don't you just give it a try?
CCC (on the other hand) is fully functional for 30 days.
Then you have to register.
It will do this over and over again, and you don't have to register.
However...
If you wish to do "incremental" backups, then you have to register.
Why don't you just give it a try?
CCC (on the other hand) is fully functional for 30 days.
Then you have to register.
Can you post the result of diskutil list ?
I’ve successfully cloned Monterey from a VM to an external SSD with
Code:
sudo asr restore --source /dev/disk1s3 --target /dev/disk3s1 –eraseIn your case, from the last image, it probably should look like this
Code:
sudo asr restore --source /dev/disk1s3 --target /dev/disk5s1 –erase
Kind of curious as to why you're doing screen shots with an external tool rather than the built-in screen capture commands.
It's hard to explain now. Just as is. I know I can use internal tool but it's about enterprise policies.
Have you run First Aid on the external disk?
Apple: "Repair volumes, then containers, then disks"
https://support.apple.com/HT210898
EN https://support.apple.com/en-us/HT210898
Apple: "Repair volumes, then containers, then disks"
https://support.apple.com/HT210898
EN https://support.apple.com/en-us/HT210898
Dude, I've already checked several different external disks. I'm always getting the same error as I said in my first post.
And I never got this error when I did imaging on Intel Macbook. So this error has connection with CPU type as I think.