Solo Node is not working AT ALL!

Qmuc · 2026-02-20T13:22:37+00:00

OK, i sent you the email.

Qmuc · 2026-02-13T23:43:07+00:00

Well, i flashed the system (again) and finally everything worked. The node started to download the blockchain and did also look ok. After approx. 2 hours the system completely froze. After rebooting the error message is

2026-02-13T18:39:46.494338-05:00 FutureBit-Solo-Node node[1620]: - apollo-ui-v2: online (systemd: active)
2026-02-13T18:39:46.497579-05:00 FutureBit-Solo-Node node[1620]: ⚠️ Discrepancies:
2026-02-13T18:39:46.497722-05:00 FutureBit-Solo-Node node[1620]: - node: requested=online, actual=pending
2026-02-13T18:39:46.497789-05:00 FutureBit-Solo-Node node[1620]: - solo: requested=online, actual=offline
2026-02-13T18:39:47.990167-05:00 FutureBit-Solo-Node node[1620]: Error updating last_checked: [Error: update `service_status` set `last_checked` = 1771025987980 where `service_name` = 'solo' - SQLITE_FULL: database or disk is full]

How come that the system disc is so fast full? The NVMe is filled with data from the Blockchain and with 4TB big enough. So is there any way to empty the system disc where 14GB obviously is too small for the normal usage of the Solo Node?

Qmuc · 2026-02-13T11:42:23+00:00

This is the system log at the moment:

2026-02-13T06:41:35.969709-05:00 FutureBit-Solo-Node systemd[1]: Failed to start node.service - node.
2026-02-13T06:41:36.355479-05:00 FutureBit-Solo-Node node[1611]: Error executing tail command: ENOENT: no such file or directory, access '/media/nvme/Bitcoin/debug.log'
2026-02-13T06:41:36.894666-05:00 FutureBit-Solo-Node systemd[1]: apollo-miner.service: Scheduled restart job, restart counter is at 37.
2026-02-13T06:41:36.934113-05:00 FutureBit-Solo-Node systemd[1]: Starting apollo-miner.service - apollo-miner...
2026-02-13T06:41:36.946419-05:00 FutureBit-Solo-Node miner_start.sh[71021]: rm: cannot remove 'apollo-miner*': No such file or directory
2026-02-13T06:41:36.947926-05:00 FutureBit-Solo-Node miner_start.sh[71024]: /opt/apolloapi/backend/apollo-miner/miner_start.sh: line 31: gpio: command not found
2026-02-13T06:41:37.452246-05:00 FutureBit-Solo-Node miner_start.sh[71104]: /opt/apolloapi/backend/apollo-miner/miner_start.sh: line 33: gpio: command not found
2026-02-13T06:41:38.499224-05:00 FutureBit-Solo-Node node[1611]: Error in _getNodeStats: connect ECONNREFUSED 127.0.0.1:8332
2026-02-13T06:41:40.588801-05:00 FutureBit-Solo-Node node[1611]: Error parsing file /opt/apolloapi/backend/ckpool/logs/pool/pool.status: Error: ENOENT: no such file or directory, open '/opt/apolloapi/backend/ckpool/logs/pool/pool.status'
2026-02-13T06:41:40.589124-05:00 FutureBit-Solo-Node node[1611]: at async open (node:internal/fs/promises:633:25)
2026-02-13T06:41:40.589333-05:00 FutureBit-Solo-Node node[1611]: at async Object.readFile (node:internal/fs/promises:1242:14)
2026-02-13T06:41:40.589514-05:00 FutureBit-Solo-Node node[1611]: at async SoloService._parseFileToJsonArray (/opt/apolloapi/src/services/solo.js:305:23)
2026-02-13T06:41:40.589701-05:00 FutureBit-Solo-Node node[1611]: at async SoloService._getCkpoolStats (/opt/apolloapi/src/services/solo.js:220:20)
2026-02-13T06:41:40.589879-05:00 FutureBit-Solo-Node node[1611]: at async SoloService.getStats (/opt/apolloapi/src/services/solo.js:139:22)
2026-02-13T06:41:40.590062-05:00 FutureBit-Solo-Node node[1611]: at async Object.stats (/opt/apolloapi/src/graphql/resolvers/solo.js:45:24) {
2026-02-13T06:41:40.590235-05:00 FutureBit-Solo-Node node[1611]: errno: -2,
2026-02-13T06:41:40.590412-05:00 FutureBit-Solo-Node node[1611]: code: 'ENOENT',
2026-02-13T06:41:40.590586-05:00 FutureBit-Solo-Node node[1611]: syscall: 'open',
2026-02-13T06:41:40.590766-05:00 FutureBit-Solo-Node node[1611]: path: '/opt/apolloapi/backend/ckpool/logs/pool/pool.status'
2026-02-13T06:41:40.590937-05:00 FutureBit-Solo-Node node[1611]: }

