Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-18532

Upgrade from MariaDB 10.1.37 to MariaDB 10.2.21 fails with: [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MariaDB 10.2.2, and it appears corrupted.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.2, 10.3, 10.4
    • N/A
    • None
    • Linux Gentoo

    Description

      MariaDB failed to start after upgrading from 10.1.37 to 10.2.21:
      1) upgrade package to MariaDB 10.2.21
      2) SET GLOBAL innodb_fast_shutdown=0;
      3) /etc/init.d/mysql restart

      2019-02-11 7:18:59 139738772682560 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MariaDB 10.2.2, and it appears corrupted. Please follow the instructions at https://mariadb.com/kb/en/library/upgrading/
      2019-02-11 7:18:59 139738772682560 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
      2019-02-11 7:19:00 139738772682560 [Note] InnoDB: Starting shutdown...
      2019-02-11 7:19:00 139738772682560 [ERROR] Plugin 'InnoDB' init function returned error.
      2019-02-11 7:19:00 139738772682560 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      2019-02-11 7:19:00 139738772682560 [Note] CONNECT: Version 1.06.0008 October 06, 2018
      2019-02-11 7:19:00 139738772682560 [Note] Plugin 'FEEDBACK' is disabled.
      2019-02-11 7:19:00 139738772682560 [ERROR] Unknown/unsupported storage engine: InnoDB
      2019-02-11 7:19:00 139738772682560 [ERROR] Aborting

      [mysqld]
      binlog_checksum = CRC32
      innodb_checksum_algorithm = crc32
      innodb_file_format = Barracuda
      innodb_file_per_table
      innodb_flush_log_at_trx_commit = 1
      innodb_log_checksum_algorithm = crc32
      log_slave_updates = 1
      master_verify_checksum = 1
      slave_parallel_threads = 5
      slave_sql_verify_checksum = 1
      sync_binlog = 1

      After removing ib_logfile* it started fine.

      Attachments

        Activity

          People

            marko Marko Mäkelä
            hydrapolic Tomas Mozes
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.