Permissions errors when installing or upgrading

I just re-installed my system, and when I went to update, I got a bunch of these errors:

rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/crypto": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/events": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/e820": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/fpu": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/numachip": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/shared": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/trace": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/uv": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/vdso": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/asm/xen": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/generated": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/generated/asm": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/generated/uapi": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/generated/uapi/asm": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/uapi": Invalid argument (22)
rsync: [generator] failed to set permissions on "/usr/lib/modules/6.5.9-zen2-1-zen/build/arch/x86/include/uapi/asm": Invalid argument (22)

This is truncated. There are thousands of lines of this.

I decided to install linux-lts as a backup, and I got this:

rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.alias.MfOt9Y": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.alias.bin.XG75Ut": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.builtin.alias.bin.nOxSDs": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.builtin.bin.DAz6IV": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.dep.VTuobs": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.dep.bin.jSsNkW": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.devname.uKzPME": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.softdep.TvyoIr": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.symbols.3lKZAs": Invalid argument (22)
rsync: [receiver] failed to set permissions on "/usr/lib/modules/backup/6.5.9-zen2-1-zen/.modules.symbols.bin.15cFuu": Invalid argument (22)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1336) [sender=3.2.7]

This isn’t truncated. Far fewer lines, but similar.

But that’s not all! When I went to install yakuake, I got this:

warning: warning given when extracting /usr/share/yakuake/skins/default/tabs/left_corner.svg (Can't set permissions to 0777)
warning: warning given when extracting /usr/share/yakuake/skins/default/tabs/right_corner.svg (Can't set permissions to 0777)
warning: warning given when extracting /usr/share/yakuake/skins/default/tabs/selected_left.svg (Can't set permissions to 0777)
warning: warning given when extracting /usr/share/yakuake/skins/default/tabs/selected_right.svg (Can't set permissions to 0777)
warning: warning given when extracting /usr/share/yakuake/skins/default/tabs/unselected_left.svg (Can't set permissions to 0777)
warning: warning given when extracting /usr/share/yakuake/skins/default/tabs/unselected_right.svg (Can't set permissions to 0777)

I installed both linux-lts and yakuake using octopi.

Here’s my garuda-inxi:

System:
Kernel: 6.7.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: hpet avail: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=ed52d193-ea71-4621-8b96-8e5f826c8896 rw rootflags=subvol=@
quiet resume=UUID=29f95931-659e-4745-a241-50d84a80ab71 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 info: frameworks
v: 5.115.0 wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B550-A GAMING v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 2604 date: 02/25/2022
CPU:
Info: model: AMD Ryzen 5 5600G with Radeon Graphics bits: 64 type: MT MCP
arch: Zen 3 gen: 4 level: v3 note: check built: 2021-22
process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000C
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 2381 high: 3237 min/max: 400/4464 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 3237 2: 3019 3: 2994
4: 2994 5: 3025 6: 2967 7: 3142 8: 3010 9: 2994 10: 400 11: 400 12: 400
bogomips: 93431
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1
bus-ID: 0a:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 37.0 C
Display: wayland server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 0
Monitor-1: HDMI-A-1 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.5-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
renoir LLVM 16.0.6 DRM 3.57 6.7.4-zen1-1-zen) device-ID: 1002:1638
memory: 500 MiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.276 layers: 3 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RENOIR) driver: mesa radv v: 23.3.5-arch1.1
device-ID: 1002:1638 surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 16.0.6 256 bits) driver: mesa llvmpipe
v: 23.3.5-arch1.1 (LLVM 16.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 0a:00.1 chip-ID: 1002:1637
class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 0a:00.6 chip-ID: 1022:15e3
class-ID: 0403
API: ALSA v: k6.7.4-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp6s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 08:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp8s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7.2:7 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 20.62 TiB used: 9.71 GiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SKC3000D2048G
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.6 temp: 24.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST3500630NS
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
tech: N/A serial: <filter> fw-rev: 3CNR scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST20000NM007D-3DJ103
size: 18.19 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: SN01 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Kingston model: DataTraveler 3.0
size: 115.23 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 1.85 TiB size: 1.85 TiB (100.00%) used: 9.71 GiB (0.5%)
fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 1.85 TiB size: 1.85 TiB (100.00%)
used: 9.71 GiB (0.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 1.85 TiB size: 1.85 TiB (100.00%)
used: 9.71 GiB (0.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 1.85 TiB size: 1.85 TiB (100.00%)
used: 9.71 GiB (0.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 16.41 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
ID-2: swap-2 type: zram size: 14.91 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 45.4 C mobo: N/A gpu: amdgpu temp: 35.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 14.91 GiB used: 3.65 GiB (24.4%)
Processes: 343 Power: uptime: 2m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 5.96 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1216 libs: 359 tools: octopi,paru Compilers:
gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.0 running-in: konsole
inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2024-02-12
Last full system update: 2024-02-12
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

It looks like something bad happened.
Rsync is called by kernel-modules-hook, that’s why you get errors in the first two blocks.
Since it’s a reinstallation, quite frankly I suggest you just do that again…

3 Likes

Weird, I’d look into this:

SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?

A very superficial search indicates those errors are common with NTFS partitions or network mounted disks, which I surmise is not the case here though.


Er… but the “unknown USB” I guess is about the Kingston (edit: I mean the Datatraveler) one, very likely I’m on a wrong path with that.

1 Like

I tried that. I got the same result.

Please, post full ISO name and downlod page.
How do you install, with ventoy.net?
Did you check sha sum?

Please use only terminal for software and kernel install, not octopi.

5 Likes

The filename is garuda-dr460nized-linux-zen-231029.iso, and I downloaded it from Garuda Linux | Download. I did install it with Ventoy. I just checksummed it, and it passed.

Did you?

3 Likes

That’s all really wierd.
Considering

Why not give BIOS update a chance.

Version 3405 16.39 MB 2024/01/08

3 Likes

I tried installing linux-lts and yakuake from the terminal (using pacman), and I didn’t get the errors.

I have to bookmark this topic for the cases when people ask why Octopi should be avoided :wink:
Glad it is solved.

4 Likes

I still have the issue with the errors from the update, though? I used Garuda Assistant to perform a System Update and I got all of those errors at the top of my first post. I got the same thing when I reinstalled and used update from the terminal.

Ah, sorry, I didn’t realize that those errors remained.
So the update fails to finish?
I’m just wondering because the first block was for the old kernel modules (6.5.9) and not the new ones (6.7.4), so maybe if the update completed it could be fixed in some other way.

The update completed. So, I guess everything should be fine, since the new version installed?

I think so.
The confirmation will come at the next kernel update, which will trigger that hook using rsync.