I decided to store the blockchain on a NTFS drive with enough space. Here is the mount line in /etc/fstab:

UUID=…   /media/my_NTFS_Drive    ntfs3   rw,relatime,discard,windows_names,gid=users,fmask=0000,dmask=0000       0       0

Shortly before the initial sync was over, around 98%, I started getting errors in the log:

2026-04-06 10:27:05.533     7f5a166fa6c0        INFO    stacktrace      src/common/stack_trace.cpp:134  Exception: std::runtime_error

followed by a stacktrace. This is informative but unactionable. systemctl --user restart monerod didn't help. The log is attached.

$ cat ~/.config/systemd/user/monerod.service
[Unit]
Description=Monero Node
After=network.target

[Service]
Type=simple
ExecStart=/usr/bin/monerod \
   --data-dir /media/my_NTFS_Drive/path_to_my_monero_dir \
   --prune-blockchain \
   --log-file /media/my_NTFS_Drive/path_to_my_monero_dir/bitmonero.log \
   --non-interactive
Nice=19
IOSchedulingClass=idle
Restart=always
RestartSec=30

[Install]
WantedBy=default.target



Please fix this. (Guesses: packaging a newer version might be due, or some debugging option has to be turned on first, or the bug report has to be reassigned to the ntfs3 maintainers, ….)

Correction:

I started to get INFO messages (and not errors). Still, they are clutter.

Now I appended

Environment=MONERO_RANDOMX_UMASK=1

to the [Service] section, and these INFO messages with exceptions and stacktraces seem to be gone for now. Not sure whether this is a permanent fix or whether they will reappear and more has to be done.

 From a programming point of view on the original setup, a constantly thrown exception is wasteful; detecting the file system and adapting to its capabilities properly right from the startup of monerod would be a better way.

This is fixed in librandomx v2.0.1 which we cannot use with current monero.
So this needs backporting.

Sorry for the noise. Got the wrong issue. For this one:

Fix: Enable hugepages on the host:
sudo sysctl -w vm.nr_hugepages=1280
# Make persistent:
echo "vm.nr_hugepages=1280" | sudo tee -a /etc/sysctl.d/monero.conf

Or launch monerod without --randomx-large-pages if you explicitly set that flag.

Please note: NTFS under Linux has no mlock support, which can exacerbate the large-page issue.

If I do this, should I keep or drop

Environment=MONERO_RANDOMX_UMASK=1

in the [Service] section of ~/.config/systemd/user/monerod.service ?

I don't think I use --randomx-large-pages.

Gratefully!
Emma

We believe that the bug you reported is fixed in the latest version of
monero, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1132852@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated monero package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sun, 04 Oct 2026 17:26:32 +0200
Source: monero
Architecture: source
Version: 0.18.5.3+~0+20260428-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptocoin Team <team+cryptocoin@tracker.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1132852 1132940
Changes:
 monero (0.18.5.3+~0+20260428-1) unstable; urgency=medium
 .
   * Team upload
   * Add note on suported file systems (Closes: #1132852, #1132940)
   * New upstream version 0.18.5.3+~0+20260428
Checksums-Sha1:
 84ea76347dd333c465935d026f451c1f47a216e3 2777 monero_0.18.5.3+~0+20260428-1.dsc
 cb403be3f0656ecfdfb426a68f50ab5f975b6cf4 337695 monero_0.18.5.3+~0+20260428.orig-Xsupercop.tar.gz
 bcb2d5165f9d8f4188c031a1df09b77d8b3a774d 14196919 monero_0.18.5.3+~0+20260428.orig.tar.gz
 ac2e9f8f6f3296e3b31aee0d0c0d78b344546aa8 19332 monero_0.18.5.3+~0+20260428-1.debian.tar.xz
 fab33f54643166faa287c68509d681505b3d63a5 9176 monero_0.18.5.3+~0+20260428-1_source.buildinfo
Checksums-Sha256:
 f4b7783c27ef98d8f6531a00edbebb269e1017af40ac93687b2cffb9e08b0067 2777 monero_0.18.5.3+~0+20260428-1.dsc
 28b09708cd979124a9d5fe81d097d68b69085d57fc5a6663187dd342ef0c3486 337695 monero_0.18.5.3+~0+20260428.orig-Xsupercop.tar.gz
 4e5ddc6a04b22c93088f53b9f443710f55739d907f712ff8739b7bbf75118b80 14196919 monero_0.18.5.3+~0+20260428.orig.tar.gz
 39bb611db2bde522276cf8c11124cc2818eac900c026b47c1509a51424950168 19332 monero_0.18.5.3+~0+20260428-1.debian.tar.xz
 eddf9e74bd14213fd292f87b6a5223576ea9be1237ad573a8b9943fa6c28e587 9176 monero_0.18.5.3+~0+20260428-1_source.buildinfo
Files:
 0e0926b4443cc6ff21147affbc7abedc 2777 utils optional monero_0.18.5.3+~0+20260428-1.dsc
 7c9de8c469829e610162d0886905da5b 337695 utils optional monero_0.18.5.3+~0+20260428.orig-Xsupercop.tar.gz
 aa998b8b9bd428710ba42567ffec6bad 14196919 utils optional monero_0.18.5.3+~0+20260428.orig.tar.gz
 cd57f0bfbc972266a3d6c6ccb2aabb53 19332 utils optional monero_0.18.5.3+~0+20260428-1.debian.tar.xz
 2be67d52d22bb46b4c370b4e47ef74d7 9176 utils optional monero_0.18.5.3+~0+20260428-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmrCcNUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHRzDADExgPzmil+oTZUxgGmgxx1R0wQ5G1FUcg8
czRIDQm+AY7dtAXfgILbbSMWXE/v+85y1DKX9cpUjRV9r+D+ymyJm7zudsV6k6aJ
VkooHZjKK6eS2pKh8eAMMwhC+uR/Qv/2lJvsw2O8vWbxR3dNYK6oF53GRTW5XVrg
nf1UM9/0wgJ5U8AmJl75jK2YqY8huwjSj8S8pZGSHwgTgpUja7oD5rzKEibMDLPm
7RHAaVfZMYGgRNyteIxQd5NKCvZUy1V4w1kGwSo1qZP6W2zqyu8hYmS3xDFDH29A
KbhFvbssJyI50i8dvy2Jn5hQRh69XRy6dDkewiiCzz/8/otKrV2EEGvRPtBV/dU5
C3gQEq1ny2LUP3KlY5f+PaYt5zrjP7/ZKQNds7nwe8asN+kz8irxsUbxHWap0kAz
DtQb+Qvj1RO1Z2UPYE6MIq6AW7WeOemLtd6XdTv+LlRhlqKN9k8PhxkXT0r5qY05
JD3pWVZWJ4nYZERdueT0Y/ZHtmIbHzk=
=gw2a
-----END PGP SIGNATURE-----