when mariadb eventually fails to start it ALWAYS takes unnecessarily long

when "service mysql start" fails, it ALWAYS takes up too much time, ~ half a minute

no matter what the error/problem is, it will keep displaying dots of the "progress bar" as if trying to start up - after the irrecoverable error has already been encountered

See the screenshot for example: the log reports work "ended" half a minute before mariadb starting command actually exits