Quote:
Back it (the Library folder) up and try the Calibre recovery.
|
-Does this mean that the entire library folder is to be duplicated?
Quote:
try the Calibre recovery.
|
-How can Calibre recovery be started?
Quote:
The only reason I can figure is the computer or disk powered down abnormally.
|
That's exactly what I suspect.
Quote:
Traceback (most recent call last):
File "calibre/gui2/main.py", line 323, in initialize_db
File "calibre/db/legacy.py", line 197, in __init__
File "calibre/db/cache.py", line 190, in __init__
File "calibre/db/cache.py", line 474, in initialize_fts
File "calibre/db/cache.py", line 485, in start_fts_pool
File "calibre/db/cache.py", line 85, in call_func_with_lock
File "calibre/db/cache.py", line 597, in queue_next_fts_job
File "calibre/db/cache.py", line 500, in _update_fts_indexing_numbers
File "calibre/db/fts/connect.py", line 70, in number_dirtied
File "calibre/db/fts/connect.py", line 59, in get_connection
File "calibre/db/fts/connect.py", line 42, in initialize
File "calibre/db/backend.py", line 433, in execute
File "src/cursor.c", line 240, in resetcursor
apsw.CorruptError: CorruptError: database disk image is malformed
|
This error message isn't very long.
With this, along with the necessary background knowledge and suitable tools, could one repair the database "by hand"?
And for a better understanding:
Does the data stored in the respective file (/Volumes/eBooks_LaCie/Calibre_2023_08_12/Author/Book/metadata.opf) contain all the data present in the respective book record? Or only the data stored in the book metadata?