Mariadb service Failed (nextcloud)

Hello, please help me, when I restart PI, mariadb works, but after a while it throws an error again.

DietPi-Services
─────────────────────────────────────────────────────
 Mode: status
[  OK  ] DietPi-Services | redis-server          active (running) since Sun 2022-11-27 09:03:13 GMT; 28min ago
[FAILED] DietPi-Services | ● mariadb.service - MariaDB 10.5.15 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-11-27 09:30:32 GMT; 1min 34s ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 1993 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 1994 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 1996 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
    Process: 2043 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 2043 (code=exited, status=1/FAILURE)
     Status: "MariaDB server is down"
        CPU: 248ms
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Plugin 'InnoDB' init function returned error.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Failed to initialize plugins.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Aborting
Nov 27 09:30:32 DietPi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 09:30:32 DietPi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Nov 27 09:30:32 DietPi systemd[1]: Failed to start MariaDB 10.5.15 database server.
[  OK  ] DietPi-Services | php7.4-fpm            active (running) since Sun 2022-11-27 09:03:17 GMT; 28min ago
[  OK  ] DietPi-Services | lighttpd              active (running) since Sun 2022-11-27 09:03:18 GMT; 28min ago
[  OK  ] DietPi-Services | cron                  active (running) since Sun 2022-11-27 09:03:18 GMT; 28min ago
[  OK  ] DietPi-Services | dropbear              active (running) since Sun 2022-11-27 09:03:12 GMT; 28min ago
[ INFO ] DietPi-Services | dietpi-vpn            inactive (dead)
[ INFO ] DietPi-Services | dietpi-cloudshell     inactive (dead)
[  OK  ] DietPi-Services | dietpi-ramlog         active (exited) since Sun 2022-11-27 09:03:12 GMT; 28min ago
[  OK  ] DietPi-Services | dietpi-preboot        active (exited) since Sun 2022-11-27 09:03:12 GMT; 28min ago
[  OK  ] DietPi-Services | dietpi-postboot       active (exited) since Sun 2022-11-27 09:03:12 GMT; 28min ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor   inactive (dead)

Probably some file system issues. Can you share following information

systemctl restart mariadb.service
journalctl -u mariadb
readlink /var/lib/mysql
readlink -f /var/lib/mysql
dmesg -l err,crit,alert,emerg

systemctl restart mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See “systemctl status mariadb.service” and “journalctl -xe” for details.

