Broken Pipe Error Write:330 Write:340
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
I've been using veracrypt on arch linux for a quite a long time now and i've never had issues such as these. But i believe since i updated to 1.21 i've been getting an error every time i try to mount ANY of my volumes. I've tried uninstalling removing all the files pertaining to it and reinstalling, but the problem persists. When i try to mount my volume i get one of 2 error messages but 9 out of 10 times it still mounts correctly and the information on it doesn't seem to be corrupted. the error reads:
Not enough data available.
Most of the time i get this the first time i try to mount after a reboot or sleep. I also get this to when i try to dismount after using umount in the terminal to force the volume to dismount because veracrypt refuses to do it now. When i try to do it in veracrypt i get this error message:
Broken pipe
VeraCrypt::File::Write:340
i believe originally i was seeing the same message with 330 instead. But now i seem to be consistantly getting 340.
I can also only sometimes create new volumes(it seems completely random), i tried to just create a new one and dump my files onto it if the errors would stop on a new volume but half the time i can't even create a new volume it fails with one of the 2 errors i've posted, during the creation stage or if it does complete i can't even mount it initially (to transfer anything on to it) giving me one of the 2 errors above but different than my original volume the new ones don't seem to mount at all, and my old one will mount usually even though i get the error popup...
Please if someone can help me figure out what to do to get veracrypt working again, I really like this solution over the one i'm being forced to use in place of this in case my data isn't safe (those error messages scared me into creating backup files for the most important ones and use gnupg to encrypt them and re-encrypt them everytime they are edited... Constantly)
Last edit: A S 2017-11-14
I don't know if this is a real work around or not. But i figured i would post this in case anyone else has this issue and found this.
Running veracrypt as root (or sudo or gksu or gksudo) seems to fix the problem completely.
So my guess is that it could have something to do with veracrypt asking for root privileges to use mount, or the /mnt dir...? I've never had any issues with this in the past. A popup has always come up and asked for the rights to mount the volume... I don't really like the idea of having to run it this way all the time... I might see if it's possible to mount it someone in my home dir so it doesn't need permission for anything...