After upgrading from 10.2.27 to 10.2.28 MariaDB was not starting up.
I used "innodb_force_recovery = 6" to bring the server back and found that a mysqlcheck crashed the service when checking databases using "FULLTEXT KEY" indexes.
Moving/removing those database's folders from /var/lib/mysql allowed me to restart MariaDB without innodb_force_recovery.
I was than able to recreate those databases and restore a full and working backup, but again when a restart was applyed, MariaDB crashed.

Downgrading to 10.2.27 solved the problem.

Error log was this after the update:

??2019-11-05 21:32:10 140612296050880 [Warning] InnoDB: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
2019-11-05 21:32:10 140612296050880 [Warning] InnoDB: io_setup() attempt 1.
2019-11-05 21:32:10 140612296050880 [Warning] InnoDB: io_setup() attempt 2.
2019-11-05 21:32:11 140612296050880 [Warning] InnoDB: io_setup() attempt 3.
2019-11-05 21:32:11 140612296050880 [Warning] InnoDB: io_setup() attempt 4.
2019-11-05 21:32:12 140612296050880 [Warning] InnoDB: io_setup() attempt 5.
2019-11-05 21:32:12 140612296050880 [ERROR] InnoDB: io_setup() failed with EAGAIN after 5 attempts.
2019-11-05 21:32:12 140612296050880 [Note] InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
2019-11-05 21:32:12 140612296050880 [Warning] InnoDB: Warning: Linux Native AIO disabled because _linux_create_io_ctx() failed. To get rid of this warning you can try increasing system fs.aio-max-nr to 1048576 or larger or setting innodb_use_native_aio = 0 in my.cnf??

And after adding "innodb_use_native_aio = 0", it turned to this:

??2019-11-06 01:07:25 0x7f100ce4d8c0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.28/storage/innobase/dict/dict0dict.cc line 1467
InnoDB: Failing assertion: table->can_be_evicted??

Full error log attached