Merci !
I will try this and give feedback.
root@DietPi:\~# systemctl status mariadb
â mariadb.service - MariaDB 10.11.14 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
ââdietpi.conf
Active: active (running) since Thu 2026-01-29 19:21:45 CET; 1 day 19h ago
Docs: man:mariadbd(8)
Process: 596 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 600 ExecStartPre=/bin/sh -c systemctl unset-environment \_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 602 ExecStartPre=/bin/sh -c \[ ! -e /usr/bin/galera_recovery \] && VAR= || VAR=`/usr/bin/galera_recovery`; \[ $? -eq 0 \] && systemctl set-environment \_WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 689 ExecStartPost=/bin/sh -c systemctl unset-environment \_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 691 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
Main PID: 632 (mariadbd)
Status: âTaking your SQL requests nowâŚâ
Tasks: 9 (limit: 61786)
CPU: 29.723s
CGroup: /system.slice/mariadb.service
ââ632 /usr/sbin/mariadbd
Jan 31 14:00:01 DietPi mariadbd\[632\]: 2026-01-31 14:00:01 543 \[Warning\] Aborted connection 543 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:05:01 DietPi mariadbd\[632\]: 2026-01-31 14:05:01 544 \[Warning\] Aborted connection 544 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:10:01 DietPi mariadbd\[632\]: 2026-01-31 14:10:01 545 \[Warning\] Aborted connection 545 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:15:02 DietPi mariadbd\[632\]: 2026-01-31 14:15:02 546 \[Warning\] Aborted connection 546 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:20:01 DietPi mariadbd\[632\]: 2026-01-31 14:20:01 547 \[Warning\] Aborted connection 547 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:25:01 DietPi mariadbd\[632\]: 2026-01-31 14:25:01 548 \[Warning\] Aborted connection 548 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:30:02 DietPi mariadbd\[632\]: 2026-01-31 14:30:02 549 \[Warning\] Aborted connection 549 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:35:01 DietPi mariadbd\[632\]: 2026-01-31 14:35:01 550 \[Warning\] Aborted connection 550 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:40:01 DietPi mariadbd\[632\]: 2026-01-31 14:40:01 551 \[Warning\] Aborted connection 551 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
Jan 31 14:45:02 DietPi mariadbd\[632\]: 2026-01-31 14:45:02 552 \[Warning\] Aborted connection 552 to db: ânextcloudâ user: âoc_admin_dpâ host: âlocalhostâ (Got an error reading communication packets)
root@DietPi:\~# ls -l /mnt/
total 13
drwxr-xr-x 4 root root 1024 Mar 1 2025 IronWolf-1
lrwxrwxrwx 1 root root 31 Mar 1 2025 dietpi_userdata â /mnt/IronWolf-1/dietpi_userdata
drwxrwxr-x 2 dietpi dietpi 4096 Dec 23 2024 ftp_client
drwxrwxr-x 2 dietpi dietpi 4096 Dec 23 2024 nfs_client
drwxrwxr-x 2 dietpi dietpi 4096 Dec 23 2024 samba
root@DietPi:\~# ls -l /mnt/dietpi_userdata/
total 6
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Music
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Pictures
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Video
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 downloads
drwxr-xr-x 6 mysql mysql 1024 Jan 29 19:21 mysql
drwxrwxâ 11 www-data www-data 1024 Mar 3 2025 nextcloud_data
root@DietPi:\~# sudo mysqldump nextcloud > /mnt/dietpi_userdata/nextcloud.sql
root@DietPi:\~# ls -l /mnt/dietpi_userdata/
total 16523
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Music
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Pictures
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Video
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 downloads
drwxr-xr-x 6 mysql mysql 1024 Jan 29 19:21 mysql
-rw-râr-- 1 root root 16913307 Jan 31 15:01 nextcloud.sql
drwxrwxâ 11 www-data www-data 1024 Mar 3 2025 nextcloud_data
root@DietPi:\~# ls -l /mnt/IronWolf-1/
total 13
drwxrwxr-x 8 dietpi dietpi 1024 Jan 31 15:01 dietpi_userdata
drwx------ 2 root root 12288 Mar 1 2025 lost+found
root@DietPi:\~# ls -l /mnt/IronWolf-1/dietpi_userdata/
total 16523
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Music
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Pictures
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 Video
drwxrwxr-x 2 dietpi dietpi 1024 Jan 17 2025 downloads
drwxr-xr-x 6 mysql mysql 1024 Jan 29 19:21 mysql
-rw-râr-- 1 root root 16913307 Jan 31 15:01 nextcloud.sql
drwxrwxâ 11 www-data www-data 1024 Mar 3 2025 nextcloud_data
Okay looks good. Now try the following:
- Flash a new DietPi image onto a new USB stick or SD card or whichever preferred boot media you have at hand. Boot it, but do not install anything yet.
- Change
dietpi_userdatato the external drive/same directory as before, withdietpi-softwareordietpi-drive_manager. - Copy
/var/www/nextcloudfrom the old drive to/mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-installation-backup.cp -a /mnt/old_usb/var/www/nextcloud /mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-installation-backup - Move the
nextcloud.sqlto/mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-database-backup.sqlmv /mnt/dietpi_userdata/nextcloud.sql /mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-database-backup.sql - Move the old raw database dir out of the way, since we want to import if freshly from the SQL dump:
mv /mnt/dietpi_userdata/mysql /mnt/dietpi_userdata/mysql_bak - Install Nextcloud:
dietpi-software install 114
That is the cleanest way of migrating an instance. dietpi-software moves the backups in place, imports the database, and takes care of all permissions etc.
Just a question.
/var/www/nextcloud seems to be on the usb-stick (sdb) which is probably corrupted.
Isnât that a risk or a problem if I copy them?
Nextcloud has an internal integrity check. So if any of these files is corrupt, the admin panel would throw a warning. In case, an update would solve it, or manually downloading the archive of the matching version. But no need to do anything unless Nextcloud tells you that files fail the integrity check.
I flashed a new USB-stick.
Booted the Raspberrypi with it.
/dev/sdb new USB-stick
/dev/sdb1 /boot/firmware
I connected the old-USB-stick.
/dev/sdc old-USB-stick
With DietPi-Drive_Manager I could mount the harddisk /dev/sda1 /mnt/IronWolf-1, but donât know how to âChange dietpi_userdata to the external drive/same directory as beforeâ. For the moment it is :
User data location: RootFS (/mnt/dietpi_userdata)
And it seems it canât achieve dietpi.com
I got a temporary shell
root@DietPi:/tmp/DietPi-Software#
In the drive manager, select the drive and there âUser dataâ. /mnt/dietpi_userdata becomes a symlink to /mnt/IronWolf-1/dietpi_userdata, so /mnt/dietpi_userdata/nextcloud_data etc should then be there.
Ok, I was not sure what was exactly the meaning of
âYour user data will be moved from /mnt/dietpi_userdata to /mnt/IronWolf-1/dietpi_userdataâ.
So it is just a symlink, not a move and erase old data.
Yeah right, just a way to keep /mnt/dietpi_userdata paths intact no matter where things are actually stored.
Should I try âCheck & Repairâ on the old-USB-stick before
cp -a /mnt/old_usb/var/www/nextcloud /mnt/dietpi_userdata/nextcloud_data/dietpi-nextcloud-installation-backup
If it copies well, not needed. If it fails, you can try it. But note that fsck itself in certain situations can also cause corruption where none was before. So if data needs to be rescued, it is better to try copying things first, before attempting a repair as last resort.
ok I went through all your points 1 â6
The last one
dietpi-software install 114 didnât work
A pop-up DietPi Software
WARNING: Current execution of DietPi-Software detected
Please check if one of the following applies:
- This script already runs on another terminal/SSH session
-Currently a cron of systemd background job executes the script.
You started this script from within another DietPi program, causing a loop.
Please assure that the current execution has finished, before retrying, otherwise cancel this instance.
The following info might help:
1400 root tty1 /bin/bash /boot/dietpi/dietpi-login
1537 root tty1 /bin/bash /boot/dietpi/dietpi-update 1
2134 root tty1 /bin/bash /boot/dietpi/dietpi-software
3522 toot tty1 /bin/bash /boot/dietpi/dietpi-software install 114
3530 root tty1 /bin/bash /boot/dietpi/dietpi-software install 114
3532 root tty1 grep -i dietpi
1538 root tty1 tee /var/tmp/dietpi/logs/dietpi-firstrun-setup.log
Retry (or) Cancel
Now I remember you said youâre on a subshell from dietpi-software. Exit or finish that one first. In case, what was the initial error there?
[FAILED] DietPi-Software | Cancelled DietPi-Software due to concurrent execution
root@DietPi:/tmp/DietPi-Software#
It complained that it could not achieve dietpi dot com
Error checking DNS resolver.
curl: (6) Could not resolve host: dietpi dot com
[FAILED] DietPi-Config | Checking URL: https://dietpi dot com/
- Command: curl -ILfvm 10 https://dietpi dot com/
Changed data in /etc/resolv.conf
Changed npt server
dietpi-software install 114
Nextcloud installation backup found
Nextcloud database backup found
nextcloud installed !
Thank you for your helpful step-by-step and your patience!!!
Ah great you found the solution. If you use DHCP, maybe the DHCP server promoted/promotes a wrong DNS resolver, and it could revert your change on next lease. But in case of static IP, not a problem, of course.
Great the Nextcloud restore/migration worked as expected.