Process failed and succeeded. :( And my data isn't being protected

I’ve run into a repeatable issue that I can’t seem to work around. Its rendered the Winclone 8 unusable.

I’ll start imaging my bootcamp partition (with an eye towards changing the split between Catalina and WinX) and I run into an unhelpfully vague error message. “There was an error while block imaging. Please check the volume and try again.” The process resumes when I click ok and then I’m told “image completed successfully” which is a FLAT OUT LIE. Maybe the process completed normally, but the proceedure was a FAILURE!

So what am I supposed to check for? What happened? I check the drive and find nothing amiss, nothing wrong as far as I can detect. So I go to your log file and I find this line at the point of failure.

pigz: abort: write error on <stdout> (File too large)

No supporting data about WHAT FILE is too large. This failure occurs at around the 30% point every time. So, the image isn’t viable, my data isn’t protected, and the process isn’t repairable.

If you don’t tell me whats wrong, and don’t log what file you tripped up on, how can I be expected to fix the issue?

2020-06-13T17:30:02-05:00:===============================================
2020-06-13T17:30:55-05:00:hiberfil exists...probing...
2020-06-13T17:31:00-05:00:Found BOOT folder or boot.ini so we have a standard Windows bootable Windows partition
2020-06-13T17:31:13-05:00:Setting to not sleep....
2020-06-13T17:31:13-05:00:Writing Version of Windows to Image
2020-06-13T17:31:14-05:00:Starting Helper Tool 
2020-06-13T17:31:14-05:00:setting up listener for mach service com.twocanoes.WincloneHelper
2020-06-13T17:31:14-05:00:Getting new connection request
2020-06-13T17:31:15-05:00:Saving Partition Type, 2.000000% complete 
2020-06-13T17:31:15-05:00:Could not read /dev/disk0.  Probably due to SIP.  Ignoring and returning 0x07
2020-06-13T17:31:15-05:00:Saving Filesize, 3.000000% complete
2020-06-13T17:31:16-05:00:Executing "ntfsinfo -m -f -f /dev/disk0s3"
2020-06-13T17:31:17-05:00:Removing Pagefile, 4.000000% complete
2020-06-13T17:31:18-05:00:Executing "ntfscp -f /dev/disk0s3 /var/folders/vq/_krv9ty10yxdxbp76zxcfj6w0000gn/T/winclone.tmp.5SVg5mZj pagefile.sys"
2020-06-13T17:31:20-05:00:Executing "ntfslabel -f -f /dev/disk0s3"
te
2020-06-13T17:31:21-05:00:Saving Image, 5.000000% complete
2020-06-13T17:31:21-05:00:Executing "ntfsclone --save-image --force --output - /dev/disk0s3"
2020-06-13T17:31:21-05:00:Executing "pigz --stdout --force"
2020-06-13T17:31:21-05:00:ntfsclone v2017.3.23 (libntfs-3g)
2020-06-13T17:31:21-05:00:Scanning volume, 10.001000% complete
2020-06-13T17:31:24-05:00:Scanning volume, 11.001500% complete
2020-06-13T17:31:26-05:00:Scanning volume, 12.002500% complete
2020-06-13T17:31:29-05:00:Scanning volume, 13.003000% complete
2020-06-13T17:31:31-05:00:Scanning volume, 14.004000% complete
2020-06-13T17:31:34-05:00:Accounting clusters ...
2020-06-13T17:31:34-05:00:Space in use       : 74090 MB (37.0%)
2020-06-13T17:31:34-05:00:Saving NTFS to image ...
2020-06-13T17:31:34-05:00:Saving NTFS to image, 20.007999% complete
2020-06-13T17:31:41-05:00:Saving NTFS to image, 21.016001% complete
2020-06-13T17:31:49-05:00:Saving NTFS to image, 22.024000% complete
2020-06-13T17:31:57-05:00:Saving NTFS to image, 23.032000% complete
2020-06-13T17:32:05-05:00:Saving NTFS to image, 24.040001% complete
2020-06-13T17:32:13-05:00:Saving NTFS to image, 25.048000% complete
2020-06-13T17:32:21-05:00:Saving NTFS to image, 26.056000% complete
2020-06-13T17:32:29-05:00:Saving NTFS to image, 27.063999% complete
2020-06-13T17:32:37-05:00:Saving NTFS to image, 28.072001% complete
2020-06-13T17:32:46-05:00:Saving NTFS to image, 29.080000% complete
2020-06-13T17:32:54-05:00:Saving NTFS to image, 30.087999% complete
2020-06-13T17:32:59-05:00:pigz: abort: write error on <stdout> (File too large)
2020-06-13T17:33:01-05:00:Helper tool error: There was an error while block imaging. Please check the volume and try again.
2020-06-13T17:33:16-05:00:Setting the system to allow sleep...

This is usually related to file system or file issues. Try running CHKDSK /b and see if it resolves any disk related errors.

tim

Chkdsk and Disk Utility both reported no errors, either on the source or destination drives.

It wasn’t until this morning that I was able to get around this roadblock.

Suffering from not enough free space in both MacOS and Windows portions of the fixed internal storage on my MacBookPro, I was trying to use an external drive. I did not go out and purchase a new one when I had almost all of a 4TB drive free. This is where my problem starts.

1. Your software allowed me to select an external drive partitioned with a file scheme that does not permit single files larger than 4 GBs in size. You should be testing for this when the estimated image size exceeds 4 GB. Backups that fail in data capture are worthless after all.

2. The error message logged was so vague that even your response did not lead you to actual cause of failure. The file being written to the external drive hit the single file size limit and returned a ‘drive full’ style error.

3. having no other means available to clear enough working space on a partition that allows for larger file sizes I had to uninstall, archive, move, and otherwise disorganize the contents of my Mac in order to make the room for the image on the internal storage. After that I was able to complete the backup, but now I’m trying to figure out how to get the image off the system so I can make the needed partitioning changes before restoring.

I hope the software engineers take notice of this thread. Using an external drive is the ONLY real option for most MacBooks these days, I hope the next revision takes my experience in account with how the setup handles the selection process and error reporting. There has to be a better way than this.