Contribute
Register

Monterey cloning NVMe not working

Status
Not open for further replies.
Joined
Sep 14, 2014
Messages
22
Motherboard
Gigabyte Z170X-UD3
CPU
i7-7700K
Graphics
HD 630
After a recent updated from Catalina to Monterey my Samsung NVMe drive was slow to boot, so I decided to upgrade to a recommended WD Black SN770.

Problem is, I cannot get a clone operation to complete with success, fails early in the clone operation. I have tried CCC, SuperDuper, and Disk Utility from recovery. All fail at about the same time. Both NVMe drives are same 1TB size and installed on the M/B. Both measure good healthy speeds from within Monterey.

Here's a log from SuperDuper. Feels like I am missing something... Any ideas? Thanks!

| 01:38:29 PM | Info | SuperDuper! Version 3.7.5 (131-4cb66b9), path: /Applications/SuperDuper!.app, load address: 0x104b19000 | 01:38:29 PM | Info | Started on Sat, Feb 25, 2023 at 1:38 PM | 01:38:29 PM | Info | Source Volume: "NVMe" mount: '/' device: disk2s5s1 file system: 'APFS' protocol: PCI-Express macOS: 12.6.3 (21G419) capacity: 1 TB available: 60.51 GB files: 367,173 directories: 128,027 | 01:38:29 PM | Info | Target Volume: "WD_BLACK" mount: '/Volumes/WD_BLACK' device: disk3s1 file system: 'APFS' protocol: PCI-Express capacity: 1 TB available: 978.25 GB files: 2,056 directories: 289 | 01:38:29 PM | Info | Copy Mode : Erase, then copy files | 01:38:29 PM | Info | Copy Script : Backup - all files.dset | 01:38:29 PM | Info | Transcript : ReplicateTranscript.plist | 01:38:30 PM | Info | PHASE: 1. Prepare to Copy Files | 01:38:31 PM | Info | ...ACTION: Erasing WD_BLACK | 01:38:32 PM | Info | ......COMMAND => Erasing WD_BLACK | 01:38:32 PM | Info | Erasing standalone volume | 01:38:32 PM | Info | Unmounting /dev/disk3s1 mounted on /Volumes/WD_BLACK | 01:38:39 PM | Info | Volume WD_BLACK on disk3s1 unmounted | 01:38:39 PM | Info | Started erase | 01:38:39 PM | Info | Preparing to erase APFS Volume content | 01:38:39 PM | Info | Checking mount state | 01:38:39 PM | Info | Erasing APFS Volume disk3s1 by deleting and re-adding | 01:38:39 PM | Info | Deleting APFS Volume from its APFS Container | 01:38:39 PM | Info | Unmounting disk3s1 | 01:38:39 PM | Info | Erasing any xART session referenced by 2A00141D-9398-4BCA-94D4-AC4732381BF9 | 01:38:39 PM | Info | Deleting Volume | 01:38:39 PM | Info | Removing any Preboot and Recovery Directories | 01:38:44 PM | Info | Preparing to add APFS Volume to APFS Container disk3 | 01:38:44 PM | Info | Creating APFS Volume | 01:38:45 PM | Info | Created new APFS Volume disk3s1 | 01:38:45 PM | Info | Setting mount state | 01:38:45 PM | Info | Setting volume permissions | 01:38:46 PM | Info | Finished erase | 01:38:46 PM | Info | PHASE: 2. Copy Files | 01:38:47 PM | Info | ...ACTION: Copying files from NVMe to WD_BLACK | 01:38:47 PM | Info | ......COMMAND => Replicating NVMe to WD_BLACK | 01:38:47 PM | Info | Initializing | 01:38:47 PM | Info | done | 01:39:01 PM | Info | done | 01:39:12 PM | Info | Couldn't set up partitions on target device - operation UnmountPartition, line #5420 - Resource busy | 01:39:14 PM | Error | ***ERROR OCCURRED: ****FAILED****: result=256 errno=60 (No such process)
 
I am not 100% sure. From what I remember, cloning Mac disk stopped working a few versions back of MacOS because of APFS.

I never had any issue *copying* an install. It's almost like cloning...

1) Install a fresh copy of MacOS on the New drive. (Make sure it boots).
2) Now you can use TimeMachine or Migration Assistant or CCC to move the files to the new drive.

It's a 2 step process but it has worked for me.

That's how I moved from SATA SSD, to a 250GB NVME and then to a 1TB NVME.
 
I am not 100% sure. From what I remember, cloning Mac disk stopped working a few versions back of MacOS because of APFS.

I never had any issue *copying* an install. It's almost like cloning...

1) Install a fresh copy of MacOS on the New drive. (Make sure it boots).
2) Now you can use TimeMachine or Migration Assistant or CCC to move the files to the new drive.

It's a 2 step process but it has worked for me.

That's how I moved from SATA SSD, to a 250GB NVME and then to a 1TB NVME.
Thanks. I have read there was a recent APFS period where SuperDuper was not working, but is supposed to be compatible now. I also tried the Disk Utility in recovery mode.

If all else fails, I will go the TimeMachine route.
 
Status
Not open for further replies.
Back
Top