Mysql startet nicht

[katinka65]

Problem beim Starten MySQL
Also ich mittlerweile alles was ich im SForum gelesen habe - ausprobiert und vermute nun, dass ich mir die Datenbank ganz zerschossen habe. Aber vielleicht kann mir auch nochjemand von Euch helfen?

Das Control Panel sagt : Fehler: MySQL wurde unerwartet beendet
Mittlerweile habe ich schon das backup als data in mein Verzeichnis kopiert und auch die ibdata1 Datei aus der data old übernommen. -> erhalte aber immer noch die alte Fehlermeldung.
Bei den logs habe ich mittlerweile etwas Neues (ich glaube das hängt mit dem kopieren zusammen) :


2024-04-09 21:16:05 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-04-09 21:16:05 0 [Note] InnoDB: Waiting for purge to start
2024-04-09 21:16:05 0 [Note] InnoDB: 10.4.32 started; log sequence number 300369; transaction id 170
2024-04-09 21:16:05 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-04-09 21:16:05 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-09 21:16:05 0 [Note] Server socket created on IP: '::'.
2024-04-10 16:44:20 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 15704
2024-04-10 16:44:20 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-04-10 16:44:20 0 [Note] InnoDB: Uses event mutexes
2024-04-10 16:44:20 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-04-10 16:44:20 0 [Note] InnoDB: Number of pools: 1
2024-04-10 16:44:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-04-10 16:44:20 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-04-10 16:44:20 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-10 16:44:20 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300378
2024-04-10 16:44:20 0 [Warning] InnoDB: Are you sure you are using the right ib_logfiles to start up the database? Log sequence number in the ib_logfiles is 300378, less than the log sequence number in the first system tablespace file header, 55852598.
2024-04-10 16:44:20 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=326] with future log sequence number 33379527
2024-04-10 16:44:20 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=301] with future log sequence number 55509468
2024-04-10 16:44:20 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=285] with future log sequence number 55509197
2024-04-10 16:44:20 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=366] with future log sequence number 55509197
2024-04-10 16:44:20 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=284] with future log sequence number 55508977

das geht so weiter bis space 57 page number 5

2024-04-10 16:44:20 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 55044502 is in the future! Current system log sequence number 300396.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 53315304 is in the future! Current system log sequence number 300396.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 48821877 is in the future! Current system log sequence number 300396.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Page [page id: space=0, page number=11] log sequence number 55694219 is in the future! Current system log sequence number 300396.

auch das geht so weiter .....

2024-04-10 16:44:20 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2024-04-10 16:44:20 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2024-04-10 16:44:20 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\mysql\gtid_slave_pos.ibd' OS error: 203
2024-04-10 16:44:20 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2024-04-10 16:44:20 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2024-04-10 16:44:20 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``mysql`.`gtid_slave_pos``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2024-04-10 16:44:20 0 [Warning] InnoDB: Ignoring tablespace for `mysql`.`gtid_slave_pos` because it could not be opened.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2024-04-10 16:44:20 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2024-04-10 16:44:20 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\mysql\innodb_index_stats.ibd' OS error: 203
2024-04-10 16:44:20 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2024-04-10 16:44:20 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2024-04-10 16:44:20 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``mysql`.`innodb_index_stats``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2024-04-10 16:44:20 0 [Warning] InnoDB: Ignoring tablespace for `mysql`.`innodb_index_stats` because it could not be opened.
2024-04-10 16:44:20 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2024-04-10 16:44:20 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2024-04-10 16:44:20 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.

......

2024-04-10 16:44:20 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
2024-04-10 16:44:20 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-10 16:44:20 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
2024-04-10 16:44:20 0 [Note] InnoDB: Buffer pool(s) load completed at 240410 16:44:20
2024-04-10 16:44:20 0 [Note] Server socket created on IP: '::'.
2024-04-10 16:50:33 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 10180
2024-04-10 16:50:33 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-04-10 16:50:33 0 [Note] InnoDB: Uses event mutexes
2024-04-10 16:50:33 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-04-10 16:50:33 0 [Note] InnoDB: Number of pools: 1
2024-04-10 16:50:33 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-04-10 16:50:33 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-04-10 16:50:33 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-10 16:50:33 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 55044502 is in the future! Current system log sequence number 300405.
2024-04-10 16:50:33 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-10 16:50:33 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 53315304 is in the future! Current system log sequence number 300405.

.......
Ich will jetzt nicht den ganzen Text hier kopieren...... (kann ich bei Bedarf gerne machen....)

Mir ist nur aufgefallen, dass ich immer lese, dass ein plugin 'feedback' disabeled ist. Ich hatte gestren noch neue plugins installiert - ob es daran liegt?
Ich würde mich echt freuen, wenn mir jemand hefen könnte .....