I apologize for the delay, it took me some time to get to a position to test this again. By the time I tested, I saw 3.1.3-16 was already available as 'stable'. I tried with that version and no longer have this issue. It seems to be resolved now. Thanks!
Did you choose to encrypt the saved image? It's the combination of the source disk being LUKS, the destination being SMB share, and choosing to encrypt the saved image.
Yes, I tried with 3.1.3-11 and still had the same issue. I was going to grab a log file, but I couldn't find the log that had this line in it. It wasn't in the /var/log/clonezilla.log You can see the point of failure between the two screenshots. When saving to a local disk, you can see right after I enter my password for the existing LUKS volume, it says it's saving the LUKS header and then has no error message. However, when I'm saving to an SMB share, after I enter the password and it runs the...
Yes, I tried with 3.1.3-11 and still had the same issue. I was going to grab a log file, but I couldn't find the log that had this line in it. It wasn't in the /var/log/clonezilla.log You can see the point of failure between the two screenshots. When saving to a local disk, you can see right after I enter my password for the existing LUKS volume, it says it's saving the LUKS header and then has no error message. However, when I'm saving to an SMB share, after I enter the password and it runs the...
Yes, I tried with 3.1.3-11 and still had the same issue. I was going to grab a log file, but I couldn't find the log that had this line in it. It wasn't in the /var/log/clonezilla.log You can see the point of failure between the two screenshots. When saving to a local disk, you can see right after I enter my password for the existing LUKS volume, it says it's saving the LUKS header and then has no error message. However, when I'm saving to an SMB share, after I enter the password and it runs the...
Is there any update on this issue? I am still having this problem with 3.1.2-22; and it's as Steven noted where if I'm backing up to a SMB share, it will fail with the error that it can't find the LUKS header file (same as all above screenshots). However, if I backup to another attached disk, it will work without issue. I set it up to open the LUKS container, encrypt the clone, and save to the SMB share and it fails every time.
Unfortunately after rebooting with Hibernate disabled, it still thinks there's a password cached at boot. Edit: I was able to figure out the issue. I started digging through all of the configuration pages. There was a setting in "System Favorite Volumes" to mount system favorites when Windows starts. Somehow this setting was enabled, even though I never use this feature. When I clicked the checkbox to disable the feature, VeraCrypt gave me an error message. It was to the effect of a certain service...
Unfortunately after rebooting with Hibernate disabled, it still thinks there's a password cached at boot.
"Start VereCrypt Background Task" is on; but "Mount all devices-hosted VeraCrypt volumes" is off.
I should have noted I also already turned that off - otherwise booting takes about 20 minutes.
I have Windows 10 with system drive encryption, on a BIOS boot. VeraCrypt is version 1.22 I also have different volumes that I mount after booting into Windows that have a separate password. Typically, when I would try to mount the other volumes, it would immediately ask me for the password - as expected. However, I've upgraded to Windows 10 version 1803, using this method: https://github.com/th-wilde/veracrypt-w10-patcher Ever since the upgrade, it seems that VeraCrypt is caching the password for...
I have Windows 10 with system drive encryption, on a BIOS boot. I also have different volumes that I mount after booting into Windows that have a separate password. Typically, when I would try to mount the other volumes, it would immediately ask me for the password - as expected. However, I've upgraded to Windows 10 version 1803, using this method: https://github.com/th-wilde/veracrypt-w10-patcher Ever since the upgrade, it seems that VeraCrypt is caching the password for the system drive, even though...
Request: Find out what reads/writes address