Hi I have gotten this error while importing movies of a new dataset:
It finds the correct number of movies to import, but then fails with this error:
Traceback (most recent call last):
File “cryosparc_master/cryosparc_compute/run.py”, line 129, in cryosparc_master.cryosparc_compute.run.main
File “/home/cryosparcuser/software/cryosparc/cryosparc_worker/cryosparc_compute/jobs/imports/run.py”, line 863, in run_import_movies_or_micrographs
level, all_base_paths, abs_to_rel_map, all_rel_paths = symlink_all_abs_files_to_import_dir(proj_dir_abs, job_dir_rel, abs_paths_to_import, uid_to_path_map)
File “/home/cryosparcuser/software/cryosparc/cryosparc_worker/cryosparc_compute/jobs/imports/run.py”, line 763, in symlink_all_abs_files_to_import_dir
abs_to_rel_map, all_rel_paths = symlink_paths(proj_dir_abs, os.path.join(job_dir_rel, import_dir_name), all_abs_paths, all_base_paths, uid_to_path_map)
File “/home/cryosparcuser/software/cryosparc/cryosparc_worker/cryosparc_compute/jobs/imports/run.py”, line 750, in symlink_paths
os.symlink(abs_path, dest)
FileNotFoundError: [Errno 2] No such file or directory: /path/to/raw/movies → /path/to/imported/movies
I’m not if this is related or not but I recently updated to v4.7 and while doing so the worker node failed to update, so I updated it manually following the cryosparc guide. I didn’t notice any errors while do so, so I thought everything was fine… but i guess not.
I tried to Force-reinstall the master and worker dependencies. with cryosparcm forcedeps and cryosparcw forcedeps. both ran to completion without errors.
Have you previously imported data to a CryoSPARC project directory on this disk? I am not sure whether the required symlink operation is supported on an ntfs3 filesystem.
hmm thanks.
yes i have 2 other data sets on that disk that imported just fine previously. I usually use ntfs without issues…
but now that you mentioned that, I checked and it seems the drive is corrupted! Strange, I did not notice any issues, I could read and write files like normal…
Thanks! I would have probably spent a lot of time troubleshooting that. I will reformat the drive, copy the data back and try again.