Cannot find checkpoint record at LSN
When your Laragon app will get shutdown unexpected, it might cause you an issue where MySQL database will not start, and you will be redirected to log file for more details. The most common problem is “Unknown storage engine ‘Aria'”. The solution is very straight forward so don’t get stressed out. The fix is here.
As instructed by Laragon error prompt. Go to the MySQL log.
Could not open mysql.plugin table: “Unknown storage engine ‘Aria'”. Some plugins may be not loaded
The full error log in my case is placed under C:\laragon.dv\data\mariadb-10.6\mysql.log (in default installation it would be placed under C:\laragon\data\mysql\mysql.log ). If you wonder why is my path different it is because i do have multiple instances of laragon installed on my PC in different directory such as laragon.dv, laragon.bc, and laragon (default installation). I also install MariaDB engine instead default MySQL so keep that in mind to not get confused.
The error log would look something like this:
Cannot find checkpoint record at LSN (1,0x65548)
2021-12-15 15:03:16 0 [ERROR] mysqld: Aria recovery failed. Please run aria_chk -r on all Aria tables (*.MAI) and delete all aria_log.######## files
2021-12-15 15:03:16 0 [ERROR] Plugin 'Aria' init function returned error.
2021-12-15 15:03:16 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2021-12-15 15:03:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-12-15 15:03:16 0 [Note] InnoDB: Number of pools: 1
2021-12-15 15:03:16 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2021-12-15 15:03:16 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2021-12-15 15:03:16 0 [Note] InnoDB: Completed initialization of buffer pool
2021-12-15 15:03:16 0 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 234591275 is in the future! Current system log sequence number 185498210.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-12-15 15:03:16 0 [Note] InnoDB: 128 rollback segments are active.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Page [page id: space=0, page number=465] log sequence number 388269238 is in the future! Current system log sequence number 185498210.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Page [page id: space=0, page number=407] log sequence number 388269374 is in the future! Current system log sequence number 185498210.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Page [page id: space=0, page number=448] log sequence number 387834748 is in the future! Current system log sequence number 185498210.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Page [page id: space=0, page number=470] log sequence number 262503819 is in the future! Current system log sequence number 185498210.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Page [page id: space=0, page number=473] log sequence number 387808465 is in the future! Current system log sequence number 185498210.
2021-12-15 15:03:16 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-12-15 15:03:16 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-12-15 15:03:16 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-12-15 15:03:16 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2021-12-15 15:03:16 0 [Note] InnoDB: 10.6.3 started; log sequence number 185498198; transaction id 309973
2021-12-15 15:03:16 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-12-15 15:03:16 0 [Note] InnoDB: Loading buffer pool(s) from C:\laragon.dv\data\mariadb-10.6\ib_buffer_pool
2021-12-15 15:03:16 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded
2021-12-15 15:03:16 0 [ERROR] Failed to initialize plugins.
2021-12-15 15:03:16 0 [ERROR] AbortingIf you find a similar issue in your log file, you are in the right place.
This issue can occur when we shout down PC while having Laragon app started and connected to MySQL database. This will cause a crash on restart. The quick fix to the above issue is simple, to remove all files from our database folder which are prepended with a arial_log text string.
Path to below folder C:\laragon\data\mariadb-10.6 (your path might look differently, like this: C:\laragon\data\mysql depending on what database engine are you using.)
Now remove all files starting with text: arial_log.... Like in the example above. Done!
After that, stop and start your Laragon app. Your database should spin again!
Simple as that! If this tutorial did not solve your issue, fallow this instead: “Laragon database crashed“.
Let me know if this post helped solve your issue. Good luck!