tom k.

So, I tried the other two backplanes but no dice. At this point either the cables are both dead or the entire backplane setup is dead. I tested each backplane against a drive just using the SAS-SATA forward breakout cable and the controller shows the forward breakout drive but not the backplane drive. I guess I’ll try some different 8087-8087 cables as they’re relatively cheap to replace, and if not return this chassis for a replacement.

I'm a little confused on what cables to use with my HBA. Basically, I've had my UnRAID machine up for about 2 years now, but was running out of space for new drives. I decided to grab one of there: https://www.servercase.co.uk/shop/server-cases/rackmount/4u-chassis/4u-short-length-server-case-w-16-x-35-hot-swappable-satasas-drive-bays-6gbs-minisas-+-2-x-525-bays-sc-4316s/ This has 16 hotswap bays, with 8087 connectors on the backplane. Now, I have a SuperMicro AOC-SASLP-MV8 HBA which was working great with a breakout cable back when I was using 8087 SAS to 4x SATA connectors. If I pull a drive out of my backplane and connect with that cable the drive is recognised jsut fine (so my controller isn't dead). But when I use these cables: https://www.amazon.co.uk/gp/product/B076VNM1JY/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 None of my drives are recognised. I can only think that either these cables are dead or (more likely) these are not the correct cables. The only thing that could be the case following that is that the backplane itself is dead. The reason I don't think its the backplane is all the drive LED's light up on the front (the drive sleds have fibre optic pass throughs and they light up so the drives are at least getting power!) Thanks in advance Tom

Oh no not the config folders, actually choosing "delete container and image" instead of just "delete container" from the docker menu on deleting Unless that is what you meant by configs

Right, I think I fixed it. Entirely deleting the image and the container, instead of just removing the container, and reinstalling, it now keeps the mixed setting! I have no idea why or how, but thank you for your assistance.

Yes, and once I cat from within the container it reflects the change.

Right, I purged all configs, reinstalled mariadb and pointed to the cache only appdata folder. When I attach to the docker, and cat the custom.cnf it DOES show the mixed binlog_format, its just mariadb seems to ignore this config file.

Absolutely, I'll move my dockers over there from now on. I've been doing it like this (wrong) for a while now apparently! It is now in /mnt/cache/appdata/mariadb/config but even with the config file set to MIXED mariadb loads up with STATEMENT

Ah I see, my apologies. However, changing it doesn't fix the issue. It still shows up as STATEMENT

Yes it is, /mnt/user/Configs is a cache only share, that maps to /mnt/cache/Configs

My configs for mariadb are in /mnt/cache/Configs/mariadb-nextcloud

Nope, still resets to STATEMENT

Hi, Posting these at the request of CHBMB. My MariaDB doesn't seem to want to set its binlog_format to mixed, which is presenting problems for NextCloud. My custom.cnf is basically the default just with changed binlog_format. ## custom configuration file, please be aware that changing options here may break things [mysqld_safe] nice = 0 [mysqld] max_connections = 100 connect_timeout = 5 wait_timeout = 600 max_allowed_packet = 16M thread_cache_size = 128 sort_buffer_size = 4M bulk_insert_buffer_size = 16M tmp_table_size = 32M max_heap_table_size = 32M # # * MyISAM # # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched. On error, make copy and try a repair. myisam_recover_options = BACKUP key_buffer_size = 128M #open-files-limit = 2000 table_open_cache = 400 myisam_sort_buffer_size = 512M concurrent_insert = 2 read_buffer_size = 2M read_rnd_buffer_size = 1M # # * Query Cache Configuration # # Cache only tiny result sets, so we can fit more in the query cache. query_cache_limit = 128K query_cache_size = 64M # for more write intensive setups, set to DEMAND or OFF #query_cache_type = DEMAND # # * Logging and Replication # # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. # As of 5.1 you can enable the log at runtime! #general_log_file = /config/log/mysql/mysql.log #general_log = 1 # # Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf. # # we do want to know about network errors and such log_warnings = 2 # # Enable the slow query log to see queries with especially long duration #slow_query_log[={0|1}] slow_query_log_file = /config/log/mysql/mariadb-slow.log long_query_time = 10 #log_slow_rate_limit = 1000 log_slow_verbosity = query_plan #log-queries-not-using-indexes #log_slow_admin_statements # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. #server-id = 1 #report_host = master1 #auto_increment_increment = 2 #auto_increment_offset = 1 log_bin = /config/log/mysql/mariadb-bin log_bin_index = /config/log/mysql/mariadb-bin.index # not fab for performance, but safer #sync_binlog = 1 expire_logs_days = 10 max_binlog_size = 100M # slaves #relay_log = /config/log/mysql/relay-bin #relay_log_index = /config/log/mysql/relay-bin.index #relay_log_info_file = /config/log/mysql/relay-bin.info #log_slave_updates #read_only # # If applications support it, this stricter sql_mode prevents some # mistakes like inserting invalid dates etc. #sql_mode = NO_ENGINE_SUBSTITUTION,TRADITIONAL # # * InnoDB # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! default_storage_engine = InnoDB # you can't just change log file size, requires special procedure #innodb_log_file_size = 50M innodb_buffer_pool_size = 256M innodb_log_buffer_size = 8M innodb_file_per_table = 1 innodb_open_files = 400 innodb_io_capacity = 400 innodb_flush_method = O_DIRECT # # * Security Features # # Read the manual, too, if you want chroot! # chroot = /var/lib/mysql/ # # For generating SSL certificates I recommend the OpenSSL GUI "tinyca". # # ssl-ca=/etc/mysql/cacert.pem # ssl-cert=/etc/mysql/server-cert.pem # ssl-key=/etc/mysql/server-key.pem # # * Galera-related settings # [galera] # Mandatory settings #wsrep_on=ON #wsrep_provider= #wsrep_cluster_address= binlog_format=mixed #default_storage_engine=InnoDB #innodb_autoinc_lock_mode=2 # # Allow server to accept connections on all interfaces. # #bind-address=0.0.0.0 # # Optional setting #wsrep_slave_threads=1 #innodb_flush_log_at_trx_commit=0 [mysqldump] quick quote-names max_allowed_packet = 16M [mysql] #no-auto-rehash # faster start of mysql but no tab completion [isamchk] key_buffer_size = 16M If I run: show variables like "binlog_format"; I get a binlog_format of STATEMENT (IE: default) Thanks for the help!

Hi, Having read through this thread I still can't get MariaDB (LSIO container) to keep mixed binlog mode. I've changed the custom.cnf file both from within the container, and externally using NP++ but when MariaDB starts up it just switches back to statement mode. At the moment, I'm having to use an SQL query to set the global binlog mode every time my server is rebooted. Any help would be appreciated! Thanks Tom

Hey, My instance isn't showing anything docker related - I've mapped the docker directory as describe in the post in this thread but I don't see anything docker related in the UI. Tom

Hey, Any chance of a Jackett-Public build? Now Jackett has removed all public trackers it has a little less utility than before. I believe this is the main Jackett-Public repo: https://github.com/raspdealer/Jackett Thanks!