Calibre 3.27.1 (64 bit) "database corrupted" error.

cHap85Lzwdzr · 07-08-2018, 06:09 PM

Hello:

After installing Calibre 3.27.1 (64 bit) the program won't launch and complains that "[t]he database at ... appears to be corrupted. Attempting to restore the database fails.

Doing a fresh installation, i.e., uninstalling Calibre 3.27.1, deleting all directories (Home and User), and reinstalling 3.27.1 does not solve the issue.

However, a fresh installation of 3.26.1 resolves the problem and 3.26.1 launches fine.

Is anyone else having this problem?

theducks · 07-08-2018, 06:47 PM

3.27.1 runs fine on W10 x64.
Check you A/V, it may be blocking a needed module

ilovejedd · 07-08-2018, 08:36 PM

Is it just me or are there notably more reported issues like this with Windows 10 than on Windows 7?

theducks · 07-08-2018, 11:15 PM

Quote:

Originally Posted by ilovejedd

Is it just me or are there notably more reported issues like this with Windows 10 than on Windows 7?

Yes, because they are ever tightening the security model trying to thwart the bad guys.
The also are trying to thwart the bad habits of users that just clicked 'allow' without really thinking about the consequences

cHap85Lzwdzr · 08-12-2018, 02:22 PM

Hello All:

I eventually figured out that it was Bitdefender's "SAFE FILES" protection. Once I allowed "calibre.exe" in "Application Access" the issue was resolved.

This issue started with Calibre 3.27.0 so I am wondering by Bitdefender was fine with 3.26.1 and prior.

avetik · 01-17-2019, 09:36 PM

I installed latest Calibre version on Chrome OS (v 73 dev) Linux container (a.k.a. Crostini).
Installation went well (only required xz-utils package installed). However, once I launch calibre and point it to an existing Library which is located on a shared USB drive (which I was maintaining just fine from another Linux install) it now shows the error message

"The library database at /mnt/chromeos/removable/SD128GB/Calibre_Large appears to be corrupted. Do you want calibre to try and rebuild it automatically? The rebuild may not be completely successful! If you say No, a new empty calibre library will be created."

And details:

Traceback (most recent call last):
File "site-packages/calibre/gui2/main.py", line 301, in initialize_db
File "site-packages/calibre/db/legacy.py", line 81, in __init__
File "site-packages/calibre/db/legacy.py", line 48, in create_backend
File "site-packages/calibre/db/backend.py", line 378, in __init__
File "site-packages/calibre/db/backend.py", line 1123, in fget
File "site-packages/calibre/db/backend.py", line 836, in conn
File "site-packages/calibre/db/backend.py", line 271, in __init__
File "site-packages/calibre/db/backend.py", line 315, in execute
File "src/cursor.c", line 1019, in APSWCursor_execute.sqlite3_prepare
File "src/statementcache.c", line 386, in sqlite3_prepare
IOError: IOError: disk I/O error

Is this easy to fix?

kovidgoyal · 01-17-2019, 09:45 PM

that's a disk i/o error it cannot be fixed in calibre, only in whatever subsytem you are using to expose the disk to your container.

avetik · 01-19-2019, 12:43 PM

Quote:

Originally Posted by kovidgoyal

that's a disk i/o error it cannot be fixed in calibre, only in whatever subsytem you are using to expose the disk to your container.

Other programs and apps I have installed so far seem to interact with the same drive just fine, but calibre has this I/O issue for some reason. And it is somehow tied to metadata.db permissions. I will try install on SD card.

07-08-2018, 06:09 PM	#1
cHap85Lzwdzr Junior Member Posts: 3 Karma: 10 Join Date: Jul 2018 Device: Windows 10	Calibre 3.27.1 (64 bit) "database corrupted" error. Hello: After installing Calibre 3.27.1 (64 bit) the program won't launch and complains that "[t]he database at ... appears to be corrupted. Attempting to restore the database fails. Doing a fresh installation, i.e., uninstalling Calibre 3.27.1, deleting all directories (Home and User), and reinstalling 3.27.1 does not solve the issue. However, a fresh installation of 3.26.1 resolves the problem and 3.26.1 launches fine. Is anyone else having this problem?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Can't assign epub viewer to "open with" in 64-bit Calibre	Hoods7070	Related Tools	4	07-29-2013 09:40 PM
Calibre plugIn Kindle Collections Error message "Value Error:month..."	readee	Plugins	4	10-10-2011 11:21 AM
Database Exception error - "malformed"	Debby	Calibre	6	02-18-2011 02:39 PM
"Database Disk Image is malformed" when connecting to Calibre after adding new books	djorkboy	Kobo Reader	13	10-07-2010 08:47 PM
"Database Disk Image is malformed" when connecting to Calibre after adding new books	djorkboy	Calibre	1	10-06-2010 08:59 PM

07-08-2018, 06:47 PM	#2
theducks Well trained by Cats Posts: 29,768 Karma: 54401244 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	3.27.1 runs fine on W10 x64. Check you A/V, it may be blocking a needed module

07-08-2018, 08:36 PM	#3
ilovejedd hopeless n00b Posts: 5,111 Karma: 19597086 Join Date: Jan 2009 Location: in the middle of nowhere Device: PW4, PW3, Libra H2O, iPad 10.5, iPad 11, iPad 12.9	Is it just me or are there notably more reported issues like this with Windows 10 than on Windows 7?

08-12-2018, 02:22 PM	#5
cHap85Lzwdzr Junior Member Posts: 3 Karma: 10 Join Date: Jul 2018 Device: Windows 10	Hello All: I eventually figured out that it was Bitdefender's "SAFE FILES" protection. Once I allowed "calibre.exe" in "Application Access" the issue was resolved. This issue started with Calibre 3.27.0 so I am wondering by Bitdefender was fine with 3.26.1 and prior.

01-17-2019, 09:36 PM	#6
avetik Member Posts: 15 Karma: 10 Join Date: Jul 2016 Device: Kindle PW3	I installed latest Calibre version on Chrome OS (v 73 dev) Linux container (a.k.a. Crostini). Installation went well (only required xz-utils package installed). However, once I launch calibre and point it to an existing Library which is located on a shared USB drive (which I was maintaining just fine from another Linux install) it now shows the error message "The library database at /mnt/chromeos/removable/SD128GB/Calibre_Large appears to be corrupted. Do you want calibre to try and rebuild it automatically? The rebuild may not be completely successful! If you say No, a new empty calibre library will be created." And details: Traceback (most recent call last): File "site-packages/calibre/gui2/main.py", line 301, in initialize_db File "site-packages/calibre/db/legacy.py", line 81, in __init__ File "site-packages/calibre/db/legacy.py", line 48, in create_backend File "site-packages/calibre/db/backend.py", line 378, in __init__ File "site-packages/calibre/db/backend.py", line 1123, in fget File "site-packages/calibre/db/backend.py", line 836, in conn File "site-packages/calibre/db/backend.py", line 271, in __init__ File "site-packages/calibre/db/backend.py", line 315, in execute File "src/cursor.c", line 1019, in APSWCursor_execute.sqlite3_prepare File "src/statementcache.c", line 386, in sqlite3_prepare IOError: IOError: disk I/O error Is this easy to fix?

01-17-2019, 09:45 PM	#7
kovidgoyal creator of calibre Posts: 43,835 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	that's a disk i/o error it cannot be fixed in calibre, only in whatever subsytem you are using to expose the disk to your container.