TruenasScale Random Hangs

TrueNAS General
1

My NAS randomly hangs when inactive requiring a hard reset.

I tried to find the issue checking the logs and pinpoint the problem to the drive i used for the apps being faulty but after changint it the problem persists.

After more checking i think the problem is related to the network as it seems to always hang after this log line.

truenas kernel: tun: Universal TUN/TAP device driver, 1.6

Some log example:

Feb 16 16:04:31 truenas kernel: igc 0000:01:00.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3290 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3290 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3289 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3292 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3292 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3292 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="virt-aa-helper" pid=3295 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirtd" pid=3297 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirtd//qemu_bridge_helper" pid=3297 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: audit: type=1400 audit(1739718297.572:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/chronyd" pid=3296 comm="apparmor_parser"
Feb 16 16:04:57 truenas kernel: RPC: Registered named UNIX socket transport module.
Feb 16 16:04:57 truenas kernel: RPC: Registered udp transport module.
Feb 16 16:04:57 truenas kernel: RPC: Registered tcp transport module.
Feb 16 16:04:57 truenas kernel: RPC: Registered tcp-with-tls transport module.
Feb 16 16:04:57 truenas kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Feb 16 16:05:00 truenas netdata[4086]: CONFIG: cannot load cloud config '/var/lib/netdata/cloud.d/cloud.conf'. Running with internal defaults.
Feb 16 16:05:02 truenas kernel: kauditd_printk_skb: 6 callbacks suppressed
Feb 16 16:05:02 truenas kernel: audit: type=1400 audit(1739718302.776:18): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=6586 comm="apparmor_parser"
Feb 16 16:05:04 truenas kernel: bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Feb 16 16:05:04 truenas kernel: Bridge firewalling registered
Feb 16 16:05:04 truenas kernel: Initializing XFRM netlink socket
Feb 16 16:05:05 truenas kernel: tun: Universal TUN/TAP device driver, 1.6
----- HARD REBOOT
Feb 16 20:22:16 truenas syslog-ng[3338]: syslog-ng starting up; version='3.38.1'
Feb 16 20:20:47 truenas kernel: Linux version 6.6.44-production+truenas (root@tnsbuilds01.tn.ixsystems.net) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Tue Jan 28 03:14:06 UTC 2025
Feb 16 20:20:47 truenas kernel: Command line: BOOT_IMAGE=/ROOT/24.10.2@/boot/vmlinuz-6.6.44-production+truenas root=ZFS=boot-pool/ROOT/24.10.2 ro libata.allow_tpm=1 amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 intel_iommu=on zfsforce=1 nvme_core.multipath=N
Feb 16 20:20:47 truenas kernel: BIOS-provided physical RAM map:
2

Please add information about the version of TrueNAS involved as well as a detailed description of your hardware.

3

TrueNAS version: ElectricEel-24.10.2

I use a MINISFORUM Mini PC UM480 XT as a server with an AMD Ryzen 7 4800H, 16 GB RAM and a 5 bays ICY Box case for the drives.

4

Are you using VMs?

How much RAM is being consumed by non-ARC?

Does the RAM usage (of non-ARC) continuously climb after some time?

5

With that generation of Ryzen, my go-to is that crash bugs when the system is inactive may be related to a known low power instability issue.

Look for a setting in the BIOS called something similar to “Power Supply Idle Control” and set that to Typical. Not sure you will be able to do that on a Minisforum BIOS, but who knows.

If it’s not that, testing the RAM is a great next thing to look into.

1 Like
6

I checked and i don’t have any option like that in the bios, either way, the system was working fine for almost a year until a couple weeks ago.

RAM consumption seems fine and it remains stable, i will check the RAM and see if thats the problem

7

When did you update to 24.10?

There have been a fair number of people running Ryzens from around 2020 and earlier reporting instability since updating to 24.10. The cause appears to be that 24.10 is better at allowing the system go into low power states than before, exactly the thing those Ryzens handled poorly (until AMD added the option in the BIOS to control it). Without that option, I believe one could also disable C6 sleep states in the BIOS, I think that was enough, albeit less ideal.

But I am not sure if 4800H is affected, maybe, maybe not.

Anyway, next is to check your RAM.

8

February 15, but i updated to 24.10 cause i was already having this issue. It makes sense for it to be caused by some power setting as it only happens when no one is using the NAS, i will check again

9

Seems like this was the problem… i foud and disable C6 sleep in the BIOS and i had 3 days without hangs.

1 Like
10

Good to know, I hope it stays that way.