Based on the description of file moves so far and the apparent involvement of multiple Linux accounts (your personal account, the “separate cryosparc user” account and, possibly, the root account), I am uncertain about the current state of the cryoSPARC instance.
It is possible that file ownerships were modified during the move of the database, which alone could “break” the installation.
Additionally, the values given for CRYOSPARC_DB_PATH appear unusual (and possibly incorrect) in that they are lacking a leading (and functionally significant) “/” character and they are ending in cryosparc_master. The latter suggests the location of the cryoSPARC master programs, not the location of the database.
Depending on whether the database already contained important information at the time of the move, you may decide to either:
- seek the the help of an experienced Linux user who is also familiar with cryoSPARC documentation to restore the current installation to a functional state or
-
permanently retire the current installation (to ensure it will not interfere with the proposed new installation) and:
- ensure the old instance is no longer running:
cryosparcm stop- terminate possible remaining processes related to the old instance. You may follow instructions in this post, except you should not run
cryosparcm startat this point.
- carefully decide on the installation and database ownership and paths
- reinstall the software
- if needed, import existing project directories to the new cryoSPARC instance
- ensure the old instance is no longer running: