Please cancel the backup via <ctrl>+<c>, if not already done or it ran into full disk issue itself.
You should have received a prompt/warning, that you space seems to be insufficient, which allows you to exit or ignore.
However you should always have a careful look, if this warning appears. According to your screen it mentions a required disk space of 17968821 MiB = 1755 GiB = 1,71 TiB, so more than even your data HDD has.
Of course this does not make much sense on the system. I ran once into a similar issue, having a several Exabyte backup. It was due to SDcard corruption: There was one single file, having this enormous size and attempting to remove or handle it, lead to an I/O error.
Please check:
- /var/tmp/dietpi/logs/dietpi-backup.log to see on which file it hang. Hope it is actually logged.
- dmesg for emmc I/O errors.
- > /forcefsck to force a system partition file system check on next reboot.
The issue most likely is related to the SDcard. Those are known to break very fast and being vulnerable to corruption, especially used as system drive, due to the many small disk changes from the OS and installed packages.
Could you find the exact file, where the backup hang, by checking it's log?
Ah sorry, I was mistake about the log location, it's /var/log/dietpi-backup.log. Since this is in RAM and cleared every hour. So I guess you need to rerun the backup for a minute or such, cancel it again and then check the log: tail /var/log/dietpi-backup.log
Copy & paste works, but take care that file permissions are preserved, otherwise when restoring the backup without permissions, the system will not work properly. The target file systems needs to support them and e.g. use cp -a /source/dir /target/dir to have permissions preserved on copy.
Generally about file system corruption:
- Sometimes fsck needs to be done more than once to resolve all issues and also on reboot (non-interactively) not all cases will be cleaned, especially if this means that broken files are removed/lost.
- You will have best results, if you plug the SDcard into another external Linux system and run fsck interactively there.