After the update, nextcloud stopped working for me

for the VPN, open dietpi-vpn and disable/remove the configuration.

For NC, it seems like a mismatch between NC database and what is present on file system level. Let’s try to find out which location NC is using.

cat /var/www/nextcloud/config/config.php | grep datadirectory

Inside NC, can you try to create a new demo file called dietpi.test.file. Important, it needs to be called exactly like this as we need to search for it. Check where it is located on your file system.

find / -name "dietpi.test.file"
'datadirectory' => '/mnt/dietpi_userdata/nextcloud_data',

and how should I create the file, I tried directly in NC using the web interface, but it gave the error “cannot create file”

can you share following

readlink /mnt/dietpi_userdata/
readlink -f /mnt/dietpi_userdata/
ls -la /mnt/dietpi_userdata/nextcloud_data
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
df -h
dmesg -l 0,1,2,3
root@DietPi:~# readlink -f /mnt/dietpi_userdata/
/mnt/cloud/dietpi_userdata
root@DietPi:~# ls -la /mnt/dietpi_userdata/nextcloud_data
total 111236
drwxrwx--- 6 www-data www-data      4096 Sep 26 23:15 .
drwxrwxr-x 8 dietpi   dietpi        4096 Nov  2  2022 ..
-rw-r--r-- 1 www-data www-data       542 Nov 19  2022 .htaccess
-rw-r--r-- 1 www-data www-data         0 Nov 19  2022 .ocdata
drwxr-xr-x 7 www-data www-data      4096 Sep 18 16:10 admin
drwxr-xr-x 9 www-data www-data      4096 Sep 23 16:04 appdata_ock2gwc8lm4h
drwxr-xr-x 2 www-data www-data      4096 Nov 19  2022 files_external
-rw-r--r-- 1 www-data www-data         0 Nov 19  2022 index.html
-rw-r----- 1 www-data www-data   8973477 Oct  1 11:22 nextcloud.log
-rw-r----- 1 www-data www-data 104869848 Sep 26 23:11 nextcloud.log.1
drwxr-xr-x 4 www-data www-data      4096 Nov 19  2022 updater-ock2gwc8lm4h
-rw-r--r-- 1 www-data www-data     15470 Nov 19  2022 updater.log
root@DietPi:~# 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
root@DietPi:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        30G  1.5G   27G   6% /
devtmpfs        1.9G     0  1.9G   0% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           769M  8.6M  761M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           1.9G  4.0K  1.9G   1% /tmp
tmpfs            50M  4.0K   50M   1% /var/log
/dev/mmcblk0p1  127M   32M   95M  26% /boot
/dev/sda1       916G  165G  706G  19% /mnt/cloud
root@DietPi:~# dmesg -l 0,1,2,3
[    0.597732] bcm2708_fb soc:fb: Unable to determine number of FBs. Disabling driver.

what is the exact error message if you try to create a new file/folder?

Folder cannot be created

ok let’s check one more thing.

ls -la /mnt/dietpi_userdata/nextcloud_data/admin/files/
root@DietPi:~# ls -la /mnt/dietpi_userdata/nextcloud_data/admin/files/
total 72
drwxr-xr-x 5 www-data www-data  4096 Oct  1 12:48 .
drwxr-xr-x 7 www-data www-data  4096 Sep 18 16:10 ..
drwxr-xr-x 2 www-data www-data  4096 Sep 19 23:48 InstantUpload
-rw-r--r-- 1 www-data www-data 50598 Nov  2  2022 Nextcloud.png
drwxr-xr-x 4 www-data www-data  4096 Oct  1 10:32 SSD
drwxr-xr-x 2 www-data www-data  4096 Oct  1 12:48 ahoj
-rw-r--r-- 1 www-data www-data     0 Oct  1 10:30 dietpi.test.file

interesting, the test file has been created, even if there was an error :thinking:

can you try to rescan from file system level

