Thank you for the suggestion.
The tool will only run when mysql is running. Therefore I can only execute it when I have edited the my.cnf to include
innodb_force_recovery = 1
The tool then returns all tables with status : ok.
At this point mysql is running. The site is viewable but we are unable to login or process sales through woocommerce.
Error log is showing:
2018-04-16T03:59:54.580657Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-04-16T03:59:54.580677Z 0 [Note] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 5.7.17) starting as process 1199 ...
2018-04-16T03:59:54.611269Z 0 [Note] InnoDB: PUNCH HOLE support not available
2018-04-16T03:59:54.611307Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-16T03:59:54.611313Z 0 [Note] InnoDB: Uses event mutexes
2018-04-16T03:59:54.611317Z 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2018-04-16T03:59:54.611322Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-16T03:59:54.611325Z 0 [Note] InnoDB: Using Linux native AIO
2018-04-16T03:59:54.611526Z 0 [Note] InnoDB: Number of pools: 1
2018-04-16T03:59:54.611604Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-04-16T03:59:54.613324Z 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2018-04-16T03:59:54.630324Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-04-16T03:59:54.634170Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-04-16T03:59:54.668872Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-16T03:59:54.740544Z 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=0, page number=512]. You may have to recover from a backup.
2018-04-16T03:59:54.740574Z 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
Can we identify what table this page is on and correct?