# Unable to start mysql getting Unable to lock ./ib\_logfile0 error: 11 **URL:** \ **Category:** Percona Distribution for MySQL\ **Created:** [May 15, 2024, 5:42pm UTC](https://forums.percona.com/t/unable-to-start-mysql-getting-unable-to-lock-ib-logfile0-error-11/30342 "2024-05-15T17:42:48Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ipcmlr](https://avatars.discourse-cdn.com/v4/letter/i/df705f/32.png) [@ipcmlr](https://forums.percona.com/u/ipcmlr)\ **Post date:** [May 15, 2024, 5:42pm UTC](https://forums.percona.com/t/unable-to-start-mysql-getting-unable-to-lock-ib-logfile0-error-11/30342/1 "2024-05-15T17:42:48Z")
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](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](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](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. help. ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [May 15, 2024, 7:13pm UTC](https://forums.percona.com/t/unable-to-start-mysql-getting-unable-to-lock-ib-logfile0-error-11/30342/2 "2024-05-15T19:13:44Z")
Check SELinux. `getenforce` if that’s not disabled or permissive, then that’s the issue. Run `setenforce 0` to disable it. ---
**Author:** ![ipcmlr](https://avatars.discourse-cdn.com/v4/letter/i/df705f/32.png) [@ipcmlr](https://forums.percona.com/u/ipcmlr)\ **Post date:** [May 16, 2024, 12:54pm UTC](https://forums.percona.com/t/unable-to-start-mysql-getting-unable-to-lock-ib-logfile0-error-11/30342/3 "2024-05-16T12:54:30Z")
Thanks I think it may be some corruption on the logfile. thanks. ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [May 16, 2024, 2:25pm UTC](https://forums.percona.com/t/unable-to-start-mysql-getting-unable-to-lock-ib-logfile0-error-11/30342/4 "2024-05-16T14:25:46Z")
Then you can simply remove the redo logs and start MySQL. They will get recreated automatically.