Cannot start MySQL/MariaDB on Plesk server: Assertion failure in thread 908 in file fut0lst.ic

Symptoms

• MySQL/MariaDB server keeps crashing with the following records in /var/log/mysqld.log or /var/log/mariadb/mariadb.log files:

  CONFIG_TEXT: 190408 13:44:12 InnoDB: Assertion failure in thread 139664240350976 in file btr/btr0btr.c line 136
  InnoDB: Failing assertion: (ibool)!!page_is_comp(root) == dict_table_is_comp(index->table)
  InnoDB: We intentionally generate a memory trap.
  InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
  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: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
  InnoDB: about forcing recovery.
  12:44:12 UTC - mysqld got signal 6 ;
  InnoDB: Failing assertion: (ibool)!!page_is_comp(root) == dict_table_is_comp(index->table)
  InnoDB: We intentionally generate a memory trap.
  InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
  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: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
  InnoDB: about forcing recovery.
  12:44:12 UTC - mysqld got signal 6 ;

  OR

  CONFIG_TEXT: [FATAL] InnoDB: The page in the doublewrite buffer is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6For more information, see Help and Support Center at http://www.mysql.com.

• Cannot start MySQL (or/and Plesk SQL Server):

  CONFIG_TEXT: MySQL was stopped, attempted start - error 1067

• MySQL error log %plesk_dir%MySQL\Data\*.err or /var/log/mysql.log contains the following information:

  CONFIG_TEXT: InnoDB: Assertion failure in thread 908 in file fut0lst.ic line 83
  InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
  InnoDB: We intentionally generate a memory trap.

Cause

Severe InnoDB corruption caused by server outage or faulty RAM module.

Resolution

Apply one of the following solutions:

• Fix the InnoDB corruption according to the article:

  • How to fix InnoDB corruption cases for the MySQL/MariaDB databases on Plesk for Linux?

  • How to fix InnoDB corruption cases for the MySQL/MariaDB databases on Plesk for Windows?

• Restore the server from a snapshot

• Replace faulty RAM module(s)