gitkeepĭrwx- 2 umbrel nx 4096 out 25 15:24 letsencrypt Skipping status update when not on Umbrel OSĭrwx- 5 umbrel nx 4096 out 25 15:24 data And if I delete it, it is kind of recreated instantly: # uptimeġ8:31:34 up 0:02, 1 user, load average: 2,10, 0,52, 0,17 Today I found something interesting, I’m not sure it’s related to the problem.īut between rebooting the server and mounting the HDD, I realized the server created “by itself” a /mnt/hdd/umbrel/lnd/ folder.

So I believe it’s something related to I/O, not to network. Note: I’m always able to open the web interface and to remotely access the server (via SSH), even when it stops syncing. I know my setup is somehow unique, but if possible I would like to keep it, because I plan installing NextCloud when I get Umbrel working flawlessly (that’s why I encrypted the HDD). It is now stopped at block 713.846 (5 hours ago).ĭo you have any ideas on what is causing this? Then I reboot the server, mount the HDD, start Umbrel, it works as normal, restarting to sync from, let’s say, 99,91%. Ls: reading directory '/mnt/hdd': Input/output error listing directories and files), I get a lot of I/O errors: # ll /mnt/hdd Although the web interface keeps saying “Running” and “100% Synchronized”, if I SSH to the server and start inspecting the HDD contents (i.e.

it downloads a block mined 1 minute ago), it stops syncing and does not download further blocks.

What’s happening is: when Bitcoin Core gets 100% synchronized (e.g.

Umbrel 0.4.9 (latest at the moment) on the HDD.

1TB HDD with a single partition encrypted with VeraCrypt.

openSUSE Leap 15.3 (Linux) on the microSD.

Download veracrypt 1.24 update7