ncc files:scan --all
Starting scan for user 1 out of 1 (admin)
Exception during scan: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused
#0 /var/www/nextcloud/3rdparty/doctrine/dbal/src/Connection.php(1519): OC\DB\Connection->connect()
#1 /var/www/nextcloud/3rdparty/doctrine/dbal/src/Connection.php(1041): Doctrine\DBAL\Connection->getWrappedConnection()
#2 /var/www/nextcloud/lib/private/DB/Connection.php(261): Doctrine\DBAL\Connection->executeQuery()
#3 /var/www/nextcloud/3rdparty/doctrine/dbal/src/Query/QueryBuilder.php(345): OC\DB\Connection->executeQuery()
#4 /var/www/nextcloud/lib/private/DB/QueryBuilder/QueryBuilder.php(281): Doctrine\DBAL\Query\QueryBuilder->execute()
#5 /var/www/nextcloud/lib/private/Files/Cache/Cache.php(493): OC\DB\QueryBuilder\QueryBuilder->execute()
#6 /var/www/nextcloud/lib/private/Files/Cache/Scanner.php(389): OC\Files\Cache\Cache->getId()
#7 /var/www/nextcloud/lib/private/Files/Cache/Scanner.php(394): OC\Files\Cache\Scanner->scanChildren()
#8 /var/www/nextcloud/lib/private/Files/Cache/Scanner.php(342): OC\Files\Cache\Scanner->scanChildren()
#9 /var/www/nextcloud/lib/private/Files/Utils/Scanner.php(256): OC\Files\Cache\Scanner->scan()
#10 /var/www/nextcloud/apps/files/lib/Command/Scan.php(161): OC\Files\Utils\Scanner->scan()
#11 /var/www/nextcloud/apps/files/lib/Command/Scan.php(217): OCA\Files\Command\Scan->scanFiles()
#12 /var/www/nextcloud/3rdparty/symfony/console/Command/Command.php(255): OCA\Files\Command\Scan->execute()
#13 /var/www/nextcloud/core/Command/Base.php(177): Symfony\Component\Console\Command\Command->run()
#14 /var/www/nextcloud/3rdparty/symfony/console/Application.php(1009): OC\Core\Command\Base->run()
#15 /var/www/nextcloud/3rdparty/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand()
#16 /var/www/nextcloud/3rdparty/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun()
#17 /var/www/nextcloud/lib/private/Console/Application.php(213): Symfony\Component\Console\Application->run()
#18 /var/www/nextcloud/console.php(100): OC\Console\Application->run()
#19 /var/www/nextcloud/occ(11): require_once('/var/www/nextcl...')
#20 {main}
+---------+-------+--------------+
| Folders | Files | Elapsed time |
+---------+-------+--------------+
| 2       | 0     | 00:00:00     |
+---------+-------+--------------+

ok something seems to be wrong with your MariaDB hosting NC database.

Can you share current database log again

journalctl -u mariadb
Oct 02 11:59:03 DietPi mariadbd[216148]: 231002 11:59:03 [ERROR] mysqld got signal 11 ;
Oct 02 11:59:03 DietPi mariadbd[216148]: This could be because you hit a bug. It is also possible that this binary
Oct 02 11:59:03 DietPi mariadbd[216148]: or one of the libraries it was linked against is corrupt, improperly built,
Oct 02 11:59:03 DietPi mariadbd[216148]: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 02 11:59:03 DietPi mariadbd[216148]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Oct 02 11:59:03 DietPi mariadbd[216148]: We will try our best to scrape up some info that will hopefully help
Oct 02 11:59:03 DietPi mariadbd[216148]: diagnose the problem, but since we have already crashed,
Oct 02 11:59:03 DietPi mariadbd[216148]: something is definitely wrong and this may fail.
Oct 02 11:59:03 DietPi mariadbd[216148]: Server version: 10.5.19-MariaDB-0+deb11u2 source revision: f8a85af8ca1c937b8d4f847477bd282f80251cde
Oct 02 11:59:03 DietPi mariadbd[216148]: key_buffer_size=134217728
Oct 02 11:59:03 DietPi mariadbd[216148]: read_buffer_size=131072
Oct 02 11:59:03 DietPi mariadbd[216148]: max_used_connections=3
Oct 02 11:59:03 DietPi mariadbd[216148]: max_threads=153
Oct 02 11:59:03 DietPi mariadbd[216148]: thread_count=3
Oct 02 11:59:03 DietPi mariadbd[216148]: It is possible that mysqld could use up to
Oct 02 11:59:03 DietPi mariadbd[216148]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467887 K  bytes of memory
Oct 02 11:59:03 DietPi mariadbd[216148]: Hope that's ok; if not, decrease some variables in the equation.
Oct 02 11:59:03 DietPi mariadbd[216148]: Thread pointer: 0x7f28000c68
Oct 02 11:59:03 DietPi mariadbd[216148]: Attempting backtrace. You can use the following information to find out
Oct 02 11:59:03 DietPi mariadbd[216148]: where mysqld died. If you see no messages after this, something went
Oct 02 11:59:03 DietPi mariadbd[216148]: terribly wrong...
Oct 02 11:59:03 DietPi mariadbd[216148]: stack_bottom = 0x7f981b2868 thread_stack 0x49000
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(my_print_stacktrace)[0x555a13a590]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(handle_fatal_signal)[0x5559c7d304]
Oct 02 11:59:03 DietPi mariadbd[218883]: addr2line: 'linux-vdso.so.1': No such file
Oct 02 11:59:03 DietPi mariadbd[216148]: linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0x7f9cc007a8]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5559f890c4]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(std::unique_lock<std::mutex>::unlock())[0x555a03b3d0]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5559fb9910]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5559fbd124]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5559fbe114]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5559fbe78c]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(std::unique_lock<std::mutex>::unlock())[0x5559fcb974]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x5559f2a900]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(handler::ha_write_row(unsigned char const*))[0x5559c8977c]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(write_record(THD*, TABLE*, st_copy_info*, select_result*))[0x5559a8128c]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(mysql_insert(THD*, TABLE_LIST*, List<Item>&, List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates, bool, select_result*))[0x5559a87bfc]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(mysql_execute_command(THD*))[0x5559ab4ba8]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x5559ab81e4]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x5559ab9b48]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(do_command(THD*))[0x5559abb7ec]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(do_handle_one_connection(CONNECT*, bool))[0x5559b8ff38]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(handle_one_connection)[0x5559b90194]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*) [0x5559e8e958]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(start_thread)[0x7f9c633648]
Oct 02 11:59:03 DietPi mariadbd[216148]: ??:0(clone)[0x7f9c2f2c1c]
Oct 02 11:59:03 DietPi mariadbd[216148]: Trying to get some variables.
Oct 02 11:59:03 DietPi mariadbd[216148]: Some pointers may be invalid and cause the dump to abort.
Oct 02 11:59:03 DietPi mariadbd[216148]: Query (0x7f28010520): INSERT INTO `oc_filecache` (`mimepart`, `mimetype`, `mtime`, `size`, `etag`, `storage_mtime`, `permissions`, `name`, `parent`, `checksum`, `path_hash`, `path`, `storage`) VALUES('1', '2', '1694962659', '-1', '651aa27767f16', '1694962659', '31', '09', '46285', '', 'ef8a5105010169997928ed323e64d40e', 'files/SSD/Samsung/Socialni foto/2023/09', '1')
Oct 02 11:59:03 DietPi mariadbd[216148]: Connection ID (thread ID): 165
Oct 02 11:59:03 DietPi mariadbd[216148]: Status: NOT_KILLED
Oct 02 11:59:03 DietPi mariadbd[216148]: 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
Oct 02 11:59:03 DietPi mariadbd[216148]: The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
Oct 02 11:59:03 DietPi mariadbd[216148]: information that should help you find out what is causing the crash.
Oct 02 11:59:03 DietPi mariadbd[216148]: Writing a core file...
Oct 02 11:59:03 DietPi mariadbd[216148]: Working directory at /mnt/cloud/dietpi_userdata/mysql
Oct 02 11:59:03 DietPi mariadbd[216148]: Resource Limits:
Oct 02 11:59:03 DietPi mariadbd[216148]: Limit                     Soft Limit
        Hard Limit           Units
