redbaron192

Hiya, I've just noticed a new minor issue - Using a space character in the image folder name stops it from being listed when you do the recoverdisk process. i.e. "2025-08-16-11-imgext4-latest" would be listed in the recoverdisk image selection dialog, whereas "2025-08-16-11-imgext4 latest" would not be. currently using "clonezilla-live-3.2.3-6-amd64"

Hiya, 20GB/min verify speed.... very nice indeed :o) Some feedback on the ISO... Using Ubuntu 22.04.5LTS, I could not get "Etcher-linux-x64-2.1.2.zip" to create a usable USB stick at all with the "clonezilla-live-3.2.3-6-amd64.iso" In the end I switched over to my Windows 10 and used Rufus 4.6. Rufus reported that the ISO file had two ways of being put onto a USB stick, either as a ISO copy or a Direct Image. Only the ISO copy method worked. Cheers. Sent with Proton Mail secure email. On Sunday,...

Backup filename containing () causes crash with unexpected token

Hiya, I got a failure this morning doing a backup with my new setup. I immediately repeated the backup process and the second time it verified successfully. I have the all log files for both attached. The files from the first failed attempt (backup named 2025-04-29-08-imgWin10good) are all before time 09:11:00. All files after 09:11:00 are from the second successful attempt (backup named 2025-04-29-08-imgWin10again). Both backups used identical source & target drives. I just did a comparison of both...

Hi Steven, Been doing some more testing of my verification issues (previous comment 2025-02-21)... For faster backups I switched to using a new internal NTFS SSD instead of the external NTFS USB drive (This took USB out of the equation as well). It doubled my backup speed but still got occasional CRC verification failures. I know from experience that writing NTFS from Linux can cause NTFS FS corruption so I decided to make my Clonezilla target EXT4 instead of NTFS (to rule out any NTFS FS issues)....

Hi Steven, Been doing some more testing of my verification issues (previous comment 2025-02-21)... For faster backups I switched to using a new internal NTFS SSD instead of the external NTFS USB drive (This took USB out of the equation as well). It doubled my backup speed but still got occasional CRC verification failures. I know from experience that writing NTFS from Linux can cause NTFS FS corruption so I decided to make my Clonezilla target EXT4 instead of NTFS (to rule out any NTFS FS issues)....

Using Ubuntu 22.04.5 LTS OS. Bug occurs in 1.26.18. I just tried 1.26.20 and it occurs in there as well. veracrypt has been working fine since installation (I've never had a bug in veracrypt). I'm not sure if there was a Ubuntu OS update in the last 24 hours (15/03/2025@1617) or not to cause this. It was working the other day. My veracrypt archive is on a USB 2.0 stick (file system on stick is ExFAT 1.0). Filesystem within the veracrypt archive is NTFS (i think). I also run the same veracrypt version...

I know this is an old thread but it saves creating a new issue.... I use a Clonezilla Live boot-able DVD. From past experience I always do a verify image for every SaveDisk, so that I know what I have backed up is going to work should I need to restore. My backups are sourced from a laptop internal 256GB SSD containing 10 partitions, split between Win10 NTFS, a couple of Ubuntu Ext4 and a NTFS data partition, plus the usual small partitions to support Windows and efi\grub booting etc... totaling...