MySQL startet nicht wegen Table crash

[DeeUrb]

nach einem Tipp aus dem Forum habe ich MariaDB in der shell aufgerufen und hier das Protokoll. Wie kann ich die besagte table manuell reparieren? Danke für jede Hilfe!

2023-09-07 14:56:07 0 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2023-09-07 14:56:07 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 6580
2023-09-07 14:56:07 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-09-07 14:56:07 0 [Note] InnoDB: Uses event mutexes
2023-09-07 14:56:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-09-07 14:56:07 0 [Note] InnoDB: Number of pools: 1
2023-09-07 14:56:07 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-09-07 14:56:07 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-09-07 14:56:07 0 [Note] InnoDB: Completed initialization of buffer pool
2023-09-07 14:56:07 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-09-07 14:56:07 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-09-07 14:56:07 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-09-07 14:56:07 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2023-09-07 14:56:07 0 [Note] InnoDB: Waiting for purge to start
2023-09-07 14:56:07 0 [Note] InnoDB: 10.4.28 started; log sequence number 17519540; transaction id 13650
2023-09-07 14:56:07 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2023-09-07 14:56:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-09-07 14:56:07 0 [Note] Server socket created on IP: '::'.
2023-09-07 14:56:07 0 [ERROR] mysqld: Table '.\mysql\db' is marked as crashed and last (automatic?) repair failed
2023-09-07 14:56:07 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table '.\mysql\db' is marked as crashed and last (automatic?) repair failed
2023-09-07 14:56:07 0 [ERROR] Aborting

[DeeUrb]

gelöst:
Nach erfolglosem Versuch, die db mit --innodb-force-recovery wieder herzustellen, gelang es mit dem Überschreiben der drei Dateien db.frm, db.MAD, db.MAI mit denen aus dem backup-Ordner ohne Datenverlust der WP-Installation. Lesen bildet