Oct 02 11:59:03 DietPi mariadbd[216148]: Max cpu time              unlimited
        unlimited            seconds
Oct 02 11:59:03 DietPi mariadbd[216148]: Max file size             unlimited
        unlimited            bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max data size             unlimited
        unlimited            bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max stack size            8388608
        unlimited            bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max core file size        0
        unlimited            bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max resident set          unlimited
        unlimited            bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max processes             15104
        15104                processes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max open files            32768
        32768                files
Oct 02 11:59:03 DietPi mariadbd[216148]: Max locked memory         8388608
        8388608              bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max address space         unlimited
        unlimited            bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max file locks            unlimited
        unlimited            locks
Oct 02 11:59:03 DietPi mariadbd[216148]: Max pending signals       15104
        15104                signals
Oct 02 11:59:03 DietPi mariadbd[216148]: Max msgqueue size         819200
        819200               bytes
Oct 02 11:59:03 DietPi mariadbd[216148]: Max nice priority         0
        0
Oct 02 11:59:03 DietPi mariadbd[216148]: Max realtime priority     0
        0
Oct 02 11:59:03 DietPi mariadbd[216148]: Max realtime timeout      unlimited
        unlimited            us
Oct 02 11:59:03 DietPi mariadbd[216148]: Core pattern: core
Oct 02 11:59:03 DietPi mariadbd[216148]: Kernel version: Linux version 6.1.21-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0,
GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023
Oct 02 11:59:03 DietPi systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
Oct 02 11:59:03 DietPi systemd[1]: mariadb.service: Failed with result 'signal'.
Oct 02 11:59:03 DietPi systemd[1]: mariadb.service: Consumed 5.615s CPU time.
Oct 02 11:59:08 DietPi systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 83.
Oct 02 11:59:08 DietPi systemd[1]: Stopped MariaDB 10.5.19 database server.
Oct 02 11:59:08 DietPi systemd[1]: mariadb.service: Consumed 5.615s CPU time.
Oct 02 11:59:08 DietPi systemd[1]: Starting MariaDB 10.5.19 database server...
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] Starting MariaDB 10.5.19-MariaDB-0+deb11u2 source revision f8a85af8ca1c937b8d4f847477bd282f80251cde as process 218955
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Uses event mutexes
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Number of pools: 1
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Using ARMv8 crc32 instructions
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Using Linux native AIO
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Completed initialization of buffer pool
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=5073225747,5073225747
Oct 02 11:59:09 DietPi mariadbd[218955]: 2023-10-02 11:59:09 0 [Note] InnoDB: Starting final batch to recover 91 pages from redo log.
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: 128 rollback segments are active.
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: 10.5.19 started; log sequence number 5081130217; transaction id 24445417
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] Plugin 'FEEDBACK' is disabled.
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: Loading buffer pool(s) from /mnt/cloud/dietpi_userdata/mysql/ib_buffer_pool
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] Server socket created on IP: '127.0.0.1'.
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] Reading of all Master_info entries succeeded
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] Added new Master_info '' to hash table
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] /usr/sbin/mariadbd: ready for connections.
Oct 02 11:59:10 DietPi mariadbd[218955]: Version: '10.5.19-MariaDB-0+deb11u2'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Debian 11
Oct 02 11:59:10 DietPi systemd[1]: Started MariaDB 10.5.19 database server.
Oct 02 11:59:10 DietPi /etc/mysql/debian-start[218979]: Upgrading MySQL tables if necessary.
Oct 02 11:59:10 DietPi mariadbd[218955]: 2023-10-02 11:59:10 0 [Note] InnoDB: Buffer pool(s) load completed at 231002 11:59:10
Oct 02 11:59:10 DietPi /etc/mysql/debian-start[218982]: Looking for 'mariadb' as: /usr/bin/mariadb
Oct 02 11:59:10 DietPi /etc/mysql/debian-start[218982]: Looking for 'mariadb-check' as: /usr/bin/mariadb-check
Oct 02 11:59:10 DietPi /etc/mysql/debian-start[218982]: This installation of MariaDB is already upgraded to 10.5.15-MariaDB.
Oct 02 11:59:10 DietPi /etc/mysql/debian-start[218982]: There is no need to run mysql_upgrade again for 10.5.19-MariaDB.
Oct 02 11:59:10 DietPi /etc/mysql/debian-start[218982]: You can use --force if you still want to run mysql_upgrade
Oct 02 11:59:10 DietPi /etc/mysql/debian-start[218994]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables

