[SOLVED] RSYNC fails to backup

alex4buba · 08-19-2025, 05:27 AM

A few days ago, after a software update, my daily automated rsync scskhedule fails to work. I used an external hard disk for the laptop backup, then I tried another disk, but it does the same thing again...

Below is a small code snipest of the errors, I tried, chown and chmod following google search, but nothing works, any help please

Code:

rsync: [generator] chgrp "/media/alexe/Elements/tue/." failed: Operation not permitted (1)
rsync: [generator] symlink "/media/alexe/Elements/tue/org.kde.ktimer.desktop" -> "unsupported reparse tag 0xa000000c" failed: Permission denied (13)
rsync: [generator] recv_generator: mkdir "/media/alexe/Elements/tue/125-Ubuntu" failed: Permission denied (13)
*** Skipping any contents from this failed directory ***
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.20221213_191838.jpg.rqtP3U" failed: Permission denied (13)
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.20240519_073206.jpg.QVj3CA" failed: Permission denied (13)
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.21_006920_fmlyltr_4.pdf.d51JDb" failed: Permission denied (13)
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.5.jpg.e6rDw1" failed: Permission denied (13)
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.Alex_Drivers_Back.jpg.VHyzp2" failed: Permission denied (13)
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.Alex_Drivers_Front.jpg.3R3nJM" failed: Permission denied (13)
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.Alex_Lauris_Gra.jpg.SrGzMP" failed: Permission denied (13)
rsync: [receiver] mkstemp "/media/alexe/Elements/tue/.Alex_Passport.jpg.RRnatu" failed: Permission denied (13)

pan64 · 08-19-2025, 05:55 AM

have you checked those permissions?

alex4buba · 08-19-2025, 06:21 AM

Quote:

Originally Posted by pan64

have you checked those permissions?

What should I check? unclear.
I am operating it as Administrator and Permissions for owner is Read or Modify

Please explain
Many thanks

pan64 · 08-19-2025, 07:40 AM

why did you get permission denied? That is what you need to check.
Which linux user tried to write those files/dirs....
How are permissions set on these files/directories ?

michaelk · 08-19-2025, 08:08 AM

Is the new drive formated with a linux filesystem?
As posted does it have the proper permissions?

Ia the old drive full or has somehow failed? Something has changed.
Can you manually create files etc on the drive via sudo or whatever user runs rsync?

alex4buba · 08-19-2025, 07:56 PM

Quote:

Originally Posted by michaelk

Is the new drive formated with a linux filesystem?
As posted does it have the proper permissions?

Ia the old drive full or has somehow failed? Something has changed.
Can you manually create files etc on the drive via sudo or whatever user runs rsync?

Following your comments,

I did the following in command line:
sudo chown -R alexe:alexe /media/alexe/Elements
[sudo] password for alexe:

And that fixed the problem

The old disk was not full, I just decided to leave it at home and travel with a new disk.
The file format is set to ext4

The backup is running now as I am writing this.

Many tahnks for your time

alex4buba · 08-20-2025, 04:49 AM

After executing the backup (manually) I restarted my laptop, but am unable to fix the following error:

Code:

An error occurred while accessing 'Elements', the system responded: The requested operation has failed: Error mounting system-managed device /dev/sda1: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error

There is only one user account, me. I am marked as Administrator.
The only way I can Mount is by using the KDE Partition Manager, the the disk dos't mount automatically when turning the laptop on.

What should I do?

Thanks for any help

chrism01 · 08-20-2025, 08:48 PM

Code:

 /dev/sda1: wrong fs type, bad option, bad superblock on /dev/sda1

You need to check that.

After you've mounted it via partition mgr, run the 'mount' cmd without any params and look at the output https://phoenixnap.com/kb/linux-mount-command .

Check where it's mounted and the type; post the output here.
Also, post the contents of /etc/fstab for comparison .

Most likely you have wrong type in fstab. If it was corrupted, you wouldn't be able to mount it at all.

alex4buba · 08-21-2025, 05:30 AM

Quote:

Originally Posted by chrism01

Code:

 /dev/sda1: wrong fs type, bad option, bad superblock on /dev/sda1

You need to check that.

After you've mounted it via partition mgr, run the 'mount' cmd without any params and look at the output https://phoenixnap.com/kb/linux-mount-command .

Check where it's mounted and the type; post the output here.
Also, post the contents of /etc/fstab for comparison .

Most likely you have wrong type in fstab. If it was corrupted, you wouldn't be able to mount it at all.

Executing mount command produces the following:

Code:

alexe@alexe:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=16203292k,nr_inodes=4050823,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3249292k,mode=755,inode64)
/dev/nvme0n1p2 on / type ext4 (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=7080)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/var/lib/snapd/snaps/bare_5.snap on /snap/bare/5 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core18_2923.snap on /snap/core18/2923 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core18_2934.snap on /snap/core18/2934 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core20_2582.snap on /snap/core20/2582 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core20_2599.snap on /snap/core20/2599 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core22_2045.snap on /snap/core22/2045 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/core22_2010.snap on /snap/core22/2010 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/gtk-common-themes_1535.snap on /snap/gtk-common-themes/1535 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/noson_644.snap on /snap/noson/644 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/mkcron_2.snap on /snap/mkcron/2 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/qt513_24.snap on /snap/qt513/24 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/noson_654.snap on /snap/noson/654 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/snapd_24792.snap on /snap/snapd/24792 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
/var/lib/snapd/snaps/snapd_24718.snap on /snap/snapd/24718 type squashfs (ro,nodev,relatime,errors=continue,threads=single,x-gdu.hide,x-gvfs-hide)
tmpfs on /tmp type tmpfs (rw,noatime,inode64)
/dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3249288k,nr_inodes=812322,mode=700,uid=1000,gid=1000,inode64)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sda1 on /media/alexe/Elements type ext4 (rw,relatime)

The fstab file shows this:

Code:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=9D7C-022A                              /boot/efi               vfat    defaults            0 2 
UUID=7c484880-4377-4a40-a6c6-7fc5176a155e   /                       ext4    defaults            0 1 
/swapfile                                   swap                    swap    defaults            0 0 
tmpfs                                       /tmp                    tmpfs   noatime,mode=1777   0 0 
/dev/sda1                                   /media/alexe/Elements   exfat   nofail              0 0

Executing the -t command, shows this:

Code:

#
alexe@alexe:~$ mount -t ext4
/dev/nvme0n1p2 on / type ext4 (rw,relatime)
/dev/sda1 on /media/alexe/Elements type ext4 (rw,relatime)

Nothing of the above is clear what it means, hope to you it does...

Many thanks

michaelk · 08-21-2025, 05:59 AM

Your fstab has exfat but the filesystem is ext4.

alex4buba · 08-21-2025, 06:51 AM

Quote:

Originally Posted by michaelk

Your fstab has exfat but the filesystem is ext4.

Many thanks, that fixed the problem

Cheers