Truenas community edition 25.04.2.3 anl later freeze, kernel panic etc whet trying to mount damaged zfs pool

[Andrey_Novsinclair]

1. Made zfs pool of 4 disks 1tb size, type RAIDZ1
2. occasionally run server without SDA (first drive in pool)
3. Seen that pool is degraded, hot plug drive back. Truenas is not detected drive.
4. Reboot - freeze.
5. Unplug drives - boot, GUI impport pool - FREEZE
6. Unplug “failed drive”, reboot - linux shell zpool import - kernel panic, freeze.
7. Update to 25.10-BETA.1 - SAME USSUE!
   What can i do next?
   Same topic also exist in bug treker but it is closed withoit answer.

[Andrey_Novsinclair]

25.0.4.0 same

[NugentS]

Please read

Joes Rules to Asking for Help

Purpose: To assist people posting clear and informative requests for help and to define the absolute minimum information required in order to provide the helper what is needed and to reduce assumptions. EDIT: I have moved the specific areas of interest to separate entries below. Please read Joes Rules before posting anything Drive Failures Drive Speed Tests Network Issues Software Issues Build Advice Joes Rules Be considerate. This rule applies to both the person asking a question a…

[Andrey_Novsinclair]

MB: GA-H100M-H
CPU: Xeon 1225v6
BOOT: Nvme 256
HDD: 4x1 TB SATA in Z1
SMB share

25.04.0 same ussue.

[Andrey_Novsinclair]

Changed MB to Asrock AM4, CPU to Ryzen 5 3400G, 32 GB RAM, fresh install of 25.0.4.0 Still freeze, kernel panic or reboot.

[neofusion]

@Andrey_Novsinclair

Asrock AM4

It’s good that you’re being clear about the motherboard you’re using now since I’m sure Asrock only made a single board based on the AM4 platform.

Jokes aside, your initial description is anything but clear, for one, why would you intentionally run the pool in a degraded state? You’re doing a lot of hot-plugging and unplugging, are you aware of the risks associated with that? It’s starting to look like you were playing with fire and then got burnt.

You’ve still managed to not say what kind of SATA drives you have, or indeed any storage devices. Make and models may be helpful. At this stage I would say that any bug report you’ve found in the bug tracker is just as likely to be completely unrelated to your issue.

I would try importing the pool as read-only to see if that could possibly get past whatever pool corruption is causing the panics. It’s a long shot though.

As to the cause, it could be related to degraded states, the hot-plugging gone bad or perhaps a RAM issue, did you ever verify the RAM with memtest86 (4+ passes)?

[Andrey_Novsinclair]

Yesterday I tried repeating the experiment on a third test rig. Everything was different except the disks, but the result was the same. Today I downloaded the test data and rebuilt the rig in its original state. I’ll try repeating the experiment.

MB: GA-H110M-H
CPU: Xeon E3-1225v6
RAM: 2x8 GB DDR4
BOOT: Nvme 256 Adata
HDD: 4x1 TB SATA in Z1 (2xWD Black, 2xToshiba)

Test data: 500 Gb of photos and films.
SMB share.
Truenas Version: 25.04.2.4

So, the plan of action is:

1. Shoot yourself in the foot and remove the NOT first drive from the drive pool while the computer is off.
2. Turn on and boot up.
3. Make sure everything is working as expected.
4. Turn off TrueNAS and reconnect the drive.
5. Turn on the system… the results will be available this evening.