Library Problem (Mac M1 Pro)

[judsal]

Hi,

I've been a Calibre user for awhile now and I have been having problems with my library. I moved the library to a new local folder on my Mac. After creating a new library from this location, I had to restore database almost everytime I opened Calibre.

I just opened it and there's only one book in my library. When I click Switch/Create Library... and then choose my folder it says "There is no existing calibre library at /CalibreLibrary."

I can still see all my book folders with files inside in my folder. There are also 3 metadata files:

1) metadata [conflicted].db
2) metadata_db_prefs_backup.json
3) metadata_pre_restore.db

What should I do?

[theducks]

Is that your Library name, Because Calibre Library is the default name (note space)?

BTW The full command is
Switch/create Library: USE EXISTING:<selection>

[judsal]

Originally Posted by theducks

Is that your Library name, Because Calibre Library is the default name (note space)?

BTW The full command is
Switch/create Library: USE EXISTING:<selection>

Yes, that's my library name.

path/to/library/CalibreLibrary

[mbovenka]

Originally Posted by judsal

There are also 3 metadata files:

1) metadata [conflicted].db
2) metadata_db_prefs_backup.json
3) metadata_pre_restore.db

That first file is supposed to be 'metadata.db'. The fact that it isn't called that is the reason Calibre thinks there is no library in that directory.

The '[conficted]' bit makes me think there is some backup/sync/cloud drive program messing with your library. You being on a Mac, Time Machine maybe? Anyway, kill that, whatever it is.

[pdurrant]

Originally Posted by mbovenka

That first file is supposed to be 'metadata.db'. The fact that it isn't called that is the reason Calibre thinks there is no library in that directory.

The '[conficted]' bit makes me think there is some backup/sync/cloud drive program messing with your library. You being on a Mac, Time Machine maybe? Anyway, kill that, whatever it is.

Time Machine would never produce such a file. But I agree, it looks like some synchronisation mechanism is messing up.

[chaley]

Originally Posted by mbovenka

That first file is supposed to be 'metadata.db'. The fact that it isn't called that is the reason Calibre thinks there is no library in that directory.

The '[conficted]' bit makes me think there is some backup/sync/cloud drive program messing with your library. You being on a Mac, Time Machine maybe? Anyway, kill that, whatever it is.

Dropbox uses file names like that.

[Sirtel]

Originally Posted by chaley

Dropbox uses file names like that.

Yes. All one needs to do is to decide which database file is the one that's actually in sync with the library files and rename it to "metadata.db".

AND pause the sync while Calibre is open!

[JSWolf]

Originally Posted by Sirtel

Yes. All one needs to do is to decide which database file is the one that's actually in sync with the library files and rename it to "metadata.db".

AND pause the sync while Calibre is open!

It's not a good idea to put any working library in the directory tree of any cloud sync software. It's best to keep a copy in the cloud sync directory tree and use FreeFileSync to one-way sync to the cloud directory tree.

[rantanplan]

Originally Posted by JSWolf

It's not a good idea to put any working library in the directory tree of any cloud sync software. It's best to keep a copy in the cloud sync directory tree and use FreeFileSync to one-way sync to the cloud directory tree.

Or use rClone if you want to backup your library to DropBox.

[judsal]

Thank you guys for the help. I'm not sure how the folder got renamed but I think it has something to do with PCloud. I was using a PCloud folder before and it seems like that library was somehow still in my Calibre although I thought I had deleted it.


I changed the name and deleted the PCloud library and everything seems to be working.

[peaceridge]

Originally Posted by judsal

Thank you guys for the help. I'm not sure how the folder got renamed but I think it has something to do with PCloud. I was using a PCloud folder before and it seems like that library was somehow still in my Calibre although I thought I had deleted it.


I changed the name and deleted the PCloud library and everything seems to be working.

I had the same problem a couple of days ago with PCloud. I don't sync, but moved a small library to PCloud. [I keep a small library of new additions called "move to pcloud" and move that to PCloud periodically, after which I delete the books in it.] Anyway, after I moved it, Calibre gave me the same error. I deleted the small library on my Mac, added a new empty one through Calibre and moved on. Thank you so much for your question, now I know it is a PCloud problem. Thank goodness I didn't move my entire library!

[JSWolf]

Originally Posted by peaceridge

I had the same problem a couple of days ago with PCloud. I don't sync, but moved a small library to PCloud. [I keep a small library of new additions called "move to pcloud" and move that to PCloud periodically, after which I delete the books in it.] Anyway, after I moved it, Calibre gave me the same error. I deleted the small library on my Mac, added a new empty one through Calibre and moved on. Thank you so much for your question, now I know it is a PCloud problem. Thank goodness I didn't move my entire library!

You don't move an active library to your cloud's directory tree. You COPY. And you don't need a library with just new books to sync to the cloud as FreeFileSYnc will do the syncing/copying of yoy existing library FFS will sort it all out and deal easily with what's new/different.

[peaceridge]

Originally Posted by JSWolf

You don't move an active library to your cloud's directory tree. You COPY. And you don't need a library with just new books to sync to the cloud as FreeFileSYnc will do the syncing/copying of yoy existing library FFS will sort it all out and deal easily with what's new/different.

Thank you, you are always so helpful. I didn't move the library, I did copy it (I thought, but I will double check next time). As far as FreeFileSync, I've used it in the past on my old Windows before I changed to Mac, and it is great for looking at all my files, but it takes a while. Since I'm only copying a few books to Pcloud, it is just quicker doing it the way I've been doing. Unless, of course, Pcloud has changed something, then I'll go back to using FreeFileSync.