In which logs? If journalctl, then you need to fix your OS - firstly check and fix errors on the system drive, then reinstall everything corrupted or reinstall/reflash the OS. Make sure that you copied/moved identity to the disk with data out of the system drive.
Already restarted the whole system? Looks like the drive failed or your lost connection. Although even the connection might already been restored, if the whole docker process hasn’t been restarted the problem can still persist. Easiest possibly solution is just restarting the whole system, preferably cold (so just poweroff, wait 10secs, disconnect/reconnect USB drives if you work with those, and then restart the system).
The whole system has already restarted several times, and I already followed instructions about fixing malformed database. I have deleted the container with docker rm and recreated by running again the command updates docker run -d… without more better result
Are all nodes running on the same computer / operating system?
If Linux (debian-based), any errors in dmesg?
If not, you can stop all docker storagenodes and rm them all docker stop (...) && docker rm (...). Then docker rmi storjlabs/storagenode (if that doesn’t work, then use image ID. See also: docker rmi | Docker Docs) and then restart, in order to force docker to redownload the image.
But essentially I quite doubt it’s docker- or storj-related. I/O-errors are usually file system problems (in this case, apparently the system file system of the docker image pr even your host file system).
You could even try to get into the docker container, and check for yourself if the files stated above really exist: docker exec -it storagenode /bin/bash (might be time sensitive, due to restarts).
Does it work now?
If your system disk is dying you likely need to reinstall every single packet for the OS to allow the relocator to place binaries and configs to the healthy sectors. But it’s a cat and mouse game, you never know, when your system will stop to boot.
Meanwhile I insist to copy/move identity from the system drive to the disk with data and use this path in your docker run command.
Do you really meant RAID0? With one disk failure the whole volume will be lost.
my node doesn’t run so well and I’m working on identifying packets to reinstall. I will switch from centos to debian. I will do a better install of storj by the way.
Apologize me for the fat finger, i meant RAID1. New disks are just arrived at home and I will soonly reinstall my NAS.
RAID1 without autocorrection coming with ZFS or BTRFS doesn’t help much - mdraid do not know which data is corrupted, and which - not, meaning that it will mirror it as is and you will have a corrupted data on both drives.