Rebooting Every 30 secons

Hi

I’m very new to TrueNAS, but have been running debian based mass storage units with various raid configurations for many years. As we need to swap out all the drives in one of our current native debian based PM storage servers we decided to migrate the entire setup over to TN.

I have built a temporary storage box using a Asus P4T SE mobo with 6Gb RAM and a Gen 1 i7 processor, to backup all the data on one of the old debian based machines prior to swapping out all the drives, and then putting TN on that an then migrating everything back - and then aiming to repeat until finished.

Due to the need to do this a number of times and also move some VMs off another host in due course I have installed proxmox on this new machine, and passed through 3x8Tb HDDs to the new TN instance. Originally I installed TN Core 13.0 on it as this is what google directed me to when searching to TrueNAS download.

All was well and data was moving over fine to a RAID-Z array of 3x8Tb giving me just under 15Tb of formatted space. I rebooted at a convenient pint in this process to give the TN VM 3 cores and 5Gb of memory which increased the copy speed somewhat.

After realizing that I was on a depreciated version of TN, I migrated to TN 24.04 via the web GUI which went fine as per the upgrade instructions, and then subsequently went to 25.10 again via the web GUI.

All was working fine except for the odd windows ‘network error’ which went away on hitting Try Again.

However this morning out of the blue the VM is now rebooting every 30 seconds after startup for no obvious reason - before any more data copying was started - so no load on it or any major network traffic.

The TN console via the proxmox GUI shows numerous ‘out of memory’ errors and processes being shut down and then the VM reboots and loads up again. I was completely stable on 25.10 and data copying was going over at or near the network bandwidth for some time before this started happening.

Proxmox was never crashing and remained fully functional. I have tried reducing the memory available, increasing it and changing around the number of cores to see if I could find a hardware issue which has not changed anything. Shutting down the PM and running memtest86 is passing all the RAM. I have ordered more RAM to go in the machine to see if this helps, however as all was fine with 3 cores and 5Gb of RAM before I cant see this being an issue??

Its difficult to see the logs as it shuts down so quickly! I can get into var/log and just about start reading something before it goes down again.

Thanks in advance for any assistance.

Thankfully the old native debain based mass storage machines are still able to keep the production environment running, however the issue we have is we only have 20Gb left for users which will be running our shortly!

25.10. is not a stable build.

Use 24.10.2.1 or 25.04.0

Give the VM a minimum of 8GB RAM.
Dont passthrough single drives - your setting yourself up for data loss.

Sorry this should have read 25.04 as the version i am now running not 25.10

In addition to the above, I have also tried changing the VM CPU type to host in proxmox, which hasn’t made any difference.

Thanks, I am awaiting more RAM to arrive as I will need to take RAM off another VM that is being used in production at the moment.

All was fine with 5Gb without any issues.

Until it wasn’t. TrueNAS’ minimum system requirement has been 8 GB for at least ten years. And really, except for the most-minimal workloads, you should consider 16 GB as a minimum. More than that is at your discretion, but you should expect poor performance and stability with inadequate resources.

1 Like

Thanks for the input.

Can I confirm that this is normal expected behavior if it is short of memory?

Given it was maxing out the network interface for many days without issue before, and if nothing has changed in the configuration Im struggling to see why this would suddenly start happening, as its showing over 2Gb of free memory when it happens.

Whilst I would expect performances issues with a lack of RAM (raid cache etc), I wouldnt expect a stable release to just randomly reboot because of it without any warnings.

The reason I want to make sure it to exclude any other potential hardware failures before I commit to adding more and more resources to the host that may be failing?