Unable to start mysql getting Unable to lock ./ib_logfile0 error: 11

Today we are trying to upgrade our OS. But I was getting Unable to lock ./ib_logfile0 error: 11 .
I asked that the server be reverted back but i am still getting the same issue.

I am unable to start the mysql server.
I keep getting a Unable to lock ./ib_logfile0 error: 11 but i do not see anything locking the file.

Previous to that when the server started, it automatically tried to start the server and I got a
2024-05-15T13:08:24.295729-04:00 659 [Note] [MY-010014] [Repl] While initializing dump thread for slave with UUID <80197574-422e-11ec-90f9-005056bae9dc>, found a zombie dump thread with the same UUID. Master is killing the zombie dump thread(654).
2024-05-15T13:08:40.759073-04:00 0 [Warning] [MY-012638] [InnoDB] Retry attempts for writing partial data failed.
2024-05-15T13:08:40.759166-04:00 0 [ERROR] [MY-012639] [InnoDB] Write to file ./#ib_16384_12.dblwr failed at offset 0, 65536 bytes should have been written, only 0 were written. Operating system error number 5. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2024-05-15T13:08:40.760360-04:00 0 [ERROR] [MY-012640] [InnoDB] Error number 5 means ‘Input/output error’
2024-05-15T13:08:40.760387-04:00 0 [Note] [MY-012641] [InnoDB] Some operating system error numbers are described at http://dev.mysql.com/doc/refman/8.0/en/operating-system-error-codes.html
2024-05-15T13:08:40.761082-04:00 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: buf0dblwr.cc:662:err == DB_SUCCESS || err == DB_TABLESPACE_DELETED thread 140047029339904
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:08:40 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.

I have enough space in my data directory so I do not know what is causing the server to not start.

Check SELinux. getenforce if that’s not disabled or permissive, then that’s the issue. Run setenforce 0 to disable it.

1 Like

Thanks I think it may be some corruption on the logfile. thanks.

Then you can simply remove the redo logs and start MySQL. They will get recreated automatically.