Table is marked as crashed and last (automatic?) repair failed – MySQL / MariaDB / Percona

Today we’ll look into repairing a crashed WordPress database table. The error message could appear in one of many ways, some of them below:

[20-Oct-2019 15:28:18 UTC] WordPress database error Table 'wp_options' is marked as crashed and should be repaired for query SELECT option_value FROM wp_options WHERE option_name = 'wphb_scripts_collection' LIMIT 1 made by require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WP_Hummingbird::get_instance, WP_Hummingbird->__construct, WP_Hummingbird->init, WP_Hummingbird_Core->__construct, WP_Hummingbird_Core->load_modules, array_walk, WP_Hummingbird_Core->load_module, WP_Hummingbird_Module_Minify->run, WP_Hummingbird_Module_Minify->init_module_action, WP_Hummingbird_Sources_Collector->__construct, WP_Hummingbird_Sources_Collector::get_collection, get_option

A quick look at the error message shows the wp_options table is crashed.

Or it may look something like this in phpMyAdmin if you try to browse the table

To fix this, simply click on the checkbox next to the name of the table, scroll down and select repair table from the drop down

phpMyAdmin should come back telling you it has successfully repaired the table and that’s it!