Auxilium

Oh absolutely doing exactly that, just got the additional drives today!

So far I've experimented in Ubuntu livecd, and it has similar behavior where I can't export that pool (resource busy), if I import it as readonly=on, I can export it just fine, if I import and export the zfs cache pool that I created from within unraid, it works without any issues. Pretty sure something is wrong on ZFS side at this point, the only questions would be what exactly for unraid does the export as part of the import routine, and if it is doing the export, can it perhaps do the initial import with -o readonly=on?

As of now, `/usr/sbin/zpool export -f main` is the issue, whether it's done manually or by unraid, it hangs at this point and there's no errors at `/proc/spl/kstat/zfs/dbgmsg` 1743673194 ffff8890506cc100 spa_history.c:293:spa_history_log_sync(): command: zpool export -f main 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1536, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 817053 ms ago, max_size 4020535296 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1345, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 674740 ms ago, max_size 4294909952 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1538, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 817113 ms ago, max_size 2162425856 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1540, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 817082 ms ago, max_size 2922012672 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1542, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 817048 ms ago, max_size 2204794880 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1544, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 817041 ms ago, max_size 2284568576 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1545, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 817060 ms ago, max_size 4294901760 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1548, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 817034 ms ago, max_size 2344198144 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1551, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 816986 ms ago, max_size 2158493696 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1553, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 816940 ms ago, max_size 2284036096 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 0, ms_id 1554, weight 7c0000000000001, selected txg 16729142 (604251 ms ago), alloc_txg 0, loaded 719064 ms ago, max_size 2163531776 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1333, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817176 ms ago, max_size 4294909952 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1334, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817193 ms ago, max_size 4294033408 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1337, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817058 ms ago, max_size 4294934528 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1338, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817041 ms ago, max_size 4294868992 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1339, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817131 ms ago, max_size 4294942720 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1340, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817079 ms ago, max_size 4294959104 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1341, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817044 ms ago, max_size 4294868992 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1342, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817130 ms ago, max_size 4294803456 1743673793 ffff8890506cc100 metaslab.c:2615:metaslab_unload(): metaslab_unload: txg 16729261, spa main, vdev_id 1, ms_id 1343, weight 7c0000000000001, selected txg 16729142 (604252 ms ago), alloc_txg 0, loaded 817142 ms ago, max_size 4294950912

For zd144, mounted the pool outside of webui, and I can see it looks like a 512GB size volume, zd144 230:144 0 512G 0 disk ├─zd144p1 230:145 0 244M 0 part ├─zd144p2 230:146 0 22.4G 0 part └─zd144p3 230:147 0 489.4G 0 part I have only one volume of that size /mnt/disks/main/system filesystem none - - volume - 120G - volume - 1M - volume - 512G - volume - 240G - volume - 1M main/system 405G 8.79T 126G /mnt/disks/main/system main/system/Windows10-sz7kgd 159G 8.92T 26.8G - main/system/vm-101-disk-0 320K 8.79T 250K - main/system/vm-101-disk-1 74.5G 8.79T 74.5G - main/system/vm-106-disk-0 45.2G 8.79T 35.7G - main/system/vm-106-disk-1 291K 8.79T 221K - Which seems to be vm-101-disk-1 one, I haven't used it so deleted it now, will see if it avoids that last error. the zfs export still hangs, will leave it overnight...