journalctl -u mariadb
-- Journal begins at Sun 2022-11-27 09:03:11 GMT, ends at Sun 2022-11-27 12:10:03 GMT. --
Nov 27 09:03:13 DietPi systemd[1]: Starting MariaDB 10.5.15 database server...
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1) starting as process 513 ...
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Uses event mutexes
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Number of pools: 1
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Using ARMv8 crc32 instructions
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Using Linux native AIO
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Completed initialization of buffer pool
Nov 27 09:03:13 DietPi mariadbd[513]: 2022-11-27  9:03:13 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=643349282,643349282
Nov 27 09:03:15 DietPi mariadbd[513]: 2022-11-27  9:03:15 0 [Note] InnoDB: Starting a batch to recover 804 pages from redo log.
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: Starting final batch to recover 11 pages from redo log.
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: 128 rollback segments are active.
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait...
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: File'./ibtmp1' size is now 12 MB.
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: 10.5.15 started; log sequence number 675661140; transaction id 2414203
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] InnoDB: Loading buffer pool(s) from /mnt/cloud/dietpi_userdata/mysql/ib_buffer_pool
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] Server socket created on IP: '127.0.0.1'.
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] Reading of all Master_info entries succeeded
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] Added new Master_info '' to hash table
Nov 27 09:03:16 DietPi mariadbd[513]: 2022-11-27  9:03:16 0 [Note] /usr/sbin/mariadbd: ready for connections.
Nov 27 09:03:16 DietPi mariadbd[513]: Version: '10.5.15-MariaDB-0+deb11u1'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 11
Nov 27 09:03:16 DietPi systemd[1]: Started MariaDB 10.5.15 database server.
Nov 27 09:03:16 DietPi /etc/mysql/debian-start[556]: Upgrading MySQL tables if necessary.
Nov 27 09:03:17 DietPi mariadbd[513]: 2022-11-27  9:03:17 0 [Note] InnoDB: Buffer pool(s) load completed at 221127  9:03:17
Nov 27 09:03:17 DietPi /etc/mysql/debian-start[560]: Looking for 'mysql' as: /usr/bin/mysql
Nov 27 09:03:17 DietPi /etc/mysql/debian-start[560]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Nov 27 09:03:17 DietPi /etc/mysql/debian-start[560]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
Nov 27 09:03:17 DietPi /etc/mysql/debian-start[560]: There is no need to run mysql_upgrade again for 10.5.15-MariaDB.
Nov 27 09:03:17 DietPi /etc/mysql/debian-start[560]: You can use --force if you still want to run mysql_upgrade
Nov 27 09:03:17 DietPi /etc/mysql/debian-start[570]: Checking for insecure root accounts.
Nov 27 09:03:17 DietPi /etc/mysql/debian-start[574]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
Nov 27 09:08:22 DietPi mariadbd[513]: 2022-11-27  9:08:22 76 [ERROR] [FATAL] InnoDB: fdatasync() returned 5
Nov 27 09:08:22 DietPi mariadbd[513]: 221127  9:08:22 [ERROR] mysqld got signal 6 ;
Nov 27 09:08:22 DietPi mariadbd[513]: This could be because you hit a bug. It is also possible that this binary
Nov 27 09:08:22 DietPi mariadbd[513]: or one of the libraries it was linked against is corrupt, improperly built,
Nov 27 09:08:22 DietPi mariadbd[513]: or misconfigured. This error can also be caused by malfunctioning hardware.
Nov 27 09:08:22 DietPi mariadbd[513]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Nov 27 09:08:22 DietPi mariadbd[513]: We will try our best to scrape up some info that will hopefully help
Nov 27 09:08:22 DietPi mariadbd[513]: diagnose the problem, but since we have already crashed,
Nov 27 09:08:22 DietPi mariadbd[513]: something is definitely wrong and this may fail.
Nov 27 09:08:22 DietPi mariadbd[513]: Server version: 10.5.15-MariaDB-0+deb11u1
Nov 27 09:08:22 DietPi mariadbd[513]: key_buffer_size=134217728
Nov 27 09:08:22 DietPi mariadbd[513]: read_buffer_size=131072
Nov 27 09:08:22 DietPi mariadbd[513]: max_used_connections=12
Nov 27 09:08:22 DietPi mariadbd[513]: max_threads=153
Nov 27 09:08:22 DietPi mariadbd[513]: thread_count=12
Nov 27 09:08:22 DietPi mariadbd[513]: It is possible that mysqld could use up toNov 27 09:08:22 DietPi mariadbd[513]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467879 K  bytes of memory
Nov 27 09:08:22 DietPi mariadbd[513]: Hope that's ok; if not, decrease some variables in the equation.
Nov 27 09:08:22 DietPi mariadbd[513]: Thread pointer: 0x7f4c001338
Nov 27 09:08:22 DietPi mariadbd[513]: Attempting backtrace. You can use the following information to find out
Nov 27 09:08:22 DietPi mariadbd[513]: where mysqld died. If you see no messages after this, something went
Nov 27 09:08:22 DietPi mariadbd[513]: terribly wrong...
Nov 27 09:08:22 DietPi mariadbd[513]: stack_bottom = 0x7fa40e0868 thread_stack 0x49000
Nov 27 09:08:22 DietPi mariadbd[513]: ??:0(my_print_stacktrace)[0x556698ee00]
Nov 27 09:08:22 DietPi mariadbd[513]: ??:0(handle_fatal_signal)[0x55664cd114]
Nov 27 09:08:22 DietPi mariadbd[1611]: addr2line: 'linux-vdso.so.1': No such file
Nov 27 09:08:22 DietPi mariadbd[513]: linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0x7fa7f78788]
Nov 27 09:08:22 DietPi mariadbd[513]: ??:0(gsignal)[0x7fa75caeac]
Nov 27 09:08:22 DietPi mariadbd[513]: ??:0(abort)[0x7fa75b7aa0]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5566873a14]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(std::unique_lock<std::mutex>::unlock())[0x55667d27b4]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55667bab10]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55667bcb90]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55667bcd50]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55667bcdf4]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5566866774]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5566866cd0]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x556676582c]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(handler::compare_key_parts(Field const&, Column_definition const&, st_key_part_info const&, st_key_part_info const&) const)[0x55664cdb8c]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(ha_commit_trans(THD*, bool))[0x55664dc028]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(trans_commit_stmt(THD*))[0x55663f01e8]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(mysql_execute_command(THD*))[0x5566307668]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x556630b230]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x556630ce8c]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(do_command(THD*))[0x556630e7c8]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(do_handle_one_connection(CONNECT*, bool))[0x55663e2858]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(handle_one_connection)[0x55663e2ab4]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55666d84f8]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(start_thread)[0x7fa79aa648]
Nov 27 09:08:23 DietPi mariadbd[513]: ??:0(clone)[0x7fa7669c1c]
Nov 27 09:08:23 DietPi mariadbd[513]: Trying to get some variables.
Nov 27 09:08:23 DietPi mariadbd[513]: Some pointers may be invalid and cause the dump to abort.
Nov 27 09:08:23 DietPi mariadbd[513]: Query (0x7f4c011160): UPDATE `oc_authtoken` SET `last_activity` = 1669540058 WHERE (`id` = 20) AND (`last_activity` < 1669540043)
Nov 27 09:08:23 DietPi mariadbd[513]: Connection ID (thread ID): 76
Nov 27 09:08:23 DietPi mariadbd[513]: Status: NOT_KILLED
Nov 27 09:08:23 DietPi mariadbd[513]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off
Nov 27 09:08:23 DietPi mariadbd[513]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
Nov 27 09:08:23 DietPi mariadbd[513]: information that should help you find out what is causing the crash.
Nov 27 09:08:23 DietPi mariadbd[513]: Writing a core file...
Nov 27 09:08:23 DietPi mariadbd[513]: Working directory at /mnt/cloud/dietpi_userdata/mysql
Nov 27 09:08:23 DietPi mariadbd[513]: Resource Limits:
Nov 27 09:08:23 DietPi mariadbd[513]: Limit                     Soft Limit    Hard Limit           Units
Nov 27 09:08:23 DietPi mariadbd[513]: Max cpu time              unlimited     unlimited            seconds
Nov 27 09:08:23 DietPi mariadbd[513]: Max file size             unlimited     unlimited            bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max data size             unlimited     unlimited            bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max stack size            8388608     unlimited            bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max core file size        0     unlimited            bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max resident set          unlimited     unlimited            bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max processes             15106      15106                processes
Nov 27 09:08:23 DietPi mariadbd[513]: Max open files            32768      32768                files
Nov 27 09:08:23 DietPi mariadbd[513]: Max locked memory         65536      65536                bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max address space         unlimited     unlimited            bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max file locks            unlimited     unlimited            locks
Nov 27 09:08:23 DietPi mariadbd[513]: Max pending signals       15106     15106                signals
Nov 27 09:08:23 DietPi mariadbd[513]: Max msgqueue size         819200     819200               bytes
Nov 27 09:08:23 DietPi mariadbd[513]: Max nice priority         0     0
Nov 27 09:08:23 DietPi mariadbd[513]: Max realtime priority     0     0
Nov 27 09:08:23 DietPi mariadbd[513]: Max realtime timeout      unlimited     unlimited            us
Nov 27 09:08:23 DietPi mariadbd[513]: Core pattern: core
Nov 27 09:08:23 DietPi systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
Nov 27 09:08:23 DietPi systemd[1]: mariadb.service: Failed with result 'signal'.Nov 27 09:08:23 DietPi systemd[1]: mariadb.service: Consumed 7.175s CPU time.
Nov 27 09:08:28 DietPi systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 1.
Nov 27 09:08:28 DietPi systemd[1]: Stopped MariaDB 10.5.15 database server.
Nov 27 09:08:28 DietPi systemd[1]: mariadb.service: Consumed 7.175s CPU time.
Nov 27 09:08:28 DietPi systemd[1]: Starting MariaDB 10.5.15 database server...
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1) starting as process 1676 ...
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [Warning] Can't create test file /var/lib/mysql/DietPi.lower-test
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] mariadbd: File '/var/lib/mysql/aria_log_control' not found (Errcode: 30 "Read-only file system")
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] mariadbd: Got error 'Can't open file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] Plugin 'Aria' init function returned error.
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] Plugin 'InnoDB' init function returned error.
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] Failed to initialize plugins.
Nov 27 09:08:28 DietPi mariadbd[1676]: 2022-11-27  9:08:28 0 [ERROR] Aborting
Nov 27 09:08:28 DietPi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 09:08:28 DietPi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Nov 27 09:08:28 DietPi systemd[1]: Failed to start MariaDB 10.5.15 database server.
Nov 27 09:11:34 DietPi systemd[1]: Starting MariaDB 10.5.15 database server...
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1) starting as process 1830 ...
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [Warning] Can't create test file /var/lib/mysql/DietPi.lower-test
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] mariadbd: File '/var/lib/mysql/aria_log_control' not found (Errcode: 30 "Read-only file system")
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] mariadbd: Got error 'Can't open file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] Plugin 'Aria' init function returned error.
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] Plugin 'InnoDB' init function returned error.
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] Failed to initialize plugins.
Nov 27 09:11:34 DietPi mariadbd[1830]: 2022-11-27  9:11:34 0 [ERROR] Aborting
Nov 27 09:11:34 DietPi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 09:11:34 DietPi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Nov 27 09:11:34 DietPi systemd[1]: Failed to start MariaDB 10.5.15 database server.
Nov 27 09:30:32 DietPi systemd[1]: Starting MariaDB 10.5.15 database server...
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1) starting as process 2043 ...
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [Warning] Can't create test file /var/lib/mysql/DietPi.lower-test
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] mariadbd: File '/var/lib/mysql/aria_log_control' not found (Errcode: 30 "Read-only file system")
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] mariadbd: Got error 'Can't open file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Plugin 'Aria' init function returned error.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Plugin 'InnoDB' init function returned error.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Failed to initialize plugins.
Nov 27 09:30:32 DietPi mariadbd[2043]: 2022-11-27  9:30:32 0 [ERROR] Aborting
Nov 27 09:30:32 DietPi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 09:30:32 DietPi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Nov 27 09:30:32 DietPi systemd[1]: Failed to start MariaDB 10.5.15 database server.
Nov 27 12:08:36 DietPi systemd[1]: Starting MariaDB 10.5.15 database server...
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1) starting as process 2810 ...
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [Warning] Can't create test file /var/lib/mysql/DietPi.lower-test
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] mariadbd: File '/var/lib/mysql/aria_log_control' not found (Errcode: 30 "Read-only file system")
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] mariadbd: Got error 'Can't open file' when trying to use aria control file '/var/lib/mysql/aria_log_control'
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] Plugin 'Aria' init function returned error.
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] Plugin 'InnoDB' init function returned error.
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] Failed to initialize plugins.
Nov 27 12:08:36 DietPi mariadbd[2810]: 2022-11-27 12:08:36 0 [ERROR] Aborting
Nov 27 12:08:36 DietPi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 12:08:36 DietPi systemd[1]: mariadb.service: Failed with result 'exit-code'.
Nov 27 12:08:36 DietPi systemd[1]: Failed to start MariaDB 10.5.15 database server.

