CAlibre 4.0 - Can't open database file errors - Page 2

JSWolf · 10-05-2019, 12:07 PM

Quote:

Originally Posted by hydin

Wow this is gonna take a while. I'll update in a day or two. If anyone is looking for programming feedback, some sort of percentage or something would be awesome. I'm just looking at a solid bar with a warning that this is gonna be a three step process.

How did it go? I would expect it to be done by now.

theducks · 10-05-2019, 12:17 PM

Quote:

Originally Posted by hydin

Nah, no optical discs on the PC. Just lots and lots of hard drives. I'll try the backup idea mentioned above and let you guys know how it goes!

Thanks!

That eliminates a possible issue

Good luck with the debug

hydin · 10-05-2019, 07:23 PM

Nope, still going.

Potentially a stupid question but should I cancel and delete the db file, and then restart and repair?

theducks · 10-05-2019, 07:34 PM

Quote:

Originally Posted by hydin

Nope, still going.

Potentially a stupid question but should I cancel and delete the db file, and then restart and repair?

Tough one. I think I will let Kovid call that.
A test: can you open any book in that library using the direct from the start menu (fire off the viewer, then have it open a book inside the Library)?

JSWolf · 10-05-2019, 08:04 PM

Quote:

Originally Posted by hydin

Nope, still going.

Potentially a stupid question but should I cancel and delete the db file, and then restart and repair?

Is the hard drive active? Is the Calibre process using CPU cycles? Is the free disk space getting lower?

kovidgoyal · 10-05-2019, 08:35 PM

Quote:

Originally Posted by hydin

Nope, still going.

Potentially a stupid question but should I cancel and delete the db file, and then restart and repair?

You can cancel a backup in the middle. But I suggest you first ensure that it works with a new library. Run calibre as

calibre --with-library "path to some empty folder"

and see if things work,

hydin · 10-05-2019, 09:33 PM

Ok, better idea of what I did.

Made library while in calibre
Exited, went into library via cmd line above
It worked. Added, removed books, hopped in a few times.
Made a random folder name (no actual folder, just a random directory), went into it with the cmd line, worked. Added book, worked.

So, what do I do now? I'm not getting that error in this library. Should I check out my others on the pc or should I try to see what's up with the main one, or just delete the db from the main and try to repair/restore? I've got like 32k books in the main one so for all I know that's the problem.

kovidgoyal · 10-05-2019, 09:38 PM

First check you have enough free space on the drive with the problem library. Then check that all other libraries work. Then try moving the problem library to another drive. If it still fails after that, then you can either

1) delete metadaata.db and try a repair
2) simply crate a new empty library and use add books (book per folder) to add ll the books from the old library folder into the new library

hydin · 10-05-2019, 09:45 PM

Yea there's like 85 gigs open, plenty of space. When I head back into the main library I still get the same problem.

Seems like the faster option would be the adding books to the new one. I'll create an empty one and add the books from there. I'm assuming it's one book per folder?

Thanks!!

kovidgoyal · 10-05-2019, 09:49 PM

yes one book per folder.

hydin · 10-09-2019, 10:39 PM

Welp.

It's fixed.

Turns out I had a bad sector on my drive and that's where the issues began. Ran a scandisk and fixed the errors, and copied the database file back over to the directory and boom, works like a champ.

I guess the lesson is, bad timing can happen to anyone, and always run a scandisk if something goes weird after an install.

Thanks for all the help guys!

DNSB · 10-10-2019, 01:16 AM

Quote:

Originally Posted by hydin

Welp.

It's fixed.

Turns out I had a bad sector on my drive and that's where the issues began. Ran a scandisk and fixed the errors, and copied the database file back over to the directory and boom, works like a champ.

I guess the lesson is, bad timing can happen to anyone, and always run a scandisk if something goes weird after an install.

Thanks for all the help guys!

Once again proving that Murphy was a raving optimist when he said "If" as in "If anything can go wrong, it will".

10-05-2019, 09:33 PM	#22
hydin Connoisseur Posts: 66 Karma: 186 Join Date: Nov 2008 Device: Paperwhite, Nook Glowlight 3	Ok, better idea of what I did. Made library while in calibre Exited, went into library via cmd line above It worked. Added, removed books, hopped in a few times. Made a random folder name (no actual folder, just a random directory), went into it with the cmd line, worked. Added book, worked. So, what do I do now? I'm not getting that error in this library. Should I check out my others on the pc or should I try to see what's up with the main one, or just delete the db from the main and try to repair/restore? I've got like 32k books in the main one so for all I know that's the problem. Last edited by hydin; 10-05-2019 at 09:40 PM. Reason: made a bit more concise.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre metadata.db contains errors... Calibre2opds cannot open file.	anamardoll	Related Tools	25	02-12-2018 08:33 PM
Calibre 2.7 Unable to open Database file	Gordo29	Devices	22	11-04-2016 11:10 PM
unable to open database file	mihal.v	Calibre	3	08-16-2014 09:44 AM
Unable to open database file	wladdy	Library Management	6	08-28-2012 05:04 AM
Unable to open database file	JulieR	Calibre	2	04-24-2009 04:40 AM

10-05-2019, 07:23 PM	#18
hydin Connoisseur Posts: 66 Karma: 186 Join Date: Nov 2008 Device: Paperwhite, Nook Glowlight 3	Nope, still going. Potentially a stupid question but should I cancel and delete the db file, and then restart and repair?

10-05-2019, 09:38 PM	#23
kovidgoyal creator of calibre Posts: 45,349 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	First check you have enough free space on the drive with the problem library. Then check that all other libraries work. Then try moving the problem library to another drive. If it still fails after that, then you can either 1) delete metadaata.db and try a repair 2) simply crate a new empty library and use add books (book per folder) to add ll the books from the old library folder into the new library

10-05-2019, 09:45 PM	#24
hydin Connoisseur Posts: 66 Karma: 186 Join Date: Nov 2008 Device: Paperwhite, Nook Glowlight 3	Yea there's like 85 gigs open, plenty of space. When I head back into the main library I still get the same problem. Seems like the faster option would be the adding books to the new one. I'll create an empty one and add the books from there. I'm assuming it's one book per folder? Thanks!!

10-05-2019, 09:49 PM	#25
kovidgoyal creator of calibre Posts: 45,349 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	yes one book per folder.

10-09-2019, 10:39 PM	#26
hydin Connoisseur Posts: 66 Karma: 186 Join Date: Nov 2008 Device: Paperwhite, Nook Glowlight 3	Welp. It's fixed. Turns out I had a bad sector on my drive and that's where the issues began. Ran a scandisk and fixed the errors, and copied the database file back over to the directory and boom, works like a champ. I guess the lesson is, bad timing can happen to anyone, and always run a scandisk if something goes weird after an install. Thanks for all the help guys!