Can’t start MariaDB: Assertion failure in thread 908 in file fut0lst.ic

Symptoms

• Can't start MariaDB and/or Plesk SQL Server

  MySQL was stopped, attempted start - error 1067

• The following error is logged to /var/log/mysql.log or %plesk_dir%MySQLData*.err

  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.

• The MariaDB server keeps crashing, with the following records in /var/log/mysqld.log or /var/log/mariadb/mariadb.log

  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 ;

  [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.

Cause

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

Resolution

1. Replace the faulty RAM module(s) with the help of the hosting provider (if applicable)
2. Recover the databases where possible, as instructed in the appropriate guide for the system:
   • 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?