I’ve been running a node for approximately 1 year and it is now full at 4.5Tb. It’s running on a 20c/40t rackmount server that is entirely unnecessary, so I’m trying to move it to my 6Tb disk attached to my Rpi. I followed the installation directions exactly for the installation on the server and the pi.
I have gotten to the point where I can SSH into either machine from the other, and at the point in the installation-for-rpi directions where I would create an identity. Rsync is installed on both machines. I think my problem is mostly my inexperience with Linux in general, but when I SSH into either machine from the other and run the command ‘rsync -aP /mnt/storj/identity/storagenode/ /mnt/storj2/storagenode-new/identity/’, I get
rsync: change+dir “/mnt/storj/identity” failed: No such file or directory (2)
rsync: mkdir “/mnt/storj2/storagenode-new/identity” failed: No such files or directory (2)
rsync error: error in file IO (code 11) at main.c(681) [Receiver=3.1.3]
I’m hoping someone can explain what’s going on, as I’m not sure why the files wouldn’t be there since I didn’t make any changes during installation. Am I missing part of the command that I’m supposed to fill in myself? I did some searching here and it seems like nobody is using the command specified in the documentation, and I don’t know enough to know what will work for me.
You don’t first connect via ssh and then rsync. After connection, you are on the other machine. It doesn’t know about filesystem of the one that you are connecting from. What you need instead is to specify a “network path” like this: rsync -aP ~/SourceDirectory/* firstname.lastname@example.org.XXX:~/Destination
Take a look here (just a first link from google) for caveats and options:
You do know that since you already have a node, you shouldn’t create new identity, right?
I seem to have figured out the path to the original identity just by copying the stated location from the original installation directions ~/.local/share/storj/identity/storagenode/*
But I cannot figure out what needs to be the path for the destination. email@example.com.XXX:~/mnt/storj2/storagenode-new/identity does not work ‘No such file or directory’ I’m obviously making some simple mistake with the path here but I don’t know what.
Why don’t you connect the usb harddrive to the server and transfer it directly over usb then connect it to your rpi when done.
This should be a lot faster than trying to transfer it over network.
If there was documentation explaining that, then I would, but I’m not familiar enough with Linux, Storj, or any part of this to diverge from the documentation. I would not be able to get it to work. Waiting for a sync also just isn’t much of a problem for me, but losing the 4.5tb node would be pretty annoying.
Ommit the ~ as this gets substituted by the user’s home directory /home/user. So the path would be /home/user/mnt/storj2/storagenode-new/identity in your example, which does not exist. What you want ist the right absolute path /mnt/storj2/storagenode-new/identity. Make sure that the user can write into that folder.
Ommit the ~ as this gets substituted by the user’s home directory /home/user.
you need to remove the “~” character and use an absolute path.
That worked! Sort of. It now seems to be making the attempt correctly, but still failed because ‘Permission denied’. The command I am using is ‘sudo rsync -aP ~/.local/share/storj/identity/storagenode/* firstname.lastname@example.org:/mnt/storj2/storagenode-new/identity/’
When I run that command it asks for sudo password for the machine I’m ssh’d into and then asks for password for the pi. When I enter the passwords it then shows some lines with download rates, all with times of 0:00:00, and tells me they all failed on the reciever side because permission denied.
Success! I also created the /mnt/storj2/storagenode-new/orders/ directory and /mnt/storj2/storagenode-new/storage/ directory and given user permissions, but I can’t figure out where the actual orders and data are on the original machine. Can I get some help finding those?
If you place your identity to the disk with data instead of SD card, it should survive.
In the worst case you would need to re-flash the SD card, install docker and run your node back.
Please never run the setup step again for the existing worked node and it should be ok.