Error in running extraction from module SMS: database disk image is malformed

[N4M3Z]

Running mvt-ios check-backup on a backup newly created idevicebackup2 backup --full and decrypted with mvt-ios decrypt-backup produced the following error:

         INFO     [mvt.ios.modules.fs.sms] Found SMS database at path: Backup/3d/3d0d7e5fb2ce288813306e4d4636395e047a3d28
         ERROR    [mvt.ios.modules.fs.sms] Error in running extraction from module SMS: database disk image is malformed
                  Traceback (most recent call last):
                    File "/usr/local/lib/python3.9/site-packages/mvt/common/module.py", line 134, in run_module
                      module.run()
                    File "/usr/local/lib/python3.9/site-packages/mvt/ios/modules/fs/sms.py", line 57, in run
                      cur.execute("""
                  sqlite3.DatabaseError: database disk image is malformed

Analysis on other payloads works as expected (calls, chrome_favicon etc.).
The device in question has a history that goes back to 2009, so perhaps this is caused by an older attachment format?
(idevicebackup2 1.3.1, mvt at 425d83e).

[Te-k]

Yep, some files in backups are malformed, there is a way to fix them with them with the .clone sqlite command

[SandMouse]

May I add, I encounter an identical issue with mvt.ios.modules.fs.interactionc

ERROR    [mvt.ios.modules.fs.interactionc] Error in running extraction from module
                  InteractionC: database disk image is malformed
                  Traceback (most recent call last):
                    File "/usr/local/lib/python3.9/site-packages/mvt/common/module.py", line 134, in
                  run_module
                      module.run()
                    File "/usr/local/lib/python3.9/site-packages/mvt/ios/modules/fs/interactionc.py",
                  line 76, in run
                      cur.execute("""
                  sqlite3.DatabaseError: database disk image is malformed

[SandMouse]

Yep, some files in backups are malformed, there is a way to fix them with them with the .clone sqlite command

Can you point me in the right direction how to manually fix this?

Answer to my own question: Use the clone tool, replace the original file.

(https://database.guide/clone-sqlite-database/)

[botherder]

For example:

$ mv Backup/3d/3d0d7e5fb2ce288813306e4d4636395e047a3d28 Backup/3d/3d0d7e5fb2ce288813306e4d4636395e047a3d28.bak
$ sqlite3 Backup/3d/3d0d7e5fb2ce288813306e4d4636395e047a3d28.bak
sqlite> .clone Backup/3d/3d0d7e5fb2ce288813306e4d4636395e047a3d28