Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6132

2025-06-14 11:35:29 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 15748
2025-06-14 11:35:29 0 [ERROR] mysqld.exe: File 'C:\xampp\mysql\data\aria_log.00000003' not found (Errcode: 2 "No such file or directory")
2025-06-14 11:35:29 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2025-06-14 11:35:29 0 [Note] InnoDB: Uses event mutexes
2025-06-14 11:35:29 0 [Note] InnoDB: Compressed tables use zlib 1.3
2025-06-14 11:35:29 0 [Note] InnoDB: Number of pools: 1
2025-06-14 11:35:29 0 [Note] InnoDB: Using SSE2 crc32 instructions
2025-06-14 11:35:29 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2025-06-14 11:35:29 0 [Note] InnoDB: Completed initialization of buffer pool
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\cursillo_db\users.ibd' OS error: 71
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``cursillo_db`.`users``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2025-06-14 11:35:29 0 [Warning] InnoDB: Ignoring tablespace for `cursillo_db`.`users` because it could not be opened.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-14 11:35:29 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-14 11:35:29 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\diary\entries.ibd' OS error: 203
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``diary`.`entries``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2025-06-14 11:35:29 0 [Warning] InnoDB: Ignoring tablespace for `diary`.`entries` because it could not be opened.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\test\images.ibd' OS error: 71
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`images``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2025-06-14 11:35:29 0 [Warning] InnoDB: Ignoring tablespace for `test`.`images` because it could not be opened.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\test\locations.ibd' OS error: 71
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`locations``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2025-06-14 11:35:29 0 [Warning] InnoDB: Ignoring tablespace for `test`.`locations` because it could not be opened.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\test\pictures.ibd' OS error: 71
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`pictures``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2025-06-14 11:35:29 0 [Warning] InnoDB: Ignoring tablespace for `test`.`pictures` because it could not be opened.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\test\weekends.ibd' OS error: 71
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``test`.`weekends``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2025-06-14 11:35:29 0 [Warning] InnoDB: Ignoring tablespace for `test`.`weekends` because it could not be opened.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2025-06-14 11:35:29 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2025-06-14 11:35:29 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2025-06-14 11:35:29 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\upload_image\images.ibd' OS error: 203
2025-06-14 11:35:29 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2025-06-14 11:35:29 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2025-06-14 11:35:29 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``upload_image`.`images``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2025-06-14 11:35:29 0 [Warning] InnoDB: Ignoring tablespace for `upload_image`.`images` because it could not be opened.
2025-06-14 11:35:29 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2025-06-14 11:35:29 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2025-06-14 11:35:29 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2025-06-14 11:35:29 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2025-06-14 11:35:29 0 [Note] InnoDB: Waiting for purge to start
2025-06-14 11:35:29 0 [Note] InnoDB: 10.4.32 started; log sequence number 5909303; transaction id 11521
2025-06-14 11:35:29 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2025-06-14 11:35:29 0 [Note] InnoDB: Buffer pool(s) load completed at 250614 11:35:29
2025-06-14 11:35:29 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-06-14 11:35:29 0 [Note] Server socket created on IP: '::'.
2025-06-14 11:35:29 0x3390 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6132
InnoDB: Failing assertion: slot
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
250614 11:35:29 [ERROR] mysqld got exception 0x80000003 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.4.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
2025-06-14 11:35:29 0x425c InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6132
InnoDB: Failing assertion: slot
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.