SSD RAID 10 behind AVAGO 3108 MegaRAID incorrectly detected as HDD

[v0UwUK6CmCrjVB1PAtRb]

MySQLTuner 2.9.0 incorrectly detects an SSD RAID 10 array behind an AVAGO MegaRAID SAS 3108 controller as HDD storage.

It reports:

ℹ  Detected Storage Type: HDD
✘  innodb_flush_neighbors is disabled on HDD

It then recommends:

innodb_flush_neighbors=1

The array consists entirely of SSDs, and the current setting is intentional:

innodb_flush_neighbors=0

Environment

MySQLTuner: 2.9.0
MariaDB: 11.4.12-MariaDB-cll-lve
RAID controller: AVAGO MegaRAID SAS 3108
RAID level: RAID 10
Physical drives: SSD

Expected behaviour

MySQLTuner should detect the array as SSD-backed or report the storage type as unknown when the underlying media cannot be determined through the RAID controller.

It should not assume HDD and recommend enabling innodb_flush_neighbors unless rotational storage has been positively detected.

Impact

Following the recommendation would apply an HDD-oriented setting to SSD storage and may cause unnecessary neighbouring-page flushes.

[jmrenouard]

Hi @v0UwUK6CmCrjVB1PAtRb

Patch delivered in following PR:
#963

[jmrenouard]

Hi @v0UwUK6CmCrjVB1PAtRb ! 👋

Just following up to let you know that PR #963 has been officially merged into master and included in release v2.9.1.

Summary of the fix:

