The following messages are in /var/log/mariadb/mariadb.log when I try to start mariadb:

151103 13:42:01 [Note] InnoDB: Initializing buffer pool, size = 128.0M
151103 13:42:01 [Note] InnoDB: Completed initialization of buffer pool
151103 13:42:01 [Note] InnoDB: Restoring page 0 of tablespace 0
151103 13:42:01 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
151103 13:42:01 [ERROR] InnoDB: space header page consists of zero bytes in data file ./ibdata1
151103 13:42:01 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
151103 13:42:01 [ERROR] Plugin 'InnoDB' init function returned error.

This error seems similar to this one (https://stackoverflow.com/questions/26576745/innodb-error-space-header-page-consists-of-zero-bytes-in-data-file-ibdata1 ), but this is a brand new Fedora 22 system and the database has not been used, yet.

1 Answer 1


Stop mariadb, remove ibdata1, restart.

  • you made my day ! While I wanted to end up with a huge ibdata1 file, after a big cleanup, dumping then removing all db, renaming ibdata1 to ibdata1.bak, no way to restart sql. Once again simple is beautiful !
    – Kojo
    Jan 6, 2016 at 17:28
  • Hmm. Seemed to work for me as well... Nov 7, 2016 at 15:56
  • The 'restart' notices that ibdata1 is missing, so it builds a fresh one. (Note: no data, no tables, etc, will be in this fresh one.) I do not know why "zero bytes" happened in the first place.
    – Rick James
    Nov 12, 2016 at 0:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.