bota87
October 11, 2020, 5:47pm
1
I’m trying to setup the second node on my raspberry.
I’ve generated a second identity and start the node with this
docker run -d --restart unless-stopped --stop-timeout 300
-p 28968:28967
-p 127.0.0.1:14003:14002
-e WALLET=“xxxxxxxxxxx”
-e EMAIL="xxxxxxx@gmail.com "
-e ADDRESS=“xxxxxxx.eu:28968”
-e STORAGE=“1TB”
–mount type=bind,source=“/media/maxtor/storagenode2/identity”,destination=/app/identity
–mount type=bind,source=“/media/maxtor/storagenode2/data”,destination=/app/config
–name storagenode2 storjlabs/storagenode:latest
The node keep restarting and all I get from the log is this
$ docker logs -f --tail 100 storagenode2
Error: sync /app/config/config.yaml500872744: structure needs cleaning
Error: sync /app/config/config.yaml336711568: structure needs cleaning
Error: sync /app/config/config.yaml607011623: structure needs cleaning
Error: sync /app/config/config.yaml143781070: structure needs cleaning
The data directory is empty, what I’m missing?
Alexey
October 11, 2020, 5:57pm
2
Please, show results of this command:
df -H
sudo grep "/media/maxtor/storagenode2" /etc/fstab
bota87
October 11, 2020, 6:01pm
3
$ df -H
File system Dim. Usati Dispon. Uso% Montato su
/dev/root 236G 56G 168G 25% /
devtmpfs 1,9G 0 1,9G 0% /dev
tmpfs 2,1G 8,2k 2,1G 1% /dev/shm
tmpfs 2,1G 203M 1,9G 11% /run
tmpfs 5,3M 4,1k 5,3M 1% /run/lock
tmpfs 2,1G 0 2,1G 0% /sys/fs/cgroup
/dev/mmcblk0p1 265M 56M 209M 22% /boot
tmpfs 402M 0 402M 0% /run/user/1001
/dev/sdc1 4,0T 3,2T 621G 84% /media/raspihdd
/dev/sda1 2,0T 476G 1,4T 26% /media/maxtor
$ cat /etc/fstab
proc /proc proc defaults 0 0
PARTUUID=6c586e13-01 /boot vfat defaults 0 2
PARTUUID=fec687e2-633a-a048-96a9-cf368b9f6927 / ext4 defaults,noatime 0 1
PARTUUID=2d9512f2-01e7-8547-9b29-7ff09aef056b /media/raspihdd ext4 relatime,errors=remount-ro 0 1
PARTUUID=6815c43c-64bd-f447-978b-0c7299eb385c /media/maxtor ext4 relatime,errors=remount-ro 0 1
Alexey
October 11, 2020, 6:04pm
4
The error “structure needs cleaning” usual mean that filesystem is corrupted and need to be fixed with fsck.
The fsck should be performed on unmounted disk. So, you need stop and remove the container, unmount the disk and run fsck:
docker stop -t 300 storagenode2
docker rm storagenode2
sudo umount /media/maxtor
fsck /dev/sda1
When filesystem will be fixed, your can try to mount back and run the storagenode2