TrueNAS scale - Beelink Me Mini - reboots under load

TrueNAS General
1

Hi there,
Have a new Beelink Me Mini running latest TrueNAS Scale.
Have 4 x MSI SPATIUM M450 1TB PCIe 4.0 NVMe M.2 2280 SSD and 1 x 32Gb Optane for boot

All working perfectly for a few weeks so decided to start rsyncing over my stuff from an old QNAP.
Some larger volumes came across perfectly but a volume with a bunch of smaller files reliably reboots after just a minute or so.

TrueNas reboots after a few minutes. I’ve tried:

  • remote syslog - nothing gets sent at time of reboot
  • journalctl prior boots - nothing gets logged at time of reboot
  • video the console - one time only i saw a small panic message ( one out of at least 30 attempts )
  • kdump - can’t work out how to enable this, i can see the setting in ‘system/advanced/config’ in the cli and mentioned in the middlewared python code but how to enable as it’s not exposed in the advanced gui?

setting USE_KDUMP=1 in /etc/default/kdump-tools doesn’t work - this flag gets reset back to 0 on next boot. Looking at file timestamps it’s being reset by middlewared - only message i can see related to this is:

middlewared /var/lib/systemd/coredump not mounted

which is possibly being thrown by /usr/lib/python3/dist-packages/middlewared/plugins/sysdataset.py:

        subprocess.run(['umount', '/var/lib/systemd/coredump'], check=False)
        os.makedirs('/var/lib/systemd/coredump', exist_ok=True)
        subprocess.run(['mount', '--bind', corepath, '/var/lib/systemd/coredump'])

it is mounted - at least by the time i can login:
root@truenas:/etc/default# mount|grep core
pool/.system/cores on /var/db/system/cores type zfs (rw,noatime,xattr,noacl,casesensitive)
pool/.system/cores on /var/lib/systemd/coredump type zfs (rw,noatime,xattr,noacl,casesensitive)

I guess 2 questions

  • any tips on this config? seems pretty vanilla config
  • are there docs i can’t find on enabling these features? I also see
    uploadcrash | true
    what is that feature?
  • any help to enable kdump so i can catch this panic myself and diagnose

Sorry for the long post - Thanks for reading!!

2

Did you do a thread search for Beelink? There have been a lot of problems reported with different models. Maybe try Beelilnk Support if your model is covered by the issues with NVMe

3

Hi @SmallBarky
thanks for looking at my issue

yes i’ve searched a bunch - there’s a few beelink issues with drives disconnecting but not my exact scenario that I can see.

Good idea - i’ll also reach out to Beelink support as well.

4

ok with the help of a colleague and going down all sorts of rabbit holes I have switched from CIFS mounting the QNAP SMB 1.0 volume (yes it’s an ancient TS-209 from 2007 still going strong) on the truenas host itself and rsyncing locally to

logging into the qnap and using rsync over ssh to replicate.

Been running for hours with no issue.

Nothing unusual - 43,000 files and 73G

i guess part of the original question remains - how can i enable to kdump to self-diagnose this panic?

5

Have you already put this system through a night of memtest86?
If not, I advice you to do so, just to help rule out bad RAM as the cause.

6

Also check your power budget with these PCIe 4.0 drives and the Optane boot.

7

Frequent reboots on a Beelink Mini running TrueNAS Scale typically indicate power or thermal instability. Check BIOS settings for power limits or C-states and disable turbo boosting temporarily. Monitor CPU temps under load—small form factors overheat quickly. Using a higher-wattage PSU or adding active cooling usually stabilizes performance. Also ensure ECC memory isn’t required for your setup if using ZFS.

8

hi,

Thanks to all that have replied and had a look.

I switched to NFS and it replicated the entire volume perfectly.

if i switch to CIFS it reboots within a few minutes.

So i don’t think it’s a power issue… i even saw the kernel panic fly past one time - i just couldn’t get a photo/video

My original question remains - how can i turn on kdump? Seems odd that there is config in the system but no documented way to turn it on.

Thanks!