Skip to main content
NetApp Stage KB

Unable to start MySQL in UM due to "Unable to read page"

Last Updated:

Applies to

  • ActiveIQ Unified Manager  (UM) 9.6 +
  • OnCommand Unified Manager (UM) 9.5 and below


  • Unable to start the MySQL process in UM
  • MySQL error.log:
InnoDB: Page may be a transaction system page
2022-09-22T13:39:41.717356Z 1 [ERROR] [MY-011906] [InnoDB] Database page corruption on disk or a failed file read of page [page id: space=0, page number=5]. You may have to recover from a backup.
InnoDB: Page may be a transaction system page
2022-09-22T13:39:41.799035Z 1 [ERROR] [MY-011899] [InnoDB] [FATAL] Unable to read page [page id: space=0, page number=5] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see for more details. Aborting...
2022-09-22T13:39:41.799067Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: triggered thread 139803704239872

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.