Hi I just purchased Winclone 8 today. I have a 2012 MBP running Mojave and Windows 10 in the bootcamp partition. Size of the bootcamp partition is 249 GB and Windows 10 etc currently occupies 33.04 GB of that. I want to create a backup/clone of my Bootcamp on an external HD which is 80GB in size and formatted to MS-DOS (FAT32). My attempt to perform a volume to volume cloning gives me the error “There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks”. I need help please. Thanks.
I am new to Winclone. I assumed I could clone my Windows 10 bootcamp partition to an external HD so if I ever lost my bootcamp I could recreate it from the clone.
Does the external drive have to be the same size as the bootcamp partition, or just large enough for the space used?
What kind of problem would there be with one of the volumes or the disks?
OK so I’m a little further along now. I used a different external HD, 340GB, and I formatted it to MS DOS (GUID partition map).
All went well… until I got this error message:
‘The Windows partition could not be mounted Read/Write to create the boot folder at the root of the Windows partition. Mount the Windows partition Read/Write, delete hiberfil.sys, and then try setting legacy bootable manually.’
Please could someone explain what this means, and how I go about it? Thanks.
Was Windows installed via Boot Camp assistant? That last step is trying to fix an issue from a non-standard setup of Windows. You can try selecting Tools->Make EFI Bootable and rebooting and seeing if it works. That error comes are all data has been restored.
tim
Yes it is windows 10 installed using bootcamp in Mojave on a mid-2012 MBP.
I have no idea what you are talking about, sorry. Select Tools… where? And reboot, what?
The error message … does that mean I have a clone which is unuseable?
I know I sound as thick as two short planks but I’ve never used Winclone before. I thought it would just create a clone I could keep as a backup. Thanks.
In Winclone, there is a Tools menu. Select the menu, then select Make EFI bootable. Then select your boot camp partition.
Then select the Boot Camp partition in Startup Disk preference pane and restart the Mac into Windows.
tim
Thank you but I am completely out of my depth here.
I am in the same boat here…
I have a MacBook Pro (Retina, 15-inch, Mid 2015)
Upgraded to Catalina and upgraded VMWare Fusion without lic for old Mac.
I have got VMWare Win10 / Bootcamp to come up and have re-installed vmTools, and all is working.
I am now attempting to use 2C to copy the Win10 over to a 500 or 1TB drive.
Waiting to boot up new MacBookPro 16 inch to do TimeMachine restore and pay for VMWare Fusion 11.5
Starts to do it’s thing but gives me this:
There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks.
Log Errors
Accounting clusters …
Cluster accounting failed at 19081465 (0x12328f9): extra cluster in $Bitmap
Cluster accounting failed at 19081466 (0x12328fa): extra cluster in $Bitmap
Cluster accounting failed at 19081467 (0x12328fb): extra cluster in $Bitmap
Cluster accounting failed at 19081468 (0x12328fc): extra cluster in $Bitmap
Cluster accounting failed at 19081469 (0x12328fd): extra cluster in $Bitmap
Cluster accounting failed at 19081470 (0x12328fe): extra cluster in $Bitmap
Cluster accounting failed at 19081471 (0x12328ff): extra cluster in $Bitmap
Cluster accounting failed at 19081472 (0x1232900): extra cluster in $Bitmap
Cluster accounting failed at 19081473 (0x1232901): extra cluster in $Bitmap
Cluster accounting failed at 19081474 (0x1232902): extra cluster in $Bitmap
Totally 68 cluster accounting mismatches.
ERROR: Filesystem check failed! Windows wasn’t shutdown properly or inconsistent
filesystem. Please run chkdsk /f on Windows then reboot it TWICE.
, exitCode=1, NSLocalizedDescription=There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks.}
2019-12-20T20:21:43-06:00:Setting the system to allow sleep…
2019-12-20T20:21:48-06:00:Helper tool error: There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks.
another log:
2019-12-21T12:05:01-06:00:Preparing disk-to-disk clone
2019-12-21T12:05:02-06:00:Setting to not sleep…
2019-12-21T12:05:05-06:00:Winclone Helper Tool starting restore.
2019-12-21T12:05:07-06:00:Executing “ntfsclone -f -O /dev/disk2s3 /dev/disk0s3”
2019-12-21T12:05:07-06:00:ntfsclone v2017.3.23 (libntfs-3g)
2019-12-21T12:05:07-06:00:NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 196435066880 bytes (196436 MB)
2019-12-21T12:05:07-06:00:Starting Disk To Disk Imaging, 0.000000% complete
)
ERROR(13): Opening file ‘/dev/disk2s3’ failed: Permission denied
2019-12-21T12:05:08-06:00:Last message repeated 1 times
2019-12-21T12:05:08-06:00:Helper tool error: There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks.
2019-12-21T12:05:10-06:00:Error Error Domain=TaskError Code=5 “There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks.” UserInfo={standardError=ntfsclone v2017.3.23 (libntfs-3g)
, standardOutput=NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 196435066880 bytes (196436 MB)
Current device size: 196435070464 bytes (196436 MB)
ERROR(13): Opening file ‘/dev/disk2s3’ failed: Permission denied
, exitCode=1, NSLocalizedDescription=There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks.}
2019-12-21T12:05:10-06:00:Setting the system to allow sleep…
2019-12-21T12:05:40-06:00:Mounting Error: An timeout occurred when mounting /dev/disk2s3. Please check that you can mount the volume in Disk Utility and try again
Additional Info: Error occurred at TCSPrivHelperToolController.m:479
2019-12-21T12:05:40-06:00:Mounting Error
2019-12-21T12:05:40-06:00:Helper tool error: There was an error during the disk to disk clone. There may be a problem with one of the volumes or the disks.
Yes, it is related to disk errors. Make sure to run chkdsk:
tim