Zotero doesn't open any longer
After a long time without any problems and only pleasure of fine work, my Zotero-stand-alone on MacBook High Sierra does not open any longer but tells me :
Error: Error(s) encountered during statement execution: disk I/O error [QUERY: SELECT ROWID AS id, libraryID, key FROM items] [PARAMS: ] [ERROR: disk I/O error]
Zotero.DBConnection.prototype.queryAsync<@chrome://zotero/content/xpcom/db.js:703:10
From previous event:
ZoteroService@file:///Applications/Zotero.app/Contents/Resources/components/zotero-service.js:347:4
@chrome://zotero/content/include.js:4:14
I tried to install zotero anew, same result.
Can anybody help me?
Thanks!
Error: Error(s) encountered during statement execution: disk I/O error [QUERY: SELECT ROWID AS id, libraryID, key FROM items] [PARAMS: ] [ERROR: disk I/O error]
Zotero.DBConnection.prototype.queryAsync<@chrome://zotero/content/xpcom/db.js:703:10
From previous event:
ZoteroService@file:///Applications/Zotero.app/Contents/Resources/components/zotero-service.js:347:4
@chrome://zotero/content/include.js:4:14
I tried to install zotero anew, same result.
Can anybody help me?
Thanks!
https://www.zotero.org/support/reporting_problems#reporting_startup_errors
so I used :
prt-19105:~ tmohnike$ /Applications/Zotero.app/Contents/MacOS/zotero -jsconsole
giving
JavaScript warning: resource://gre/modules/commonjs/toolkit/loader.js -> resource://zotero/bluebird/util.js, line 201: unreachable code after return statement
the Error console does not allow me to copy-paste, but states the same sentence, adding eval (obj);
And than comes the error message already quoted :
Error(s) encountered during statement execution: disk I/O error [QUERY: SELECT ROWID AS id, libraryID, key FROM items] [PARAMS: ] [ERROR: disk I/O error]
Source file : chrome://zotero/content/xpcom/db.js line 703
Does this help you?
I would make a copy of the zotero.sqlite* files in your Zotero data directory, and then try scanning your disk for errors in Disk Utility. Whether or not that finds errors, you should then upload your database to the DB Repair Tool to see if it finds errors. (It will tell you if it did, and repair them if possible. If it doesn't say it found errors, you can ignore the DB copy it produces.)