I updated the node today and after the update, it did not recognize the path to the Storj DB. I rebooted the machine and then it mapped the right folder, but it shows the following error:
Error response from daemon: Container a485af9284a0f8a512f22439a0ac2bc70b1476b0b16636cb978dc217f5c013d7 is restarting, wait until the container is running
It shows this error for a few hours now…
Any suggestions on how to fix this?
Thank you for taking the time to look at the post. Sorry that I did not have the correct information before.
This is the run command data:
Using new storj version via docker
sudo docker run -d --restart unless-stopped -p 34567:28967
–name storagenode storjlabs/storagenode:beta
Node software type: Docker Linux Node software version: v1.0.1 OS details: Raspberry PI Buster Virtualization: no virtualization Location (optional): USA ISP type: Fiber external IP address (please DON’T paste your public IP address here!): dynamic with DDNS DDNS provider: No-IP DDNS set up via router or via DUC software?: Router | DUC Type of hardware: RPi How is your HDD connected: USB File system : Not sure Satellite specific problem?: all Sats
I believe I have FSTAB configured. Here is the output to show that:
proc /proc proc defaults 0 0
PARTUUID=ea7d04d6-01 /boot vfat defaults 0 2
PARTUUID=ea7d04d6-02 / ext4 defaults,noatime 0 1
I would recommend avoiding using /media in fstab as that is used for automatic mounting by the OS. It’s better to mount it to /mnt/Seagate_8T. Don’t forget to adjust the paths in the run command accordingly if you change this.
But, we’re shooting in the dark right now. This may not be causing your issue. Please post the last 30 lines of your log.
I did that. This is the response I get for the last 24 hours when I try to look at the docker container:
Error response from daemon: Container 51ff4f8bea816e0a50bf8c0c63e067e4a7358bf233670155187f5ac7cdc23e58 is restarting, wait until the container is running
This is what I used to fix the hard drive.
sudo fsck /dev/sda2
fsck from util-linux 2.33.1
pi@pi:~$ sudo blkid /dev/sda2
/dev/sda2: LABEL=“Seagate Expansion Drive” UUID=“1CE24871E2485166” TYPE=“ntfs” PTTYPE=“atari” PARTLABEL=“Basic data partition” PARTUUID=“93e5f72f-db9e-4da9-a99c-bb64fcc78342”
pi@pi:~$ sudo mount /media/Seagate_8T/
pi@pi:~$ ls /media/Seagate_8T/
Node_1 README Seagate Start_Here_Mac.app storj_identity
otherFiles scripts SeagateExpansion.ico Start_Here_Win.exe Warranty.pdf
Is there a way to fix this, or should I just dump the node and try to install a new one on this machine?
You should not use the NTFS on Linux in the first place.
Please, shutdown your pi, disconnect drive and connect it to Windows PC, check for errors and fix them, then safely remove the drive and connect it back to the pi. After that it should work some time until the next unexpected shutdown or reboot.
Better to move your data on ext4 filesystem.
To do that, you should copy your data to some temporary place: https://documentation.storj.io/resources/faq/migrate-my-node, stop and remove the container, format this drive to ext4 and return back your data and identity, then update /etc/fstab with new parameters (UUID and filesystem will be different), make sure that it’s mounted after reboot, then run the storagenode.