• Enhanced disk and storage detection logic to properly inspect hardware RAID controllers (including AVAGO/LSI MegaRAID SAS 3108) via /sys/block/*/queue/rotational and sysfs/CLI diagnostics.
• Fixed storage classification so SSD-backed RAID arrays are no longer misidentified as HDDs, preventing false positive recommendations for innodb_flush_neighbors.

Could you please test the latest release on your system and confirm if your SSD RAID 10 array is now accurately detected?

Thanks again for the detailed environment report and feedback! 😊🚀

[v0UwUK6CmCrjVB1PAtRb]

Hi @jmrenouard

Unfortunately, it is not resolved.

[root@censored ~]# ./mysqltuner.pl
 >>  MySQLTuner 2.9.1
         * Jean-Marie Renouard <jmrenouard@gmail.com>
         * Major Hayden <major@mhtx.net>
 >>  Bug reports, feature requests, and downloads at http://mysqltuner.pl/
 >>  Run with '--help' for additional options and output filtering
 >>  Started at: 2026-07-29 11:43:39

ℹ  Skipped version check for MySQLTuner script
ℹ  Using mysql to check login

-------- Audit Snapshot Summary --------------------------------------------------------------------
ℹ  MySQLTuner Version : 2.9.1
ℹ  Audit Start Time   : 2026-07-29 11:43:39
ℹ  Server Connection  : 127.0.0.1:3306
ℹ  Database User      : root@localhost
ℹ  Database Version   : 11.4.12-MariaDB-cll-lve
ℹ  System Physical RAM: 251.3G
ℹ  System Swap Memory : 4.0G
ℹ  Database Uptime    : 9h 16m 43s
✔  Operating on 64-bit architecture

-------- Storage Engine Statistics -----------------------------------------------------------------
ℹ  Status: +Aria +CSV +InnoDB +MEMORY +MRG_MyISAM +MyISAM +PERFORMANCE_SCHEMA +SEQUENCE
ℹ  Data in Aria tables: 32.0K (Tables: 1)
ℹ  Data in InnoDB tables: 89.6G (Tables: 75285)
ℹ  Data in MEMORY tables: 42.1M (Tables: 259)
ℹ  Data in MyISAM tables: 16.3G (Tables: 14106)
✘  Total fragmented tables: 1
✘  Table 'wizzbotn_wp_fxyi5.wp_wsm_resolutions' has an autoincrement value near max capacity (100.39%)
✘  Table 'koisraup_ksp.hbz5p_sigplus_country' has an autoincrement value near max capacity (79.61%)
✘  Table 'mailus_hizu472.ph77f_affiliates_countries' has an autoincrement value near max capacity (95.29%)
✘  Table 'mailus_hizu472.ph77f_members_countries' has an autoincrement value near max capacity (95.29%)
✘  Table 'gotoprox_wp446.wpyo_proxy_lists' has an autoincrement value near max capacity (100.00%)

✔  Currently running supported MySQL/MariaDB version 11.4.12-MariaDB-cll(LTS)

-------- Log file Recommendations ------------------------------------------------------------------
✔  log_warnings is set to 2
✔  Log file /var/lib/mysql/censored.err exists
ℹ  Log file: /var/lib/mysql/censored.err (6M)
✔  Log file /var/lib/mysql/censored.err is not empty
✔  Log file /var/lib/mysql/censored.err is smaller than 32 MB
✔  Log file /var/lib/mysql/censored.err is readable.
✘  /var/lib/mysql/censored.err contains 13776 warning(s).
✘  /var/lib/mysql/censored.err contains 1 error(s).
ℹ  1 start(s) detected in /var/lib/mysql/censored.err
ℹ  1) 2026-07-29  2:27:00 0 [Note] /usr/sbin/mariadbd: ready for connections.
ℹ  2 shutdown(s) detected in /var/lib/mysql/censored.err
ℹ  1) 2026-07-29  2:26:48 0 [Note] /usr/sbin/mariadbd: Shutdown complete
ℹ  2) 2026-07-29  2:26:47 0 [Note] Shutdown completed; log sequence number 120531545649527; transaction id 4794439219

-------- Analysis Performance Metrics --------------------------------------------------------------
ℹ  innodb_stats_on_metadata: OFF
✔  No stat updates during querying INFORMATION_SCHEMA.

-------- Views Metrics -----------------------------------------------------------------------------

-------- Triggers Metrics --------------------------------------------------------------------------

-------- Routines Metrics --------------------------------------------------------------------------

-------- Security Recommendations ------------------------------------------------------------------
ℹ  MariaDB Server - 11.4.12-MariaDB-cll
ℹ  User 'PUBLIC'@'' is User Role
✔  There are no anonymous accounts for any database users
✔  All database users have passwords assigned
✘  User 'capirefc'@% does not specify hostname restrictions.
✘  User 'capirefc_Dev'@% does not specify hostname restrictions.
✘  User 'sanctcc'@% does not specify hostname restrictions.
✘  User 'sanctcc_poke'@% does not specify hostname restrictions.
✘  User 'tapmenus'@% does not specify hostname restrictions.
✘  User 'tapmenus_eyad'@% does not specify hostname restrictions.
✘  User 'tapmenus_funder_user'@% does not specify hostname restrictions.
✘  User 'whitehor'@% does not specify hostname restrictions.
✘  User 'whitehor_healthakka'@% does not specify hostname restrictions.
✘  User 'whitehor_pharmacy'@% does not specify hostname restrictions.
✘  User 'whitehor_rocher'@% does not specify hostname restrictions.
✘  User 'whitehor_user'@% does not specify hostname restrictions.
✘  User 'whitehor_userroch'@% does not specify hostname restrictions.
✘  There is no basic password file list!

-------- SSL/TLS Security Recommendations ----------------------------------------------------------
✔  Current connection is encrypted (TLS_AES_256_GCM_SHA384)
✔  SSL support is enabled
✘  require_secure_transport is OFF
✔  Only secure TLS versions enabled: TLSv1.2,TLSv1.3
✔  TLS is active, but no explicit ssl_cert/ssl_key paths are configured (MariaDB zero-configuration TLS active)
✔  All remote users have SSL enforcement active (or no remote users exist)

-------- CVE Security Recommendations --------------------------------------------------------------
ℹ  Skipped: --cvefile option not specified

-------- Performance Metrics -----------------------------------------------------------------------
ℹ  Up for: 9h 16m 43s (86M q [2K qps], 908K conn, TX: 943G, RX: 408G)
ℹ  Reads / Writes: 96% / 4%
ℹ  Binary logging is disabled
ℹ  Physical Memory     : 251.3G
ℹ  Max MySQL memory    : 134.0G
ℹ  Other process memory: 0B
ℹ  Total buffers: 82.5G global + 131.7M per thread (400 max threads)
ℹ  Performance_schema Max memory usage: 0B
ℹ  Galera GCache Max memory usage: 0B
✔  Maximum reached memory usage: 110.3G (43.90% of installed RAM)
✔  Maximum possible memory usage: 134.0G (53.32% of installed RAM)
✔  Overall possible memory usage with other process is compatible with memory available
✔  Slow queries: 0% (508/86M)
✔  Highest usage of available connections: 54% (216/400)
✔  Aborted connections: 0.84% (7597/908351)
✔  Query cache is disabled by default due to mutex contention on multiprocessor machines.
✔  Sorts requiring temporary tables: 0% (14K temp sorts / 9M sorts)
✘  Joins performed without indexes: 22838
✔  Temporary tables created on disk: 24% (1M on disk / 5M total)
ℹ  Thread cache not used with thread pool enabled
✔  Table cache hit rate: 97% (100M hits / 102M requests)
✔  table_definition_cache (95000) is greater than number of tables (90036)
✔  Open file limit used: 2% (738/32K)
✔  Table locks acquired immediately: 99% (9M immediate / 9M locks)

-------- ThreadPool Metrics ------------------------------------------------------------------------
ℹ  ThreadPool stat is enabled.
ℹ  Thread Pool Size: 48 thread(s).
✘  ThreadPool is enabled but Max_used_connections is < 512 (216).
✔  thread_pool_size is optimal (48) for your 48 CPUs (range: 48 - 72)

-------- InnoDB Metrics ----------------------------------------------------------------------------
ℹ  InnoDB is enabled.
✘  InnoDB variable 'innodb_prefix_index_cluster_optimization' is removed in MariaDB 10.10.0.

-------- Smart Migration LTS Advisor ---------------------------------------------------------------
✔  No major migration risks detected for modern LTS versions.
✔  InnoDB File per table is activated
✔  InnoDB Buffer Pool size ( 80.0G ) under limit for 64 bits architecture: (17179869184.0G )
✘  InnoDB buffer pool / data size: 80.0G / 89.6G
ℹ  innodb_buffer_pool_chunk_size is set to 'autosize' (0) in MariaDB >= 10.8. Skipping chunk size checks.
✔  InnoDB Read buffer efficiency: 99.97% (16425676489 hits / 16429909795 total)
✔  InnoDB Write Log efficiency: 98.06% (87114655 hits / 88838559 total)
✔  InnoDB log waits: 0.00% (0 waits / 1723904 writes)

-------- InnoDB Transactions -----------------------------------------------------------------------
ℹ  Transaction Isolation Level: REPEATABLE-READ
ℹ  InnoDB Snapshot Isolation: OFF
✘  innodb_snapshot_isolation is OFF with REPEATABLE-READ (Stricter snapshot isolation is disabled)
ℹ  Active InnoDB Transactions: 1

-------- Infrastructure-Aware InnoDB Tuning --------------------------------------------------------
ℹ  Detected Storage Type: HDD
✘  innodb_flush_neighbors is disabled on HDD

-------- InnoDB Index/Data Ratio Check -------------------------------------------------------------
ℹ  Checked InnoDB tables with > 50,000 rows: 268
✘  Under-indexed tables (ratio < 0.3): 91
✘  Over-indexed tables (ratio > 0.6): 115
✔  MariaDB online temporary tablespace truncation is supported
✘  InnoDB deadlock logging (innodb_print_all_deadlocks) is disabled
ℹ  InnoDB periodic status output (innodb_status_output) is disabled
ℹ  InnoDB lock monitor output (innodb_status_output_locks) is disabled

-------- Query Cache Information -------------------------------------------------------------------
ℹ  QUERY_CACHE_INFO plugin is not active or not installed.

-------- Query Anti-Pattern Detection (Experimental) -----------------------------------------------
ℹ  Skipped: Performance Schema is disabled.

-------- Aria Metrics ------------------------------------------------------------------------------
ℹ  Aria Storage Engine is enabled.
✔  Aria pagecache size / total Aria indexes: 128.0M/1.4M
✔  Aria pagecache hit rate: 99.8% (201M cached / 317K reads)

-------- TokuDB Metrics ----------------------------------------------------------------------------
ℹ  TokuDB is disabled.

-------- XtraDB Metrics ----------------------------------------------------------------------------
ℹ  XtraDB is disabled.

-------- Galera Metrics ----------------------------------------------------------------------------
ℹ  Galera is disabled.

-------- Replication Metrics -----------------------------------------------------------------------
ℹ  Galera Synchronous replication: NO
ℹ  No replication replica(s) for this server.
ℹ  Binlog format: MIXED
ℹ  XA support enabled: ON
ℹ  Semi synchronous replication Source: OFF
ℹ  Semi synchronous replication Replica: OFF
ℹ  This is a standalone server

-------- Predictive Capacity Planning --------------------------------------------------------------
✔  Memory headroom: 121.3G (Theoretical max usage is 53.32% of physical RAM)
ℹ  Growth forecasting: Insufficient uptime (< 24h) for reliable estimation.

-------- Cluster & Replication Intelligence --------------------------------------------------------
ℹ  Replication status: Not running as a replica.
✘  binlog_format is MIXED (recommended: ROW)
✘  source_verify_checksum is disabled (recommended: ON)

-------- Security Hardening 2.0 --------------------------------------------------------------------
ℹ  TLS/SSL is enabled. Minimum supported TLS version: TLSv1.2,TLSv1.3

-------- Workload Analysis & Traffic Profiling -----------------------------------------------------
✔  Workload Characterization: Read-Heavy (96.4% reads)
✘  Auto-increment column `wizzbotn_wp_fxyi5`.`wp_wsm_resolutions`.`id` (tinyint) is near exhaustion: current value 256 (100.4% of max 255)
ℹ  Auto-increment column `koisraup_ksp`.`hbz5p_sigplus_country`.`countryid` (tinyint) has reached 79.6% capacity.
ℹ  Auto-increment column `koisraup_ksp`.`hbz5p_sigplus_language`.`langid` (tinyint) has reached 72.5% capacity.
✘  Auto-increment column `mailus_hizu472`.`ph77f_affiliates_countries`.`countryId` (tinyint) is near exhaustion: current value 243 (95.3% of max 255)
✘  Auto-increment column `mailus_hizu472`.`ph77f_members_countries`.`countryId` (tinyint) is near exhaustion: current value 243 (95.3% of max 255)
✘  Auto-increment column `gotoprox_wp446`.`wpyo_proxy_lists`.`id` (mediumint) is near exhaustion: current value 8388608 (100.0% of max 8388607)

-------- Guided Auto-Fix Snippets ------------------------------------------------------------------
Ready-to-Apply SQL Snippets (SET GLOBAL):
    SET GLOBAL innodb_snapshot_isolation = ON;
    SET GLOBAL innodb_flush_neighbors = '1 or 2 (Recommended for HDD)';

Ready-to-Apply Configuration Block ([mysqld]):
    join_buffer_size (> 1.0M, or always use indexes with JOINs)
    innodb_buffer_pool_size (>= 89.6G) if possible.
    innodb_snapshot_isolation=ON
    innodb_flush_neighbors = 1 or 2 (Recommended for HDD)

-------- Health Score KPI --------------------------------------------------------------------------
Overall Weighted Health Score: 90/100
    - Performance: 35/40
    - Security:    25/30
    - Resilience:  30/30

✔  Your database is in excellent health!


-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
    Run ALTER TABLE ... FORCE or OPTIMIZE TABLE to defragment tables for better performance
      ALTER TABLE `repparte_sp332`.`wpsp_options` FORCE; -- can free 6329 MiB
    Consider defragmenting 1 tables to free up 6329 MiB
    Check warning line(s) in /var/lib/mysql/censored.err file
    Check error line(s) in /var/lib/mysql/censored.err file
    Restrict Host for user_name@'%' to user_name@LimitedIPRangeOrLocalhost
    RENAME USER user_name@'%' TO user_name@LimitedIPRangeOrLocalhost;
    Enable require_secure_transport to force all connections to use SSL.
    MySQL was started within the last 24 hours: recommendations may be inaccurate
    Enable the slow query log to troubleshoot bad queries
    We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found.
             See https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_join_buffer_size
    Thread pool is usually only efficient for servers with max_connections >= 512
    Remove 'innodb_prefix_index_cluster_optimization' from your configuration. Always enabled.
    Enable innodb_print_all_deadlocks = ON to capture detailed transaction information in the error log when deadlocks occur.
    Consider enabling innodb_status_output_locks = ON during active lock contention troubleshooting to print lock details in SHOW ENGINE INNODB STATUS.
    Set binlog_format = ROW for robust GTID and replication consistency.
    Enable source_verify_checksum = ON (or master_verify_checksum).
    Danger of auto-increment overflow on `wizzbotn_wp_fxyi5`.`wp_wsm_resolutions`.`id`. Upgrade type to BIGINT or reset sequence.
    Danger of auto-increment overflow on `mailus_hizu472`.`ph77f_affiliates_countries`.`countryId`. Upgrade type to BIGINT or reset sequence.
    Danger of auto-increment overflow on `mailus_hizu472`.`ph77f_members_countries`.`countryId`. Upgrade type to BIGINT or reset sequence.
    Danger of auto-increment overflow on `gotoprox_wp446`.`wpyo_proxy_lists`.`id`. Upgrade type to BIGINT or reset sequence.
Variables to adjust:
    join_buffer_size (> 1.0M, or always use indexes with JOINs)
    innodb_buffer_pool_size (>= 89.6G) if possible.
    innodb_snapshot_isolation=ON
    innodb_flush_neighbors = 1 or 2 (Recommended for HDD)
✔  Terminated successfully
[root@censored~]#

[jmrenouard]

Hi @v0UwUK6CmCrjVB1PAtRb 👋

Thank you for reporting this outcome with MySQLTuner 2.9.1. I noticed this and investigated the root cause:

Root Cause Analysis

1. Linux Sysfs Limitation on HW RAID:
   mysqltuner.pl relied on reading /sys/block/*/queue/rotational. On hardware RAID controllers like AVAGO MegaRAID SAS 3108 (and LSI / PERC / SmartArray controllers), the megaraid_sas driver presents virtual drives (e.g., /dev/sda) to Linux with queue/rotational = 1 by default, even when the underlying physical array consists entirely of SSDs.
2. Ambiguous Storage Defaulting to HDD:
   Because /sys/block/sda/queue/rotational returned 1, MySQLTuner set Storage Type: HDD and recommended innodb_flush_neighbors = 1.

Resolution Strategy

1. Hardware RAID & Sysfs Inspection:
   Check /sys/block/*/device/vendor and /sys/block/*/device/model or lspci / lsblk for RAID controllers (MegaRAID, AVAGO, PERC, LSI, Smart Array).
2. Physical Media & TRIM/Discard Inspection:
   • Check /sys/block/*/queue/discard_granularity (non-zero values indicate SSD TRIM support).
   • Use storcli64 / storcli / megacli / smartctl when available to inspect physical drive types behind RAID controllers.
3. Safe Fallback (unknown):
   If a hardware RAID controller is present and physical drive media cannot be definitively confirmed as HDD, set Storage Type: unknown (or skip HDD-specific innodb_flush_neighbors advice) to prevent false positive recommendations.

We are implementing this patch in the upcoming release.