Does your sync report or logs include SQLITE_CORRUPT (sometimes preceded by SQLITE_BUSY)?
Know that PhotoStructure runs a database recovery process on startup, so restarting the application may fix the issue–but the rebuild process bats about 500–sometime the db is left in a truly corrupt state.
If restarting PhotoStructure doesn’t work, the next step would be to force-rebuild your library:
- shut down PhotoStructure
- open your library directory. Here are instructions.
- delete the “previews” and “models” directories.
- restart PhotoStructure. PhotoStructure should automatically restart the sync process.
Note, though, that it’s highly likely that with the same software and hardware, you’ll eventually see the same error.
If you’re on macOS, one thing you could try is disabling your Mac from going to sleep, at least until your first sync runs to completion.
At least on my test Macs, I’ve found that after the mac goes to sleep and resumes, many of my external hard drives go into a zombie state. Opening a finder window into the external drive just hangs with the spinning beach ball of doom.
I have found that SanDisk external SSDs are reliable (I bought a couple through Costco). I found that Samsung external SSD were hit or miss. My handful of third-party SSD external cases (made by Cable Matters, Plugable, and Sabrent) did not prove to be reliable after waking from sleep, at least on my M1 Mac Mini.
This suspend/resume-causing-drive-zombies issue doesn’t seem to happen, at least in my testing, on Linux or Windows.