hmm this looks like your MariaDB software is broken / corrupted. Do you have a backup created before running the update process?

Unfortunately i don’t but that’s exactly how it stopped working and i thought a dietpi update would fix it

You have a problem with your local database environment and no update will fix this problem.

Let’s check following

mysql -e "SHOW DATABASES;"
mysql -e "SELECT db, host, user FROM mysql.db;"
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| nextcloud          |
| performance_schema |
+--------------------+
root@DietPi:~# mysql -e "SELECT db, host, user FROM mysql.db;"
+-----------+------+----------+
| db        | host | user     |
+-----------+------+----------+
| nextcloud | %    | oc_admin |
+-----------+------+----------+

ok let’s try to create a backup of your Nextcloud database

mysqldump nextcloud > "/mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-database-backup.sql"

If all goes well, DB dump should be at /mnt/dietpi_userdata/nextcloud_data/

ls -la /mnt/dietpi_userdata/nextcloud_data/
root@DietPi:~# mysqldump nextcloud > "mysqldump nextcloud > "/mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-database-backup.sql"dietpi-nextcloud-database-backup.sql"
-bash: mysqldump nextcloud > /mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-database-backup.sqldietpi-nextcloud-database-backup.sql: No such file or directory
root@DietPi:~# ls -la /mnt/dietpi_userdata/nextcloud_data/
total 115128
drwxrwx--- 6 www-data www-data      4096 Sep 26 23:15 .
drwxrwxr-x 8 dietpi   dietpi        4096 Nov  2  2022 ..
-rw-r--r-- 1 www-data www-data       542 Nov 19  2022 .htaccess
-rw-r--r-- 1 www-data www-data         0 Nov 19  2022 .ocdata
drwxr-xr-x 7 www-data www-data      4096 Sep 18 16:10 admin
drwxr-xr-x 9 www-data www-data      4096 Sep 23 16:04 appdata_ock2gwc8lm4h
drwxr-xr-x 2 www-data www-data      4096 Nov 19  2022 files_external
-rw-r--r-- 1 www-data www-data         0 Nov 19  2022 index.html
-rw-r----- 1 www-data www-data  12956894 Oct  3 14:40 nextcloud.log
-rw-r----- 1 www-data www-data 104869848 Sep 26 23:11 nextcloud.log.1
drwxr-xr-x 4 www-data www-data      4096 Nov 19  2022 updater-ock2gwc8lm4h
-rw-r--r-- 1 www-data www-data     15470 Nov 19  2022 updater.log