Как запустить mysql после ошибки?

Question

[Владимир Алексеев]

Как запустить mysql без повторного импорта и переустановки

У меня установлен WSL, в нею я импортировал локальную базу данных. Дамп весил 40гб. В ходе работы я заметил что phpMyAdmin подвисает и вообще работает медленно. Я запустил команду (для 4 млн строк чтобы по Left Join занулило ключ, которого не сущетсвует, т.к. отключил проверку на ключи во время дампа ), потом я передумал и захотел улучшить конфиги mysql по советам из интернета для более быстрой работы. для этого я прервал процесс а еще убил его. С тех пор у меня не работает sudo systemctl start mysql, sudo systemctl restart mysql, sudo systemctl stop mysql. Все зависает

При volodya_unix@ADMINPC:/mnt/c/Users/ADMIN$ sudo systemctl status mysql
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: activating (start) since Tue 2025-07-22 20:44:43 +10; 13min ago
Process: 252 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 324 (mysqld)
Status: "Server startup in progress"
Tasks: 13 (limit: 14352)
Memory: 1.4G
CGroup: /system.slice/mysql.service
└─324 /usr/sbin/mysqld

Jul 22 20:44:43 ADMINPC systemd[1]: Starting MySQL Community Server...

sudo tail -n 100 /var/log/mysql/error.log
2025-07-22T09:59:01.696811Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-07-22T09:59:12.361197Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.22.04.1) starting as process 5929
2025-07-22T09:59:12.376604Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-07-22T09:59:20.254481Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.22.04.1) starting as process 5977
2025-07-22T09:59:20.282040Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-07-22T09:59:20.794320Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
... (Много раз)
2025-07-22T10:00:59.101149Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
2025-07-22T10:00:59.101206Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 11 in a file operation.
2025-07-22T10:00:59.101215Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 means 'Resource temporarily unavailable'
2025-07-22T10:00:59.101232Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1'
2025-07-22T10:00:59.101239Z 1 [ERROR] [MY-012959] [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!
2025-07-22T10:00:59.101247Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file.
2025-07-22T10:00:59.169797Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2025-07-22T10:00:59.169961Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-07-22T10:00:59.169976Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-07-22T10:00:59.170391Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.42-0ubuntu0.22.04.1) (Ubuntu).
2025-07-22T10:03:39.415185Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.22.04.1) starting as process 7287
2025-07-22T10:03:40.303346Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-07-22T10:12:00.648099Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.22.04.1) starting as process 9430
2025-07-22T10:12:00.775908Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-07-22T10:25:48.225816Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.22.04.1) starting as process 16302
2025-07-22T10:25:48.289738Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-07-22T10:26:18.823279Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.22.04.1) starting as process 16575
2025-07-22T10:26:18.928363Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-07-22T10:44:43.455840Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.42-0ubuntu0.22.04.1) starting as process 324
2025-07-22T10:44:43.497292Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.

Answer 1

[Руслан Федосеев]

База убита. Начинайте заново - удалить все, начинать с нуля

Answer 2

[Alexey Dmitriev]

Нужно взять ошибки из лога - вот эти

spoiler

2025-07-22T10:00:59.101232Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1'
2025-07-22T10:00:59.101239Z 1 [ERROR] [MY-012959] [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!

и подумать, что они могут значить, что это вообще за файл. Ну или погуглить ошибки.

Comments

[Melkij]

не, тут гораздо интереснее чуть выше Operating system error number 11 in a file operation.
то есть ошибка вовсе не самого mysql, а ОС не даёт работать.