Database upgrade error

kerrypettigrew
I'm getting the following error message:
Error: Error(s) encountered during statement execution: disk I/O error [QUERY: PRAGMA foreign_key_check] [PARAMS: ] [ERROR: disk I/O error]
Zotero.DBConnection.prototype.queryAsync@chrome://zotero/content/xpcom/db.js:680:13
From previous event:
ZoteroService@file:///C:/Program%20Files%20(x86)/Zotero/components/zotero-service.js:346:7
@chrome://zotero/content/include.js:4:14
The discussion linked below was the top hit when I searched for my error message https://forums.zotero.org/discussion/88190/i-just-updated-zotero-and-got-the-following-error-see-below
While I'm also experiencing a disk I/O error, it differs from the error described by PAWatt. Does this make a difference to the steps I should take to rectify it?
  • dstillman
    disk I/O error
    A disk I/O error is a general, unspecified problem with Zotero's ability to access your disk. If you have your Zotero data directory on a network drive or external disk, you should move it back to the local disk to avoid these kinds of problems.

    If your data directory is already on a local disk, there may be an actual problem with your disk, and you should check it for errors. It could potentially also be caused by security software interfering with Zotero's ability to access the disk.
  • eiuolnmu
    From the windows security standpoint, I was having the same issue. For my machine, it was Windows 10 Ransomware protection. It was protecting the Zotero folder. I removed it, and it was able to write and upgrade the DB.

    Thank you for the assistance.
  • kerrypettigrew
    Finally fixed! I ran DISM and SFC (some files were corrupted and had to be repaired). That still didn't fix the problem - the error remained the same, and I was still unable to copy zotero.sqlite and paste it elsewhere - but what sorted it in the end was deleting zotero.sqlite (this deletes your local library btw). Once I'd done that, Zotero opened and offered to let me sync afresh from my online library. I didn't have to mess with my security setup at all, thankfully.

    For those like me who haven't run DISM and SFC before, here is exactly what I did (so you don't have to spend ages in despair on forums). This is for Windows 10:
    1) open an elevated command window (i.e. windows+R, type 'cmd' and press Ctrl+Shift+Enter to run the command as an administrator
    2) Run the following command: DISM.exe /Online /Cleanup-image /Restorehealth
    3) Once that's done, run the following command: sfc /scannow
    4) Send a report to your desktop using the following command: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
    5) Take a look - see if anything was broken, and if it got repaired ok
    6) repeat steps 2-5 to check - your new sfcdetails.txt should say all was well

    thanks everybody
Sign In or Register to comment.