I have the same error with DejaDup in Ubuntu 16.04.
I am trying to run a backup (not restore!), and got this error:
Ni mogoče brati /tmp/duplicity-gUZKem-tempdir/mktemp-jecFmU-5: (<type
'exceptions.IOError'>, IOError('CRC check failed 0x5528869f !=
0x2aeb4411L',), <traceback object at 0x7fd5292a9830>)
It is in slovenian, but it means:
Cannot read /tmp/duplicity-gUZKem-tempdir/mktemp-jecFmU-5: (<type
'exceptions.IOError'>, IOError('CRC check failed 0x5528869f != 0x2aeb4411L',),
<traceback object at 0x7fd5292a9830>)
I tried to delete .cache/deja-dup, but the error is still there.
I am doing a backup to a remote server via ssh. I have reported this
under another bug, but it seems it belongs here.
Anyway, I deleted a file "duplicity-new-
signatures.20161011T065304Z.to.20161013T050922Z.sigtar.gz" on a backup
server, and now it is working (however, it started a new backup). But
this is really bad.
And just another question - would it be possible for me to restore
backup in that case?
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
Backing up fails with 'IOError CRC check failed'.
Status in Déjà Dup:
Status in Duplicity:
Status in deja-dup package in Ubuntu:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (<type
'exceptions.IOError'>, IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), <traceback object at 0x9fe0554>)
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~desktop-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp