Restoring a corrupted database:
a) Android indicates that the DB is corrupted
b) Linux indicates that the DB is corrupted
c) All backups indicate the same thing.
d) DB was OK two days ago. Over six months since last test of backup DB.
Has there been any changes to the code that would have corrupted the DB when upgrading lately?
Is there a script or program to check the integrity or recover from a corrupted DB?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 2.34 in Windows is the best to use to attempt recovery.
All backups corrupt sounds like very strange things happening. Where do you store the database and backups?
Are any other files corrupt?
Try the repair option in KeePass - create a new database and select File > Import, KeePass KDBX (2.x) (Repair mode).
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
They are created on Fedora, and then transferred to Google's drive automatically. I will attempt recovery of the kdbx file on a Windows box. No other files are indicating being corrupt.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Restoring a corrupted database:
a) Android indicates that the DB is corrupted
b) Linux indicates that the DB is corrupted
c) All backups indicate the same thing.
d) DB was OK two days ago. Over six months since last test of backup DB.
Has there been any changes to the code that would have corrupted the DB when upgrading lately?
Is there a script or program to check the integrity or recover from a corrupted DB?
Version 2.34 in Windows is the best to use to attempt recovery.
All backups corrupt sounds like very strange things happening. Where do you store the database and backups?
Are any other files corrupt?
Try the repair option in KeePass - create a new database and select File > Import, KeePass KDBX (2.x) (Repair mode).
cheers, Paul
They are created on Fedora, and then transferred to Google's drive automatically. I will attempt recovery of the kdbx file on a Windows box. No other files are indicating being corrupt.