I have a ZFS pool that migrated first from TrueNAS to Proxmox, and now to Unraid, problem is that despite having same hardware, I can import the zfs pool just fine manually and with webui, but if I try to export it, that export hangs forever until rebooted. When WebUI is trying to do that, the array start hangs indefinitely. There is an odd error in console, but it references devices I can't trace to specific disks... Apr 3 02:58:56 SERVER emhttpd: shcmd (145): /usr/sbin/zpool import -f -m -N -d /dev/sdg1 -d /dev/sdi1 -d /dev/sdm1 -d /dev/sdk1 -d /dev/sdf1 -d /dev/sdl1 -d /dev/sdh1 -d /dev/sdj1 5996407494583481397 main Apr 3 02:59:05 SERVER kernel: zd32: p1 p2 p3 Apr 3 02:59:05 SERVER kernel: zd48: p1 p2 p3 Apr 3 02:59:05 SERVER kernel: device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: [email protected] Apr 3 02:59:06 SERVER kernel: zd64: p1 p2 p3 p4 Apr 3 02:59:07 SERVER kernel: zd112: p1 p2 p3 p4 Apr 3 02:59:07 SERVER kernel: zd128: p1 p2 p3 p4 Apr 3 02:59:07 SERVER kernel: zd144: p1 p2 p3 Apr 3 02:59:07 SERVER emhttpd: main: zfs verify devices Apr 3 02:59:07 SERVER emhttpd: /usr/sbin/zpool status -P main 2>&1 Apr 3 02:59:07 SERVER emhttpd: pool: main Apr 3 02:59:07 SERVER emhttpd: state: ONLINE Apr 3 02:59:07 SERVER emhttpd: status: Some supported and requested features are not enabled on the pool. Apr 3 02:59:07 SERVER emhttpd: #011The pool can still be used, but some features are unavailable. Apr 3 02:59:07 SERVER emhttpd: action: Enable all features using 'zpool upgrade'. Once this is done, Apr 3 02:59:07 SERVER emhttpd: #011the pool may no longer be accessible by software that does not support Apr 3 02:59:07 SERVER emhttpd: #011the features. See zpool-features(7) for details. Apr 3 02:59:07 SERVER emhttpd: scan: scrub repaired 0B in 13:00:47 with 0 errors on Sun Mar 9 13:24:49 2025 Apr 3 02:59:07 SERVER emhttpd: config: Apr 3 02:59:07 SERVER emhttpd: #011NAME STATE READ WRITE CKSUM Apr 3 02:59:07 SERVER emhttpd: #011main ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 raidz1-0 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdg1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdi1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdm1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdk1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 raidz1-1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdf1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdl1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdh1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: #011 /dev/sdj1 ONLINE 0 0 0 Apr 3 02:59:07 SERVER emhttpd: errors: No known data errors Apr 3 02:59:07 SERVER emhttpd: main: zfs assign devices Apr 3 02:59:07 SERVER emhttpd: shcmd (146): /usr/sbin/zpool export -f main Apr 3 02:59:07 SERVER kernel: Buffer I/O error on dev zd144p3, logical block 128295120, async page read Apr 3 02:59:07 SERVER kernel: Buffer I/O error on dev zd144p1, logical block 256, async page read Apr 3 02:59:07 SERVER kernel: Buffer I/O error on dev zd144p2, logical block 32, async page read That zd144 is definitely related to the zpool, but it seems that since it tried to export it, the mapping is already removed by the time I want to see what it is. p.s. I also see a lot of udma crc errors, so probably cabling, but I've already swapped cables from backplane expander to jbod edge, out of jbod to server, and hba in the server, still looking into this... I also run a memtest with no errors. server-diagnostics-20250403-0305.zip