/mnt/dietpi_userdata/mysql

/mnt/cloud/dietpi_userdata/mysql

[    0.542792] bcm2708_fb soc:fb: Unable to determine number of FBs. Disabling driver.
[  302.045163] xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead
[  302.045238] xhci_hcd 0000:01:00.0: HC died; cleaning up
[  302.061064] blk_update_request: I/O error, dev sda, sector 420704 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  302.061128] Buffer I/O error on device sda1, logical block 52332
[  302.061352] blk_update_request: I/O error, dev sda, sector 973343072 op 0x1:(WRITE) flags 0x800 phys_seg 9 prio class 0
[  302.061385] Aborting journal on device sda1-8.
[  302.061418] blk_update_request: I/O error, dev sda, sector 973342720 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  302.061436] blk_update_request: I/O error, dev sda, sector 973342720 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  302.061448] Buffer I/O error on dev sda1, logical block 121667584, lost sync page write
[  302.061468] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  302.410027] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.414089] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.417388] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.417640] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.422029] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.425394] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.425508] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.425579] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.425654] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  302.425795] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  307.837563] EXT4-fs error (device sda1): ext4_read_inode_bitmap:203: comm mariadbd: Cannot read inode bitmap - block_group = 7363, inode_bitmap = 241172499
[  307.837661] EXT4-fs error (device sda1): ext4_read_inode_bitmap:203: comm mariadbd: Cannot read inode bitmap - block_group = 7364, inode_bitmap = 241172500
[  307.837715] EXT4-fs error (device sda1): ext4_journal_check_start:83: comm mariadbd: Detected aborted journal
[  307.837734] EXT4-fs (sda1): Remounting filesystem read-only
[  307.888684] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293135: comm mariadbd: reading directory lblock 0
[  307.892246] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293135: comm mariadbd: reading directory lblock 0
[  328.471781] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  328.471878] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  328.479237] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  328.479397] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  328.807222] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  328.807390] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  329.087363] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  329.087506] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  329.103068] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  329.103325] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  334.989980] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  334.990139] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  336.454768] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  336.454912] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  337.549276] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  337.549413] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  400.627596] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[  400.627741] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[  493.759949] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293135: comm mariadbd: reading directory lblock 0
[  493.762030] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293135: comm mariadbd: reading directory lblock 0
[  699.801586] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  699.801719] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  699.983779] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  699.983947] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  700.272346] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  700.272523] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  700.440923] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  700.441131] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  700.677889] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[  700.678062] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1000.399329] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 1000.399462] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 1301.332884] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 1301.333076] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 1520.896574] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm bash: reading directory lblock 0
[ 1520.896715] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm bash: reading directory lblock 0
[ 1520.897427] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm bash: reading directory lblock 0
[ 1520.897740] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm bash: reading directory lblock 0
[ 1600.420595] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 1600.420744] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 1631.560651] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293135: comm mariadbd: reading directory lblock 0
[ 1631.562717] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293135: comm mariadbd: reading directory lblock 0
[ 1632.845792] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1632.845955] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1633.119749] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1633.119913] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1633.302761] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1633.302921] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1633.499804] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1633.500026] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 1901.212489] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 1901.212624] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 2201.373911] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 2201.374058] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 2500.783014] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 2500.783158] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 2534.641924] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2534.642154] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2534.961611] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2534.961749] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2535.149543] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2535.149643] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2535.429521] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2535.429662] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2535.592988] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2535.593188] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 2800.762274] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 2800.762409] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 3100.661426] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 3100.661564] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 3400.566746] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 3400.566894] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 3437.081579] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.081718] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.259398] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.259509] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.589815] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.589971] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.776919] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.777164] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.942898] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3437.943042] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 3700.725576] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 3700.725697] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4000.625638] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4000.625774] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4301.345855] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4301.345991] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4339.533971] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4339.534147] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4339.901794] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4339.901987] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4340.072685] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4340.072830] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4340.387371] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4340.387555] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4340.579040] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4340.579231] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 4600.415261] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4600.415402] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4900.969684] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 4900.969818] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 5200.861664] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 5200.861805] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 5390.185819] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5390.185974] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5391.123996] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5391.124176] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5391.375304] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5391.375552] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5392.167802] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5392.168059] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5392.761994] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5392.762458] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5395.545422] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5395.545576] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5399.330566] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5399.330809] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5399.917666] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5399.917826] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5501.045336] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 5501.045469] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 5612.497134] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5612.497358] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5612.814080] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5612.814333] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5613.004942] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5613.005272] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5613.202833] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5613.202999] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5613.381978] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5613.382211] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 5801.083170] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 5801.083301] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 6101.326009] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 6101.326128] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 6299.711481] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6299.711734] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6299.883073] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6299.883251] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6300.017812] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6300.017988] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6300.151596] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6300.151845] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6300.293415] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6300.293660] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6400.610489] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 6400.610616] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 6451.232455] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.232708] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.334560] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.334799] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.524457] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.524725] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.674038] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.674289] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.814692] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6451.814866] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6456.426193] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6456.426369] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6457.135158] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6457.135315] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6457.531518] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6457.531762] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6457.821206] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6457.821344] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6458.139369] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6458.139552] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6700.791280] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 6700.791415] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 6973.701493] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6973.701766] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6973.704211] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6973.704416] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6973.704532] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6973.704608] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6973.714846] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6973.715059] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6974.035058] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 6974.035219] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7001.041853] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7001.041974] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7301.081503] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7301.081634] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7601.048183] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7601.048313] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7901.289353] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7901.289475] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 7922.299900] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.300022] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.300057] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.300093] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.300133] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.300183] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.300228] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.300262] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.335396] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7922.335555] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.394964] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.395260] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.398899] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.399246] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.400275] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.400625] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.402161] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.402468] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.422312] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 7927.422458] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8200.571524] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 8200.571657] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 8500.620721] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 8500.620867] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 8800.439800] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 8800.439946] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 8851.040771] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.041217] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.044758] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.044946] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.045795] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.045992] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.046717] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.047029] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.063752] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 8851.063907] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9101.180847] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 9101.181024] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php: reading directory lblock 0
[ 9311.832316] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9311.832412] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9311.954562] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9311.954741] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9312.035335] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9312.035551] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9312.364788] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0
[ 9312.364945] EXT4-fs error (device sda1): __ext4_find_entry:1665: inode #60293121: comm php-fpm7.4: reading directory lblock 0

