OSStatus error 49153 using Disk Utility > Restore to make a bootable USB copy of Macintosh HD

Hello. I have a MacBook with a 256GB internal SSD which is setup with a GUID partition map and APFS. I also have a 256GB USB stick which I've formatted in Disk Utility to also be GUID partition map and APFS.


I want to clone the HD onto the USB to make a bootable copy. When I choose the USB in Disk Utility and click restore, then select the Mac HD as the source I get 'OSStatus error 49153' after a few seconds. See screenshot. Has anybody got any ideas why this isn't working? I'm on Monterey.


I've tried clicking restore from the volume, the container and the physical device, all give the same error.


MacBook, macOS 12.6

Posted on Oct 10, 2022 06:33 AM

Reply

Similar questions

4 replies

Oct 10, 2022 01:04 PM in response to Torshen

Since recent macOS versions reside on a separate, read-only volume independent from the startup drive containing your User Accounts, I surmise Restore fails because it cannot partition the USB stick to conform to that requirement.


Creating a bootable device requires that you boot macOS Recovery and choose its "Reinstall" option: How to reinstall macOS - Apple Support. Designate the USB flash drive as its destination. Following that, it will ask the Setup Assistant will ask if you want to transfer content from a Mac (or its Time Machine backup; makes no difference) so do that also.


That — should — effectively create a duplicate of your existing installation. Caveat only because I haven't tried it with a USB stick recently. The last time I did, its performance was unacceptable. USB flash drive read / write speeds vary tremendously. External SSDs (as opposed to commonly available USB flash drives) work well, and the above procedure is what I do.

Oct 10, 2022 01:56 PM in response to John Galt

Thanks, appreciate the explanation. That sounds pretty annoying. Why have the functionality there if it doesn’t work? Reading a drive, even the OS drive, shouldn’t ever be an issue. How else could the computer function, it’s reading data constantly anyway.


I did already try doing the same thing from recovery mode and got the same errors, but the steps you’ve listed are different to what I tried. I just booted into recovery and tried to clone (sorry, “restore”) the drive.


There are 3rd party apps like Carbon Copy Cloner and others that claim to be able to create bootable copies from inside Max OS (IE not recovery mode), really didn’t think this would be so difficult when, on the face of it, the functionality is built into Disk Utility.


Anyway thanks for explaining it. I guess I’ll give up and just rely on time machine as my one and only solution then.

Oct 10, 2022 07:02 PM in response to Torshen

Apple Software Restore (ASR) aka Restore only recently became capable of cloning the startup volume.

It will clone other volumes--that's why it is there.

CCC was unable to clone the sealed system volume until Apple made ASR capable of doing so.

It's quite possible you may have to use asr in Terminal. However, this is an excerpt from the man page:


RESTORING WITH APFS FILESYSTEMS
Individual APFS volumes can not be restored directly, because their device nodes don't allow I/O from a standard process. However, asr can restore entire APFS containers, including all volumes. Or it can restore valid system configurations, which can get the effect of restoring a single system. This requires understanding what is meant by a valid system.

In order for an APFS volume to be bootable, it must contain a properly installed macOS system. It must also be part of an APFS container which also has two special volumes in it: a Preboot volume and a Recovery volume. A container may have arbitrarily many system volumes in it, but it must have only one Preboot volume and one Recovery volume, each with the corresponding APFS volume role set (see diskutil(1) for information on roles). The Preboot and Recovery volumes contain information which is tied to each system volume in the container. So for a system volume to be bootable, that information needs to be set up in the Preboot and Recovery volumes. A system which is part of a container that has these two special volumes, and for which the requisite information is set up in those volumes, will be referred to here as a valid system.


So, perhaps try Restoring the container, not the individual volumes.

Oct 11, 2022 09:12 AM in response to Torshen

Disk Utility has never been a good choice to use for cloning a bootable macOS drive. I tried it years ago before the added security features. Only Carbon Copy Cloner or SuperDuper are known to be reliable for cloning a macOS boot drive. However, like the others have mentioned, even the developers of these third party apps are no longer recommending bootable clones. In fact there are numerous posts on these forums where it may no longer work on Macs with Apple Silicon after a recent Monterey update. Here is what Michael Bombich (developer of CCC) has to say on the matter and instructions on how to attempt a bootable clone (legacy mode option):

https://bombich.com/kb/ccc6/cloning-macos-system-volumes-apple-software-restore


I'm not really sure why Apple even included the Restore option in Disk Utility since it is very limited. The only time I've ever seen it used was for creating a bootable USB drive/stick from a bootable .dmg image which was sometimes used for creating a bootable diagnostic USB drive or possibly for burning CDs.


Also, you mentioned USB stick as opposed to drive (SSD or hard drive). Unless you have one of the expensive sticks which can actually write data at 200+ MB/s, then booting from a USB stick will be extremely slow & painful.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

OSStatus error 49153 using Disk Utility > Restore to make a bootable USB copy of Macintosh HD

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.