Before you do the upgrade, can you try shutting it down after setting innodb_fast_shutdown=0? That will purge the redo logs completely before shutting down. Then try the new version and see if it starts. innodb_force_recovery is a bit of a last-resort option to try before you have to resort to more advanced methods of data recovery.
On Fri, Nov 5, 2021 at 11:30 AM Karl Levik <karl.le...@gmail.com> wrote: > > (Re-sent because I forgot to include the list, sorry.) > > Hi Marc, > > That sounds frustrating. 10.4.13 is not the most recent in the 10.4 series, > so perhaps it would help to upgrade to 10.4.21 first, and then upgrade from > there to 10.5.12? > > Your error log also suggests a solution: "Retry with innodb_force_recovery=5" > - it might be worth trying that as well. > > Cheers, > Karl > > On Thu, 4 Nov 2021 at 16:45, Marc Chamberlin <m...@marcchamberlin.com> wrote: >> >> >> Hello - I have ran into a problem that maybe someone else has hit and knows >> a solution for it. I recently upgraded my OpenSuSE 15.2 x64 version to >> OpenSuSE 15.3 x64 and installed all additional updates and patches that were >> suggested for 15.3. Most of the upgrade succeeded, all except Mariadb. >> Google has not been helpful either. My understanding of Mariadb is that >> after a new install of a new version it is suppose to automagically update >> and fix the databases from the older version, when the server is restarted, >> but I think this is failing. I found the upgrade log file for Mariadb and >> it appears to be reporting some kind of corruption has occurred. This is >> preventing the mariadb (mysql) server from even starting, so it is not >> possible to use queries to find and repair the database. - >> >> bigbang:/var/tmp/mysql-protected.lBP2YQ # more log_upgrade_run.err >> 2021-10-31 12:11:36 0 [Note] InnoDB: !!! innodb_force_recovery is set to 1 >> !!! >> 2021-10-31 12:11:36 0 [Note] InnoDB: Uses event mutexes >> 2021-10-31 12:11:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 >> 2021-10-31 12:11:36 0 [Note] InnoDB: Number of pools: 1 >> 2021-10-31 12:11:36 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions >> 2021-10-31 12:11:36 0 [Note] mysqld: O_TMPFILE is not supported on /tmp >> (disabling future attempts) >> 2021-10-31 12:11:36 0 [Note] InnoDB: Using Linux native AIO >> 2021-10-31 12:11:36 0 [Note] InnoDB: Initializing buffer pool, total size = >> 134217728, chunk size = 134217728 >> 2021-10-31 12:11:36 0 [Note] InnoDB: Completed initialization of buffer pool >> 2021-10-31 12:11:36 0 [ERROR] InnoDB: corrupted TRX_NO 5f737461748dea16 >> 2021-10-31 12:11:36 0 [Note] InnoDB: Retry with innodb_force_recovery=5 >> 2021-10-31 12:11:36 0 [ERROR] InnoDB: Plugin initialization aborted with >> error Data structure corruption >> 2021-10-31 12:11:36 0 [Note] InnoDB: Starting shutdown... >> 2021-10-31 12:11:36 0 [ERROR] Plugin 'InnoDB' init function returned error. >> 2021-10-31 12:11:36 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE >> ENGINE failed. >> 2021-10-31 12:11:36 0 [Note] Plugin 'FEEDBACK' is disabled. >> 2021-10-31 12:11:36 0 [ERROR] Unknown/unsupported storage engine: InnoDB >> 2021-10-31 12:11:36 0 [ERROR] Aborting >> >> On a hunch, I decided to install the OpenSuSE OSS repository for 15.2 and >> this allowed me to drop back and install version 10.4.13-lp152.1.1 of the >> mariadb server, client, errormessages, and tools packages. (OpenSuSE 15.3 >> wants to install version 10.5.12-3.9.1 of these mariadb packages.) And lo >> and behold the previous 10.4.13-lp152.1.1 package works fine! >> >> So what gives? Any idea why the upgraded version of mariadb packages are >> failing to upgrade and support my databases? As I said I have tried Googling >> for an answer but no joy finding one. A lot of the proposed solutions, >> Google found, assume the mariadb server is up and running (hump!) so the >> example solutions given, use mysql queries and commands to fix corrupt >> databases and tables. I should also point out that AFAIK most, if not all of >> my database structures are using InnoDB and not the older MYISAM structures >> (although the mysql database itself appears to have both). I did make a >> mariadb backup of all the databases but without the ability to start the >> mariadb server I don't know how to make use of this backup file to >> reconstruct all the databases and their tables etc. >> >> Thanks in advance for any and all advice on how to upgrade my mariadb >> server. Marc Chamberlin >> >> -- >> "The Truth is out there" - Spooky >> >> -- >> _ _ . . . . . . _ _ . _ _ _ _ . >> . . . _ . . . . _ _ . _ >> _ _ . . . . _ _ . _ . . _ . _ _ >> _ _ . _ . _ . _ . _ . >> >> Computers: the final frontier. >> These are the voyages of the user Marc. >> His mission: to explore strange new hardware. >> To seek out new software and new applications. >> To boldly go where no Marc has gone before! >> >> (This email is digitally signed. My public key for sending encrypted email >> to me can be found at - >> https://keys.openpgp.org/search?q=m...@domesweetdome.us.com or just ask me >> for it and I will send it to you as an attachment. If you don't understand, >> no worries, just ignore it and/or ask me to explain it further.) >> _______________________________________________ >> Mailing list: https://launchpad.net/~maria-discuss >> Post to : maria-discuss@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~maria-discuss >> More help : https://help.launchpad.net/ListHelp > > _______________________________________________ > Mailing list: https://launchpad.net/~maria-discuss > Post to : maria-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~maria-discuss > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp