@Dmitry A question (not a suggestion that you should do so at this time): Can you hypothetically mount (and, possibly, create necessary symbolic links) such that the CryoSPARC project directories can still be accessed under the same path as they were accessed on the old drive?
@wtempel - from the same server it doesnot seem to be possible.
So what I tried -
a) to create a new folder called old_drive
b) tried to make a symbolic link to it from the old drive (called nas/cold)
sudo mkdir /old_drive
sudo ln -s /nas/cold/cryosparc_projects /old_drive/cryosparc_projects
the old_drive/cryosparc_projects was created but “cryosparc_projects” is red - so the symbolic link is broken.
The issue is still that
XXXX@cryotem-access:/old_drive$ cd /nas/cold
ls -l
total 0
XXXX@cryotem-access:/nas/cold$
So as you see it is not possible from the sever.
Maybe it is possible from the other pc that can see the containment of the nas/cold folder. But then again not sure if the server will see any file.
p.s. the funny this is that when one types -
XXXX@cryotem-access:/nas$ mount | grep /nas/cold
192.168.220.2:/cryoem_cold on /nas/cold type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.220.24,local_lock=none,addr=192.168.220.2,_netdev)
XXXX@cryotem-access:/nas$
Did you expect to find /nas/cold/cryosparc_projects?
Is the “new drive” supposed to be and actually mounted on 192.168.220.2?
What is the output of the df -h command on 192.168.220.2?