text: ERROR: Module mpm_prefork is enabled – cannot proceed due to conflicts. It needs to be disabled first!
  In this blog we will cover the proper way to upgrade mysql as to not to get this problem. While I’m not saying this covers all steps mysql/mariadb upgrade, its a good lesson on what to expect if upgrade is done incorrectly.
  Because I use InnoDB there is no recovery/repair options because it not suppose to crash? The logs talk about
  In order to do anything I had to get mysql started. We need to start the recovery mode. Read online but we are starting from 1, then take one step at a time.
  https://blog.ghost3k.net/articles/mysql/169/fixing-mysql-innodb-index-corruption [Deals with possibly using optimize command to fix the table, in my case as soon as I did anything to a broken table mariadb/mysql server crashed and need to be restarted. This Article was helpful to learn the thought process]
  https://forums.cpanel.net/resources/innodb-corruption-repair-guide.395/ [helpful in the trying to find the issue, after that it gets into drop, create insert data which I didn’t want to do]
  https://mariadb.com/kb/en/library/innodb-recovery-under-maria/+comments/354 [Comments on recovery in InnoDB and how it not suppose to crash, I’m running on bare hardware so not virtualized ]
  https://serversforhackers.com/c/mysqldump-with-modern-mysql [Trying to mysqldump after upgrade and crash to see if I can export data before I’m forced to completely corrupt the data, first mention the PV program]
  https://mariadb.com/kb/en/library/innodb-data-dictionary-troubleshooting/ [This now gets toward the end aka playing with .ibd and .frm files which are files that mysql uses to store data. I was not able to use this info other to learn the process of possible recovery]
  https://bugs.mysql.com/bug.php?id=67179 [Similar issue as mine, Tablespace is missing for table ‘mysql/innodb_index_stats’ , this one is for windows so not related but good to see how they troubleshoot]
  As I proceed from 1 to 2 to 3, googling this exact search yelded few links “innodb_force_recovery = 4”
  [https://dba.stackexchange.com/questions/65728/forcing-innodb-recovery-of-a-corrupted-database] Getting dangerous. At this point the hopes of recovery are low, and knowing we have a full dump prior to upgrade we are forcing innodb recovery of corrupter database. Please note that if this is bad. copy mysql folders to make a copy of db files if need be.
  [https://bugs.mysql.com/bug.php?id=67595] Mysqlbug that has similar errors as mine, except it was running Windows Enterprise 64bit