我将MAMP PRO 3.5.2版本升级到第5个，MySQL启动失败。
我通过killall -9 mysqld杀死了mysqld进程，像ib_logfile*一样清理了日志文件，并尝试使用innodb recovery进行操作。
我得到的日志如下所示：
2018-10-10T14:16:12.6NZ mysqld_safe Logging to '/Applications/MAMP/logs/mysql_error.log'.
2018-10-10T14:16:12.6NZ mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql57
2018-10-10T14:16:13.043096Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2018-10-10T14:16:13.051110Z 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.7.23) starting as process 5538 ...
2018-10-10T14:16:13.064223Z 0 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql57/ is case insensitive
2018-10-10T14:16:13.074890Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-10T14:16:13.074926Z 0 [Note] InnoDB: Uses event mutexes
2018-10-10T14:16:13.074936Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-10-10T14:16:13.074943Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-10T14:16:13.074972Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2018-10-10T14:16:13.079521Z 0 [Note] InnoDB: Number of pools: 1
2018-10-10T14:16:13.084840Z 0 [Note] InnoDB: Using CPU crc32 instructions
2018-10-10T14:16:13.089357Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-10-10T14:16:13.114376Z 0 [Note] InnoDB: Completed initialization of buffer pool
2018-10-10T14:16:13.140491Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-10T14:16:13.145746Z 0 [ERROR] InnoDB: Trying to access page number 527111 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
2018-10-10T14:16:13.145772Z 0 [ERROR] InnoDB: Server exits.
2018-10-10T14:16:13.6NZ mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
当我开始考虑卸载并重新安装 MAMP 时，希望得到任何提示，这意味着我将丢失一些本地数据库安装。
谢谢！
所以问题解决了，MySQL通过MAMP 5.1在本地运行。
在找出my.cnf出了什么问题时，应用了以下设置：
- 增加
innodb_buffer_pool_size值：innodb_buffer_pool_size = 1024M - 强制恢复模式已打开
innodb_force_recovery = 1
这导致了问题中提到的错误：
[ERROR] InnoDB: Trying to access page number 527111 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server.
此时，ibdata目录和路径的默认设置在my.cnf中未注释：
innodb_data_home_dir = "/Library/Application Support/appsolute/MAMP PRO/db/mysql57"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "/Library/Application Support/appsolute/MAMP PRO/db/mysql57"
错误日志报告了访问限制(我面前没有确切的句子(，在这里丢失了一点，作为猜测措施，我将文件夹/Library/Application Support/appsolute/MAMP PRO/db/mysql57的权限扩展到了当前用户。
这并没有改变日志。关于通往ibdata的错误路径的错误仍然存在。
最后，将文件夹重命名mysql(ibdata的完整版本(~40Gb((mysql57有所帮助。
安装 MAMP 5.1 后，/Library/Application Support/appsolute/MAMP PRO/db/中存在以下文件夹结构：
-- mysql
-- mysql56_TIMESTAMP
-- mysql57
具有相同的文件结构，但对内容的仔细比较表明，mysql中文件的完整版本，因此对其进行了重命名，并在测试后删除了所有文件夹，即 MAMP 在没有它们的情况下正常工作。
所以现在我只有一个mysql文件夹在/Library/Application Support/appsolute/MAMP PRO/db/.我在过程中自定义的my.cnf内部设置回滚。