Unbinding the driver helps (0000:08:00.0' is card address and vfio-pci is driver name, replace either accordingly to what you have atm): echo '0000:08:00.0' > /sys/bus/pci/drivers/vfio-pci/unbind echo '0000:08:00.0' > /sys/bus/pci/drivers/vfio-pci/bind

There are real SR-IOV GPUs hitting the secondhand market now, namely Radeon Instinct Mi25, though getting them to work is still a puzzle, I am stuck at passing through the virtual function (partition virtual pcie device) as it expects vf_token that I can't see any way to specify right now in libvirt or qemu, but we're certainly going in the right direction

My Zoneminder instance also stopped working recently: root@5e51f9e7d397:/# service mysql status * /usr/bin/mysqladmin Ver 9.1 Distrib 10.3.32-MariaDB, for debian-linux-gnu on x86_64 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Server version 10.3.32-MariaDB-0ubuntu0.20.04.1 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/run/mysqld/mysqld.sock Uptime: 2 min 44 sec Threads: 6 Questions: 2 Slow queries: 0 Opens: 18 Flush tables: 1 Open tables: 11 Queries per second avg: 0.012 root@5e51f9e7d397:/# service zoneminder start Starting ZoneMinder: 01/29/22 00:22:11.848938 zmpkg[9316].INF [main:310] [Sanity checking States table...] DBD::mysql::st execute failed: Lost connection to MySQL server during query at /usr/share/perl5/ZoneMinder/Logger.pm line 600. 01/29/22 00:22:12.004642 zmpkg[9316].ERR [ZoneMinder::Logger:603] [Can't execute log entry 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )': Lost connection to MySQL server during query] DBD::mysql::st execute failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) at /usr/bin/zmpkg.pl line 317. 01/29/22 00:22:12.005063 zmpkg[9316].FAT [main:317] [Can't execute: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)] ZoneMinder failed to start root@5e51f9e7d397:/# service mysql status * /usr/bin/mysqladmin Ver 9.1 Distrib 10.3.32-MariaDB, for debian-linux-gnu on x86_64 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Server version 10.3.32-MariaDB-0ubuntu0.20.04.1 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/run/mysqld/mysqld.sock Uptime: 2 sec Threads: 6 Questions: 2 Slow queries: 0 Opens: 18 Flush tables: 1 Open tables: 11 Queries per second avg: 1.000 It seems like SQL server crashes and restarts 2022-01-29 00:22:11 0x1498c00c4700 InnoDB: Assertion failure in file /build/mariadb-10.3-ym4QNJ/mariadb-10.3-10.3.32/storage/innobase/fsp/fsp0fsp.cc line 1620 InnoDB: Failing assertion: n != ULINT_UNDEFINED InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/ InnoDB: about forcing recovery. 220129 0:22:11 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.3.32-MariaDB-0ubuntu0.20.04.1 key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=153 thread_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x149860000c48 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x1498c00c3dd8 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x32)[0x5574421125e2] /usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x557441c07ced] /lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x1498c3ccc3c0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x1498c3b0b18b] /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x1498c3aea859] /usr/sbin/mysqld(+0x4ee39d)[0x55744192439d] /usr/sbin/mysqld(+0x506444)[0x55744193c444] /usr/sbin/mysqld(+0xa8830a)[0x557441ebe30a] /usr/sbin/mysqld(+0xa88611)[0x557441ebe611] /usr/sbin/mysqld(+0xa8b724)[0x557441ec1724] /usr/sbin/mysqld(+0xa72982)[0x557441ea8982] /usr/sbin/mysqld(+0xab15c4)[0x557441ee75c4] /usr/sbin/mysqld(+0xa13509)[0x557441e49509] /usr/sbin/mysqld(+0xa14801)[0x557441e4a801] /usr/sbin/mysqld(+0xa15001)[0x557441e4b001] /usr/sbin/mysqld(+0xa255ce)[0x557441e5b5ce] /usr/sbin/mysqld(+0x977d89)[0x557441dadd89] /usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x91)[0x557441c13a81] /usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x1ad)[0x5574419e74ad] /usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xb97)[0x5574419f14e7] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1673)[0x557441a193b3] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1f3)[0x557441a1fe33] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1065)[0x557441a22205] /usr/sbin/mysqld(_Z10do_commandP3THD+0x12d)[0x557441a241bd] /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1fa)[0x557441b0760a] /usr/sbin/mysqld(handle_one_connection+0x3f)[0x557441b077df] /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609)[0x1498c3cc0609] /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x1498c3be7293] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x14986000f8a0): INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( '1643412131.84894', 'zmpkg', NULL, '9316', '0', 'INF', 'Sanity checking States table...', 'zmpkg.pl', NULL ) Connection ID (thread ID): 10 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /config/mysql Resource Limits: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size unlimited unlimited bytes Max core file size 0 0 bytes Max resident set unlimited unlimited bytes Max processes 386033 386033 processes Max open files 40960 40960 files Max locked memory unlimited unlimited bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 386033 386033 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Core pattern: core 220129 00:22:12 mysqld_safe Number of processes running now: 0 220129 00:22:12 mysqld_safe mysqld restarted 2022-01-29 0:22:12 0 [Note] /usr/sbin/mysqld (mysqld 10.3.32-MariaDB-0ubuntu0.20.04.1) starting as process 9346 ... 2022-01-29 0:22:12 0 [Note] InnoDB: Using Linux native AIO 2022-01-29 0:22:12 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-01-29 0:22:12 0 [Note] InnoDB: Uses event mutexes 2022-01-29 0:22:12 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-01-29 0:22:12 0 [Note] InnoDB: Number of pools: 1 2022-01-29 0:22:12 0 [Note] InnoDB: Using SSE2 crc32 instructions 2022-01-29 0:22:12 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2022-01-29 0:22:12 0 [Note] InnoDB: Completed initialization of buffer pool 2022-01-29 0:22:12 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2022-01-29 0:22:12 0 [Note] InnoDB: The log sequence number 25264289813 in the system tablespace does not match the log sequence number 25264290316 in the ib_logfiles! 2022-01-29 0:22:12 0 [ERROR] InnoDB: Page [page id: space=0, page number=6] log sequence number 29038180169 is in the future! Current system log sequence number 25264290325. 2022-01-29 0:22:12 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery. When attempting `mysqlcheck --all-databases`, it crashes too and this can be found in the logs 2022-01-29 0:28:39 10 [ERROR] InnoDB: Corruption of an index tree: table `zm`.`Events_Month` index `PRIMARY`, father ptr page no 169, child page no 170

Any chance fixes would have a relevant thread if applicable? This way more information can be found on the subject without searching and guessing.

Fresh Unifi Video docker does not accept default ubnt/ubnt credentials, writing is_default=true into system.properties have no effect - file is always overwritten with empty file on startup. Rebooting container once will yield it inoperable as webui would stop responding.

unRaid already have edac, but for some reason is missing edac-util It would provide much easier way to troubleshoot RAM and PCIe issues.

@DoItMyselfToo read my comment just above your first one, it have most necessary information required for you to fix it.

I and at least one more person have problem with System Temp, sensors output: root@SERVER:~# sensors Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 12: Undeclared bus id referenced sensors_init: Can't parse bus name /etc/sensors.d/sensors.conf content: # sensors chip "nct7904-i2c-0-2d" ignore "fan2" chip "nct7904-i2c-0-2d" ignore "fan4" chip "nct7904-i2c-0-2d" ignore "fan5" chip "coretemp-isa-0000" label "temp1" "CPU Temp" chip "i350bb-pci-0500" label "temp1" "MB Temp" chip "nct7904-i2c-0-2d" label "fan8" "Array Fan" It is with SuperMicro X9DA7 motherboard, and also X9DRi-LN4F+ (the other person on DataHoarding Discord) BLKMGK here have same problem: https://lime-technology.com/forums/topic/29533-dynamix-system-temp/?do=findComment&comment=657577 According to https://linux.die.net/man/5/sensors3.conf what is missing is bus statement, in my case it's bus "i2c-0" "SMBus I801 adapter at 9000" After that everything works.