在win10通过smb整理文件时进度卡死，然后重启（从UI操作）之后挂载不上pool/Progress stuck while organizing files via smb in win10, then after reboot (operating from UI) the mount won't go on pool

TrueNAS General
, ,
41

I don’t know this command

truenas% ipmitool mc watchdog
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc watchdog
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc watchdog get result in
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc watchdog get result   
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc watchdog get       
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc watchdog    
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc         
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool   
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc watchdog get result in?
zsh: no matches found: in?
truenas% date && ipmitool mc watchdog get
Fri Aug  1 17:42:51 +07 2025
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas% ipmitool mc watchdog get 
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
truenas%

This command is for BMC?
This board have no BMC.

42

Then it’s unlikely there is a hardware watchdog triggering a reboot, and there may be another scenario that is causing it.

We will have to go looking for any OpenZFS specific parameters that would say “reboot after stalling for X seconds/minutes” and disable them, then basically let your pool run an import and “replay” all of the transactions over time to “catch up.”

1 Like
43

Are these the parameters you are talking about?
https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html

I think the following options should be relevant to the problem I’m having, but I don’t have the knowledge to fully understand them yet.

zfs_ddt_data_is_special

zfs_disable_dup_evictio

import Group

spa_load_verify_shift

spa_load_verify_metadata

spa_load_verify_maxinflight

l2arc Group

2arc_exclude_special

memory Group

zfs_arc_lotsfree_percent

zfs_arc_pc_percent

zfs_arc_sys_free

zfs_dedup_prefetch

metaslab_debug_load

There are only two options with the word reboot.

zfs_multihost_import_intervals

zfs_scan_checkpoint_intval

Does this “catch up” process have to be completed all at once? If I run the import once and then restart, will all the previous runs be wasted?

45

I got my new backplane.
Is it necessary to try the import command again? Are there any risks?

46

I run an import with the new backplane
dbgmsgbak20250815195543…txt (101.4 KB)

1755259099   metaslab.c:2445:metaslab_load_impl(): metaslab_load: txg 6823468, spa sok1001, vdev_id 0, ms_id 2660, smp_length 41280, unflushed_allocs 2153103360, unflushed_frees 442368, freed 0, defer 0 + 0, unloaded time 634836814 ms, loading_time 22 ms, ms_max_size 771137536, max size error 771100672, old_weight 740000000000001, new_weight 740000000000001
1755259099   metaslab.c:2445:metaslab_load_impl(): metaslab_load: txg 6823468, spa sok1001, vdev_id 0, ms_id 3287, smp_length 149240, unflushed_allocs 104779776, unflushed_frees 0, freed 0, defer 0 + 0, unloaded time 634836837 ms, loading_time 58 ms, ms_max_size 696844288, max size error 696844288, old_weight 740000000000001, new_weight 740000000000001
1755259099   metaslab.c:2445:metaslab_load_impl(): metaslab_load: txg 6823468, spa sok1001, vdev_id 0, ms_id 2570, smp_length 295088, unflushed_allocs 369057792, unflushed_frees 147456, freed 0, defer 0 + 0, unloaded time 634836896 ms, loading_time 83 ms, ms_max_size 452542464, max size error 452395008, old_weight 700000000000001, new_weight 700000000000001
1755259099   metaslab.c:2445:metaslab_load_impl(): metaslab_load: txg 6823468, spa sok1001, vdev_id 0, ms_id 2594, smp_length 1432, unflushed_allocs 948154368, unflushed_frees 1000980480, freed 0, defer 0 + 0, unloaded time 634836980 ms, loading_time 34 ms, ms_max_size 385769472, max size error 384417792, old_weight 700000000000001, new_weight 700000000000001
1755259100   metaslab.c:2445:metaslab_load_impl(): metaslab_load: txg 6823468, spa sok1001, vdev_id 0, ms_id 2635, smp_length 216216, unflushed_allocs 2454712320, unflushed_frees 0, freed 0, defer 0 + 0, unloaded time 634837015 ms, loading_time 54 ms, ms_max_size 491069440, max size error 491069440, old_weight 700000000000001, new_weight 700000000000001
1755259100   metaslab.c:2445:metaslab_load_impl(): metaslab_load: txg 6823468, spa sok1001, vdev_id 0, ms_id 3127, smp_length 9288, unflushed_allocs 2342596608, unflushed_frees 494702592, freed 0, defer 0 + 0, unloaded time 634837069 ms, loading_time 77 ms, ms_max_size 201265152, max size error 201142272, old_weight 6c0000000000001, new_weight 6c0000000000001
1755259100   metaslab.c:2445:metaslab_load_impl(): metaslab_load: txg 6823468, spa sok1001, vdev_id 0, ms_id 3253, smp_length 5920, unflushed_allocs 668098560, unflushed_frees 360062976, freed 0, defer 0 + 0, unloaded time 634837148 ms, loading_time 21 ms, ms_max_size 70078464, max size error 69009408, old_weight 680000000000001, new_weight 680000000000001

This section has no changes, and it seems impossible to catch up in sections