TrueNAS Crashes Randomly, when rebooted i have to re-import my pool

TrueNAS General
1

Just as the title says, TrueNAS will crash randomly.

When i go to the server and check the monitor it has one line that states something along the lines of: “MiddleWare has stopped, press enter to use shell”.

At that point I physically restart the machine and TrueNAS will start 90% of the time. The other 10 percent, middleware will fail to start.

When TrueNAS does start up, I go into Storage and find that my drives have been disconnected from the Pool. The odd part is that the pool remains with 0 drives in it. In order to get back up and running I use the export/disconnect option to get rid of the ghost and then re-import my pool.

This issue was happening multiple times per day. I got rid of my LSI SAS 9207-8i and have plugged all of my drives directly into SATA connections on the motherboard. Since then I have only had one crash and that was about 72 hours after the change.

This pool has 5x10TB drives with a 500GB cache NVME.
My boot pool is 2x1TB SSD drives

I’m running off of an old ASUS prime board with a Ryzen 5 3600x.

Worst case I’ll have to buy a new board, but i’m curious if anyone else has had these problems

Thanks!

2

Hi and welcome to the forums.

It does sound like a hardware issue and the tricky part now is trying to identify what exactly. Common things to consider/explore would be overheating and another could be power related issues.

Could you provide you hardware specs in detail and someone may be able to help further.

PS: can you also share the output of zpool status from the shell?

3

You haven’t given us many things to work with, but you did mention the CPU in use.

If you haven’t already, do this:

  1. Go into your BIOS and set Power Supply Idle Control to Typical.
  2. If you can’t find that option, update your BIOS and look for it again. Mind you, updating the BIOS sometimes reset some settings, so be sure to note any changes you have done previously before you update it.
  3. If you still can’t find it, disable the C6 sleep state instead.

Your generation of CPU had an issue of falling into a deep sleep it couldn’t wake up from, the above adresses that specific issue.

I’ll add that the above may help with the crashes, not necessarily the issue of having to reimport your pool manually on restarts. So be sure to heed Johnny’s and others requests for information to troubleshoot that part further.

1 Like
4

pool: Lorge
state: DEGRADED
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
scan: resilvered 135M in 00:00:02 with 0 errors on Tue Jul 1 11:52:47 2025
config:

    NAME                                      STATE     READ WRITE CKSUM
    Lorge                                     DEGRADED     0     0     0
      raidz2-0                                DEGRADED     0     0     0
        27159403-eeb5-4f41-ac83-128f8ac32e8e  ONLINE       0     0     0
        422020c6-d027-4969-b269-fd5467f0bc16  REMOVED      0     0     0
        cb6c2542-e537-4149-8f8d-ce6a35315d64  ONLINE       0     0     0
        5377b289-45e8-4647-bc61-74ec7519aa12  ONLINE       0     0     0
        aec20ff2-cc60-49aa-b8f8-ad4b98e10b0a  ONLINE       0     0     0
    cache
      bee0999e-a0ee-4901-9ce4-d210ea1a2bd1    ONLINE       0     0     0

errors: Permanent errors have been detected in the following files:

pool: boot-pool
state: ONLINE
scan: resilvered 49.1M in 00:00:00 with 0 errors on Tue Jul 1 11:05:09 2025
config:

    NAME        STATE     READ WRITE CKSUM
    boot-pool   ONLINE       0     0     0
      mirror-0  ONLINE       0     0     0
        sda3    ONLINE       0     0     0
        sdb3    ONLINE       0     0     0

errors: No known data errors

I have removed the second drive as it started “clicking” after the last reboot.

5

Might also be worth testing your RAM but checkout what @neofusion said first.

Looks like your system is ungraciously shutting down or at least dropping your drives hence why on reboot your pool isn’t auto reimported.

It may take some time but you need to isolate the issue.

1 Like