I am running Ubuntu, I have done it before and no glitch, however at this time, after moving all the data to the new hard drive and change the mount parameter for the data to the new hard drive, the node doesn’t go online. When I run the dashboard it say’s offline. Anyone can remind me of maybe I am missing something? Because the identity is residing in the root folder as it was during the installation, so I did not bother changing the mount parameter for the identity, only the data. However even if I tried copying the identity folder to the new hard drive and then change the mount for the identity parameter to the new hard drive, still it say’s offline when I run the dashboard. Any ideas what am I missing? Thanks in advance.
Did you check/grant file permissions at the new location?
Here are the old and the new docker command:
Old:
docker run -d --restart unless-stopped --stop-timeout 300
-p 192.168.200.50:28967:28967
-p 192.168.200.50:14002:14002
-e WALLET="******"
-e EMAIL="@gmail.com"
-e ADDRESS=“.#$%^.:28967”
-e STORAGE=“900GB”
–mount type=bind,source="/root/.local/share/storj/identity/storagenode/",destination=/app/identity
–mount type=bind,source="/mnt/storagenode2/",destination=/app/config
–name storagenode2 storjlabs/storagenode:latest
New:
docker run -d --restart unless-stopped --stop-timeout 300
-p 192.168.200.50:28967:28967
-p 192.168.200.50:14002:14002
-e WALLET="******"
-e EMAIL="@gmail.com"
-e ADDRESS=“.#$%^.:28967”
-e STORAGE=“900GB”
–mount type=bind,source="/root/.local/share/storj/identity/storagenode/",destination=/app/identity
–mount type=bind,source="/mnt/storagenode2new/",destination=/app/config
–name storagenode2new storjlabs/storagenode:latest
The old and the new hard drive:
root@multivpn:/mnt/storagenode2# ls -l
total 44
-rw------- 1 root root 8502 Mar 3 18:20 config.yaml
drwx------ 4 root root 35 Jan 29 01:49 orders
-rw------- 1 root root 32768 Jun 8 17:08 revocations.db
drwx------ 6 root root 4096 Jun 8 17:43 storage
-rw------- 1 root root 1377 Jun 8 17:08 trust-cache.json
root@multivpn:/mnt/storagenode2# cd /mnt/storagenode2new
root@multivpn:/mnt/storagenode2new# ls -l
total 56
drwxr–r-- 2 root root 4096 Jan 23 02:20 identity
drwx------ 2 root root 16384 Jun 8 03:48 lost+found
drwx------ 4 root root 4096 Jun 8 16:52 orders
-rw------- 1 root root 32768 Jun 8 17:06 revocations.db
drwx------ 6 root root 4096 Jun 8 17:33 storage
-rw------- 1 root root 1377 Jun 8 17:06 trust-cache.json
What I noticed is that the config.yaml was not created in the new hard drive, storagenode2new, whereas in the old hard drive storagenode2 there is config.yaml. Can you please check what I am still missing. Regarding file permission I don’t see any difference between the old drive and the new drive.
I solved it: I have to copy the config.yaml manually since it did not create when I run the new docker command.
I use Windows, so I don’t know too much about that. I think you can point your docker command to a specific config.yaml, so just point that to your old one. Also double check the identity location.
Maybe if you post your docker run command someone might be able to help you a bit more 
I solved it, I manually copied the config.yaml. Thanks for heading to that directions.