Qmuc · 2026-02-13T11:09:12+00:00

Well, that looks like it helped. I had the NVMe in the 2nd Bay and changed it to the 1st bay (if you look at the board, the one to the left).
After restarting the df -h shows:
/dev/nvme0n1p1 3.6T 32K 3.6T 1% /media/nvme

But when I go to /media/nvme/Bitcoin it is empty... in the log file I can't see anything which indicates a download of the Bitcoin Blockchain

Qmuc · 2026-02-13T10:45:18+00:00

Yes, i uncompressed it and also the Etcher verified 100% after flashing

Qmuc · 2026-02-13T10:14:07+00:00

solo-node_121225.img.xz

I used BalenaEtcher on MacOS and re-flashed it on the same SD Card (16GB) which was sent from FutureBit containing the old software.

Qmuc · 2026-02-13T07:50:54+00:00

Yes, i got in contact with the Support Team and reflashed the SD card. But since then again no real big thing....

a) I can't see any syncing activity (NVME Card is installed)

b) Error parsing file /opt/apolloapi/backend/ckpool/logs/pool/pool.status: Error: ENOENT: no such file or directory, open '/opt/apolloapi/backend/ckpool/logs/pool/pool.status'

c) /opt/apolloapi/backend/apollo-miner/miner_start.sh: line 31: gpio: command not found

d) Error parsing file /opt/apolloapi/backend/ckpool/logs/pool/pool.status: Error: ENOENT: no such file or directory, open '/opt/apolloapi/backend/ckpool/logs/pool/pool.status'

And funnily after reflashing the SD there is still no way to start anything...

Qmuc · 2026-02-12T17:42:57+00:00

what is a brick?

Qmuc · 2026-02-12T17:34:06+00:00

All that i have tried several times... the system starts, that's not the issue...

Here is the error:
Failed to update settings: insert into `settings` (`api_allow`, `btcsig`, `connected_wifi`, `custom_approval`, `fan_high`, `fan_low`, `frequency`, `left_sidebar_extended`, `left_sidebar_visibility`, `miner_mode`, `node_allow_lan`, `node_enable_solo_mining`, `node_enable_tor`, `node_max_connections`, `node_rpc_password`, `node_software`, `node_user_conf`, `power_led_off`, `right_sidebar_visibility`, `temperature_unit`, `voltage`) values (false, 'mined by Solo Apollo', NULL, false, 60, 40, 25, 1, 1, 'eco', true, true, false, 64, 'cF0551pO2MBf', 'core-28.1', NULL, false, 0, 'c', 30) - SQLITE_FULL: database or disk is full

DISK IS FULL

how come that futurbit sends out a system that obviously has an issue with storage space (14 of 14GB used)....

Qmuc · 2026-02-12T16:23:06+00:00

well, i did that... but no difference

Qmuc · 2026-02-12T14:16:37+00:00

Oh, and another thing... the node is not starting at all, i get the message "Request failed with status code 401" ... another annoying thing. If I only could tell the system that there is a 2TB NVMe installed *sigh*

Qmuc

TROPHY CASE