The USB drive or its filesystem have an issue, so MariaDB fails while trying to write to it.

Is this a 2.5" drive? If so, has it a dedicated PSU or is it powered via USB only?

SSD power via USB.
DietPi installed on microSd and nextcloud moved to SSD.

Raspberry Pi USB ports are not reliable to power SSD/HDD. This could lead to file system issues as you have now. Better to use own PSU or powered USB hub.

can you share your /etc/fstab ? We could try to comment the entry for your SSD, reboot system without SSD getting mounted and perform some file system checks

I must be doing something wrong.

root@DietPi:~# /etc/fstab
-bash: /etc/fstab: Permission denied
root@DietPi:~# etc/ fstab
-bash: etc/: No such file or directory
root@DietPi:~# /etc/ fstab
-bash: /etc/: Is a directory

Install Nextcloud on microSD and use SSD only as cloud storage?

simply get the SSD powered and you are done.

yap, it’s

cat /etc/fstab
# You can use "dietpi-drive_manager" to setup mounts.
# NB: It overwrites and re-creates physical drive mount entries on use.
#----------------------------------------------------------------
# NETWORK
#----------------------------------------------------------------
#----------------------------------------------------------------
# TMPFS
#----------------------------------------------------------------
tmpfs /tmp tmpfs size=1922M,noatime,lazytime,nodev,nosuid,mode=1777
tmpfs /var/log tmpfs size=50M,noatime,lazytime,nodev,nosuid,mode=1777
#----------------------------------------------------------------
# MISC: ecryptfs, vboxsf, glusterfs, mergerfs, bind, Btrfs subvolume
#----------------------------------------------------------------
#----------------------------------------------------------------
# SWAP SPACE
#----------------------------------------------------------------
#----------------------------------------------------------------
# PHYSICAL DRIVES
#----------------------------------------------------------------
PARTUUID=8d0105b5-02 / ext4 noatime,lazytime,rw 0 1
PARTUUID=8d0105b5-01 /boot vfat noatime,lazytime,rw 0 2

