yes identical
this is what i see in the log
1a87b900 InnoDB: Page dump in ascii and hex (16384 bytes):
nection established from mta0.minotbuildersupply.com[158.255.213.61]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
000000500000000000000000000005d113363b200070000000000000000000000000000000118d2ae00000000000000000200f20000000000000006000000000000002d000000000000002e000000
1a87b900 InnoDB: uncompressed page, stored checksum in field1 1113216988, calculated checksums for field1: crc32 2577802008, innodb 1113216988, none 37359285
ing TRX_SYS
ansaction system page
80235419904 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If
80235419904 [ERROR] InnoDB: Ending processing because of a corrupt database page.
1a87b900 InnoDB: Assertion failure in thread 140480235419904 in file ha_innodb.cc line 21950
generate a memory trap.
d bug report to https://jira.mariadb.org/
ted assertion failures or crashes, even
r the mysqld startup, there may be
e InnoDB tablespace. Please refer to
.com/doc/refman/5.6/en/forcing-innodb-recovery.html
covery.
mysqld got signal 6 ;
u hit a bug. It is also possible that this binary
it was linked against is corrupt, improperly built,
rror can also be caused by malfunctioning hardware.
https://mariadb.com/kb/en/reporting-bugs
scrape up some info that will hopefully help
t since we have already crashed,
wrong and this may fail.
MariaDB
8