Auxilium

Members
  • Posts

    25
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Auxilium's Achievements

Noob

Noob (1/14)

2

Reputation

  1. 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
  2. I have same issue on 6.11.5, enumeration got broken somewhere even if I have authentication working flawlessly (with usermap file)
  3. 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
  4. 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
  5. Home share is mapped to a specific user folder, for example when User1 connects to \\server\homes it will be automatically accessing /mnt/user/homes/User2 if /mnt/user/homes is set as path You can read more here: https://wiki.samba.org/index.php/Windows_User_Home_Folders
  6. Specifically a Samba [homes] share (it is special type of share) seems to requires user to have home folder defined yes, not sure why it didn't in 6.8.3 and requires now, but checking the source code, that's how it is now. Alternatively you can specify in a samba config a share that's not using [homes] functionality: [home] comment = %U home directory path = /mnt/user/<share name>/%U valid users = %S browsable = no writable = yes create mask = 0700 directory mask = 0700 When it comes to AD, honestly no idea.
  7. Okay, digging into the samba code verified my suspicion, user home location needs to be specified at passwd for [homes] to work changing `/etc/passwd` to have home directory pointing at `/mnt/user/homes/<username here>` and restarting the samba service with `/etc/rc.d/rc.samba restart` allowed me to access the share without issues, now to do that for all users at `/boot/config/passwd` and I guess the issue is resolved for me for now, and anyone having this issue will hopefully find this post useful.
  8. I had [homes] Samba working without issues for several years, (could access \\server\homes, \\server\username) Now I found that shares stopped working and server writes this message all the time when trying to access these shares: `[homes] share not available for user %s because it was not found or created at session setup time` (https://github.com/samba-team/samba/blob/master/source3/smbd/smb2_tcon.c line 265) For me it seems like when session is established, it collects users home directories and then checks it in this place, and it's empty now? Here's how it was setup in smb-extra.conf: [homes] path = /mnt/user/homes/%S comment = Home directory browsable = no read only = no valid users = %S create mask = 0700 directory mask = 0700
  9. Any chance for edac-util to be included in next iteration?
  10. Any chance fixes would have a relevant thread if applicable? This way more information can be found on the subject without searching and guessing.
  11. Unraid allows gradual (you can start with just 1 drive) and safe (adding additional drive won't stress the rest) storage expansion, and even if you need for some reason to access data independently of system, you can! mt-st support, edac-util and built-in unassigned drive functionality (so it can be used in safe mode)
  12. 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.
  13. Clean setup, it starts and then stuck at "Starting Controller Services" "Database Service" This is server.log content which is repeated as long as docker is running
  14. unRaid already have edac, but for some reason is missing edac-util It would provide much easier way to troubleshoot RAM and PCIe issues.