Greetings everyone!
I was transitioning to fiber internet from my VDSL connection a couple of days ago. A couple of times I turned off my Raspberry Pi without a soft turn-off (stop the storj-node and then shut down the Raspberry from the terminal).
Right now, I’m getting an Input/output error when I execute the ls command from the terminal.
abc@raspberrypi:/mnt/storj $ ls -la
ls: cannot access ‘storagenode’: Input/output error
total 24
drwxr-xr-x 4 pi pi 4096 Dec 5 2021 .
drwxr-xr-x 3 root root 4096 Nov 18 2021 …
drwx------ 2 pi pi 16384 Nov 18 2021 lost+found
d??? ? ? ? ? ? storagenode
abc@raspberrypi:/mnt/storj $ ls -a
ls: cannot access ‘storagenode’: Input/output error
. … lost+found storagenode
Here is the docker logs output:
docker logs --tail 30 storagenode
--- stat config/storage/temp: no such file or directory
--- stat config/storage/garbage: no such file or directory
--- stat config/storage/trash: no such file or directory
2023-04-12 12:54:38,764 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 12:54:40,782 INFO spawned: 'storagenode' with pid 54
2023-04-12T12:54:41.116Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2023-04-12T12:54:41.173Z INFO Operator email {"Process": "storagenode", "Address": "abcdef@gmail.com"}
2023-04-12T12:54:41.174Z INFO Operator wallet {"Process": "storagenode", "Address": "0xaaaaaabbbbbbbbbb"}
Error: Error starting master database on storagenode: group:
--- stat config/storage/blobs: no such file or directory
--- stat config/storage/temp: no such file or directory
--- stat config/storage/garbage: no such file or directory
--- stat config/storage/trash: no such file or directory
2023-04-12 12:54:41,181 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 12:54:44,202 INFO spawned: 'storagenode' with pid 62
2023-04-12T12:54:44.542Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2023-04-12T12:54:44.599Z INFO Operator email {"Process": "storagenode", "Address": "abcdef@gmail.com"}
2023-04-12T12:54:44.599Z INFO Operator wallet {"Process": "storagenode", "Address": "0xaaaaaaaaaaabbbbbbbbbbbbbccccccccccccccc"}
Error: Error starting master database on storagenode: group:
--- stat config/storage/blobs: no such file or directory
--- stat config/storage/temp: no such file or directory
--- stat config/storage/garbage: no such file or directory
--- stat config/storage/trash: no such file or directory
2023-04-12 12:54:44,606 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 12:54:45,608 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2023-04-12 12:54:46,613 WARN received SIGQUIT indicating exit request
2023-04-12 12:54:46,615 INFO waiting for processes-exit-eventlistener, storagenode-updater to die
2023-04-12T12:54:46.615Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode-updater"}
2023-04-12 12:54:46,627 INFO stopped: storagenode-updater (exit status 0)
2023-04-12 12:54:47,633 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
e2fsck command output as below:
abc@raspberrypi:~ $ sudo e2fsck -p /dev/sdb1
/dev/sdb1: recovering journal
/dev/sdb1 contains a file system with errors, check forced.
/dev/sdb1: Inode 48722798 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49285578 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286370 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286404 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286409 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286490 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286494 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286502 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286649 ref count is 1, should be 2. FIXED.
/dev/sdb1: Inode 49286651 ref count is 1, should be 2. FIXED.
Error reading block 86507525 (Input/output error) while reading inode and block bitmaps.
/dev/sdb1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
After e2fsck command, I do not get any input/output error but my docker log output as below:
abc@raspberrypi:~ $ docker logs --tail 30 storagenode
2023-04-12T13:56:51.506Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "storage.allocated-disk-space"}
2023-04-12T13:56:51.506Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "contact.external-address"}
2023-04-12T13:56:51.506Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.address"}
2023-04-12T13:56:51.506Z INFO Invalid configuration file key {"Process": "storagenode-updater", "Key": "server.private-address"}
2023-04-12T13:56:51.506Z INFO Invalid configuration file value for key {"Process": "storagenode-updater", "Key": "log.output"}
2023-04-12T13:56:51.535Z INFO Anonymized tracing enabled {"Process": "storagenode-updater"}
2023-04-12T13:56:51.617Z INFO Running on version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.76.2"}
2023-04-12T13:56:51.618Z INFO Downloading versions. {"Process": "storagenode-updater", "Server Address": "https://version.storj.io"}
2023-04-12T13:56:52.006Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-04-12T13:56:52.009Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2023-04-12T13:56:52.072Z INFO Operator email {"Process": "storagenode", "Address": "abcdef90@gmail.com"}
2023-04-12T13:56:52.072Z INFO Operator wallet {"Process": "storagenode", "Address": "0xaaaaaaaaaaabbbbbbbbbbbbccccccccccccccccccc"}
2023-04-12T13:56:52.865Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode", "Version": "v1.76.2"}
2023-04-12T13:56:52.865Z INFO Version is up to date {"Process": "storagenode-updater", "Service": "storagenode"}
2023-04-12T13:56:52.902Z INFO Current binary version {"Process": "storagenode-updater", "Service": "storagenode-updater", "Version": "v1.76.2"}
2023-04-12T13:56:52.902Z INFO Version is up to date {"Process": "storagenode-updater", "Service": "storagenode-updater"}
2023-04-12T13:57:34.885Z INFO server kernel support for server-side tcp fast open remains disabled. {"Process": "storagenode"}
2023-04-12T13:57:34.887Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {"Process": "storagenode"}
Error: trust: open config/trust-cache.json: permission denied
2023-04-12 13:58:10,869 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 13:58:11,887 INFO spawned: 'storagenode' with pid 46
2023-04-12 13:58:11,890 WARN received SIGQUIT indicating exit request
2023-04-12 13:58:11,893 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2023-04-12T13:58:11.893Z INFO Got a signal from the OS: "terminated" {"Process": "storagenode-updater"}
2023-04-12 13:58:11,908 INFO stopped: storagenode-updater (exit status 0)
2023-04-12T13:58:12.221Z INFO Configuration loaded {"Process": "storagenode", "Location": "/app/config/config.yaml"}
2023-04-12T13:58:12.222Z INFO Anonymized tracing enabled {"Process": "storagenode"}
2023-04-12T13:58:12.279Z INFO Operator email {"Process": "storagenode", "Address": "abcdef@gmail.com"}
2023-04-12T13:58:12.279Z INFO Operator wallet {"Process": "storagenode", "Address": "0xaaaaaaaaaaaaaabbbbbbbbbbbbccccccccccccccc"}
2023-04-12 13:58:15,287 INFO waiting for storagenode, processes-exit-eventlistener to die
A couple of minutes later, logs output from storagenode as below, and now my node is getting restarted within 12 seconds:
abc@raspberrypi:~ $ docker logs --tail 60 storagenode
2023-04-12 14:03:13,944 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 14:03:14,946 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2023-04-12 14:03:14,948 WARN received SIGQUIT indicating exit request
2023-04-12 14:03:14,950 INFO waiting for processes-exit-eventlistener to die
2023-04-12 14:03:16,956 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
2023-04-12 14:03:19,960 INFO RPC interface 'supervisor' initialized
2023-04-12 14:03:19,961 INFO supervisord started with pid 1
2023-04-12 14:03:20,971 INFO spawned: 'processes-exit-eventlistener' with pid 12
2023-04-12 14:03:20,989 INFO spawned: 'storagenode' with pid 13
2023-04-12 14:03:21,005 INFO spawned: 'storagenode-updater' with pid 14
2023/04/12 14:03:21 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:21,097 INFO exited: storagenode-updater (exit status 1; not expected)
2023/04/12 14:03:21 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:21,128 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 14:03:22,130 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-12 14:03:22,145 INFO spawned: 'storagenode' with pid 29
2023-04-12 14:03:22,161 INFO spawned: 'storagenode-updater' with pid 30
2023/04/12 14:03:22 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:22,250 INFO exited: storagenode-updater (exit status 1; not expected)
2023/04/12 14:03:22 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:22,289 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 14:03:24,308 INFO spawned: 'storagenode' with pid 44
2023-04-12 14:03:24,322 INFO spawned: 'storagenode-updater' with pid 45
2023/04/12 14:03:24 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:24,417 INFO exited: storagenode-updater (exit status 1; not expected)
2023/04/12 14:03:24 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:24,444 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 14:03:27,465 INFO spawned: 'storagenode' with pid 60
2023-04-12 14:03:27,480 INFO spawned: 'storagenode-updater' with pid 61
2023/04/12 14:03:27 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:27,570 INFO exited: storagenode-updater (exit status 1; not expected)
2023/04/12 14:03:27 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:27,601 INFO gave up: storagenode-updater entered FATAL state, too many start retries too quickly
2023-04-12 14:03:27,607 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 14:03:28,610 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2023-04-12 14:03:28,610 WARN received SIGQUIT indicating exit request
2023-04-12 14:03:28,612 INFO waiting for processes-exit-eventlistener to die
2023-04-12 14:03:30,618 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
2023-04-12 14:03:34,985 INFO RPC interface 'supervisor' initialized
2023-04-12 14:03:34,986 INFO supervisord started with pid 1
2023-04-12 14:03:35,996 INFO spawned: 'processes-exit-eventlistener' with pid 12
2023-04-12 14:03:36,015 INFO spawned: 'storagenode' with pid 13
2023-04-12 14:03:36,032 INFO spawned: 'storagenode-updater' with pid 14
2023/04/12 14:03:36 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:36,130 INFO exited: storagenode-updater (exit status 1; not expected)
2023/04/12 14:03:36 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:36,163 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 14:03:37,166 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-12 14:03:37,174 INFO spawned: 'storagenode' with pid 30
2023-04-12 14:03:37,182 INFO spawned: 'storagenode-updater' with pid 31
2023/04/12 14:03:37 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:37,245 INFO exited: storagenode-updater (exit status 1; not expected)
2023/04/12 14:03:37 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:37,268 INFO exited: storagenode (exit status 1; not expected)
2023-04-12 14:03:39,286 INFO spawned: 'storagenode' with pid 46
2023-04-12 14:03:39,301 INFO spawned: 'storagenode-updater' with pid 47
2023/04/12 14:03:39 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:39,383 INFO exited: storagenode-updater (exit status 1; not expected)
2023/04/12 14:03:39 failed to check for file existence: stat config/config.yaml: input/output error
2023-04-12 14:03:39,410 INFO exited: storagenode (exit status 1; not expected)
Looks like I need to set up my node from scratch, Any suggestions?
Thank you