It worked all the time with an external SSD, it works for a friend too :thinking:

Yes until it’s going to fail, like in your case now.

BTW: I don’t see any mount specified for your external SSD. Can you check following

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
NAME        FSTYPE LABEL   SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID
sda                      931.5G  0 disk
└─sda1      ext4         931.5G  0 part /mnt/cloud aa2966df-204c-4444-b3a5-6085bd8d3553 acf358f8-59bf-4668-bbcc-ce2ee4aa38f8
mmcblk0                   29.7G  0 disk
├─mmcblk0p1 vfat           128M  0 part /boot      8d0105b5-01                          C01F-154E
└─mmcblk0p2 ext4          29.6G  0 part /          8d0105b5-02                          6c27bc7b-23a8-421a-a418-ae8ce3ebc457

I tried switching the USB and remounting the disk. Restart Mariadb and it works for now.

DietPi-Services
─────────────────────────────────────────────────────
 Mode: status
[  OK  ] DietPi-Services | redis-server          active (running) since Sun 2022-11-27 13:46:05 GMT; 30min ago
[  OK  ] DietPi-Services | mariadb               active (running) since Sun 2022-11-27 14:15:07 GMT; 1min 48s ago
[  OK  ] DietPi-Services | php7.4-fpm            active (running) since Sun 2022-11-27 13:46:07 GMT; 30min ago
[  OK  ] DietPi-Services | lighttpd              active (running) since Sun 2022-11-27 13:46:08 GMT; 30min ago
[  OK  ] DietPi-Services | cron                  active (running) since Sun 2022-11-27 13:46:08 GMT; 30min ago
[  OK  ] DietPi-Services | dropbear              active (running) since Sun 2022-11-27 13:46:04 GMT; 30min ago
[ INFO ] DietPi-Services | dietpi-vpn            inactive (dead)
[ INFO ] DietPi-Services | dietpi-cloudshell     inactive (dead)
[  OK  ] DietPi-Services | dietpi-ramlog         active (exited) since Sun 2022-11-27 13:46:04 GMT; 30min ago
[  OK  ] DietPi-Services | dietpi-preboot        active (exited) since Sun 2022-11-27 13:46:04 GMT; 30min ago
[  OK  ] DietPi-Services | dietpi-postboot       active (exited) since Sun 2022-11-27 13:46:04 GMT; 30min ago
[ INFO ] DietPi-Services | dietpi-wifi-monitor   inactive (dead)

your SSD is connected again? If yes, you should keep in mind it might goanna fail again.

Yes, and there is probably no other way than to buy an SSD with external power supply, right?

you could use a powered USB hub or check for a powered case where your SSD will fit in.

You could use something like this https://www.conrad.de/de/p/renkforce-festplatten-adapter-1x-usb-2-0-stecker-a-1x-sata-kombi-stecker-7-15pol-30-00-cm-schwarz-1490971.html#productDownloads
Or the most 3.5" USB cases come with an exernal power supply.

Thank you :slightly_smiling_face: so this is ideal :+1: