Thread: Empty calibre after disk crash/replacement
View Single Post
Old 05-14-2019, 06:40 PM   #4
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,122
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by ranchero View Post
I rename dthe latest dated metadata.db to metadata.db

I did not have a metadata_db_prefs_backup, but I renamed "metadata_db_prefs_backup.json"] to "metadata_db_prefs_backup", although I was pretty sure that would fail.

Well, the rebuild failed (I used Switch/create library). This was the message.

calibre, version 3.42.0
ERROR: Failed to repair library: Restoring database failed, click Show details to see details (the metadata.db file appears untouched. There is a new metadata_db_prefs_backup.json containing only 14KB).

Traceback (most recent call last):
File "site-packages\calibre\db\restore.py", line 128, in run
File "site-packages\calibre\db\restore.py", line 281, in replace_db
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: u'E:\\LIBRARY\\metadata.db'

Any advice on next step? I appear to have my original library, a metadata.db file of some 14MB. Could I create a new Calibre library by exporting the data] to a new Library 2 file?

thanks rob
The filename DOES have .json as its extension
It is small because it only describes the structure (columns and type, and setting for the. No Data.
The restor processes uses the json file to create an empty table that matched the oldne.
The next step scans the folders and uses the OPF file to populate the table (this is what takes time. Read the file, validate, make the entry. Repeat)
theducks is offline   Reply With Quote