View Single Post
Old 02-22-2026, 03:20 AM   #4
aborel
Enthusiast
aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.aborel can grok the meaning of the universe.
 
Posts: 33
Karma: 155826
Join Date: Dec 2013
Device: Kobo Aura
Quote:
Originally Posted by jprobibs View Post
I am accessing the same database from two instances of Cailbre on separate machines on the same network (not at the same time, of course). Trying to startup Cailbre on the other machine caused the same error.
There's your problem, as stated in the FAQ you should not do that https://manual.calibre-ebook.com/faq...rked-drive-nas

Yes, it can work for a while (even a long time), and only one client at a time is certainly less risky, but one day it may break anyway - other processes that just calibre might be accessing the file.

To fix your database, I suggest using calibre's repair function on a local copy on just one machine and see if it works. Otherwise, restoring from a backup is probably your best bet.

Last edited by aborel; 02-22-2026 at 03:23 AM.
aborel is offline   Reply With Quote