After upgrade an unusual behavior

Hi Garuda friends!

I'm faceing behavior when after update my system literally freaks out.
Yes I'm able to update it without a problem , but after a couple times of doing it I just gave up because I'm affraid do it. Seriouslly.

So let's start from begining maybe.

At pass in one of older post SGS adviced me to use pacman -Syu at first to update system and garuda-update in case when first one failed.

I've fallowed that path until I noticed change in update process:

╰─λ sudo pacman -Syu
Garuda Linux is updated via the "garuda-update" command instead of pacman -Syu. https://wiki.garudalinux.org/e
n/garuda-update
Would you like to run "garuda-update" instead? (i = never ask again/ignore) [y/N/i]

Which option of upgrading should I use currently? And what's the difference between them?
As far as I tested all of them just works fine, at the end system is upgraded. At least I don't feel a difference beside that extra comment from terminal.

So far so good. Let's update & upgrade the system. As mentioned above it will succeed. And system will be working just fine. But after restart it won't be usable any more!
By that I mean :

I will receive a tones of commands like
image

Above error doen't come from my computer. It's only an example found in internet. But what is common that part where /home/$USER/.config/any config file which program I try to use suddenly are not writtable. Noticed for bash, plasma, web browser- everything is not available.

After a some time a screen going to be just freezed. Tried to make a copy of error messages, screens etc. But guess what? Yeap ! Can't save it :slight_smile:

That's why I can only describe a such situation. That happend to me 3 times in last 3 months.
After a such upgrade when it finally crashed one by one app ,the only sollution is reinstalling a system.

By restoring I mean that option:

In big shortcut:

  • I use still timeshift with rsync option, and backup entire partition to another one
  • I know that current supported backup app is snapper, but after spectacular failure with it decided to go back with Timeshift, which personally in my opinion is everything I need
  • In case like described upgrade problem while nothing seams to work , using a bootable pendrive with old Garuda iso version - that one which still has got timeshift, I'm able to REINSTALL system.
  • Yes, I have to reinstall (with formatting) because without it snapshot restoring will definitelly failed!
  • Lastly I'm able to restore specific backup.
  • Finally I'm up and running , untill a new upgrade attempt :frowning:

How to fix that?

Bellow I'm pasting garuda-ixin (but keep in mind it won't be fresh since I'm not able to upgrade my system safely and that's why data is related to restored backup.

╰─λ garuda-inxi
System:
Kernel: 5.18.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
parameters: BOOT_IMAGE=/vmlinuz-linux-zen
root=UUID=87603695-d3be-46e8-98f5-47ff19e39c94 rw [email protected]
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3
Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: P55-US3L serial: <superuser required>
BIOS: Award v: FE date: 03/05/2010
CPU:
Info: model: Intel Core i5 750 bits: 64 type: MCP arch: Nehalem family: 6
model-id: 0x1E (30) stepping: 5 microcode: 0xA
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB
desc: 1x8 MiB
Speed (MHz): avg: 1783 high: 2792 min/max: 1197/2661 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 2792 2: 1276
3: 1264 4: 1800 bogomips: 21317
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Redwood XT [Radeon HD 5670/5690/5730] vendor: Gigabyte
driver: radeon v: kernel alternate: amdgpu pcie: gen: 2 speed: 5 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DVI-I-1,VGA-1 bus-ID: 01:00.0
chip-ID: 1002:68d8 class-ID: 0300
Device-2: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-1.2:3 chip-ID: 046d:0843 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2
compositor: kwin_x11 driver: X: loaded: radeon unloaded: modesetting
alternate: fbdev,vesa gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-0 model: AOC 2757M serial: <filter>
built: 2012 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 720x400
OpenGL:
renderer: AMD REDWOOD (DRM 2.50.0 / 5.18.1-zen1-1-zen LLVM 13.0.1)
v: 3.3 Mesa 22.1.0 compat-v: 3.1 direct render: Yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56
class-ID: 0403
Device-2: AMD Redwood HDMI Audio [Radeon HD 5000 Series] vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 1002:aa60 class-ID: 0403
Device-3: Creative Labs CA0106/CA0111 [SB Live!/Audigy/X-Fi Series]
driver: snd_ca0106 v: kernel bus-ID: 06:04.0 chip-ID: 1102:0007
class-ID: 0401
Device-4: Philips s SAA7131/SAA7133/SAA7135 Video Broadcast Decoder
vendor: Avermedia DVB-T Super 007 driver: saa7134 v: 0, 2, 17
bus-ID: 06:05.0 chip-ID: 1131:7133 class-ID: 0480
Device-5: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 1-1.2:3 chip-ID: 046d:0843 class-ID: 0102 serial: <filter>
Sound Server-1: ALSA v: k5.18.1-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 16.0 running: no
Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
Device-1: Realtek RTL8192EE PCIe Wireless Network Adapter driver: rtl8192ee
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: ee00 bus-ID: 02:00.0
chip-ID: 10ec:818b class-ID: 0280
IF: wlp2s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: ce00 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: docker0 state: down mac: <filter>
Drives:
Local Storage: total: 447.13 GiB used: 278.01 GiB (62.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: GOODRAM model: N/A size: 447.13 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD
serial: <filter> rev: 01.7 scheme: MBR
Partition:
ID-1: / raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
used: 64.3 GiB (32.9%) fs: btrfs dev: /dev/sda3 maj-min: 8:3
ID-2: /boot raw-size: 520 MiB size: 519 MiB (99.80%)
used: 136.5 MiB (26.3%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 11.68 GiB used: 880 MiB (7.4%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A gpu: radeon temp: 58.5 C
Fan Speeds (RPM): N/A
Info:
Processes: 290 Uptime: 10h 43m wakeups: 0 Memory: 11.68 GiB
used: 7 GiB (59.9%) Init: systemd v: 251 tool: systemctl Compilers:
gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 2010 lib: 555 Shell: fish
v: 3.4.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.16
Garuda (2.6.3-2):
System install date:     2022-05-24
Last full system update: 2022-06-06
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       <superuser required>
Snapshots:               Timeshift
Failed units:            bluetooth-autoconnect.service

Best regards

You can use update, which is a shortcut to garuda-update.
Thread here about that: Update Vs Garuda-update - #4 by TNE.

It allows a lot of manual intervention to be skipped, and things to be fixed before you even know they would have broken. You can see some examples of that here. Garuda Linux / Packages / Stable PKGBUILDs / Garuda Update · GitLab

I can't speak for using timeshift anymore, it is probably no longer officially supported. You should consider BTRFS Assistant Btrfs Assistant 1.0 is nearly here. If there's some missing functionality in timeshift, you should communicate what specifically that is.

If you are able to restore an old backup still, why not restore that, and upload or save your important data somewhere else, so you can avoid restoring to an old medium.

3 Likes

When the permission issue occurs, you could try

sudo chown -R $USER: $HOME

This will change the ownership of all files and directories within your home directory to you.

2 Likes

Let me share this wiki article I wrote up:

6 Likes

garuda-update did a job perfectly !
Last full system update: 2022-06-23
Full success, even after restart no issues so far! Thank you!!!

Do I understand it correctly that
sudo pacman -Syu
shouldn't be used any more?

I think so, but I just really like it and get use to backup on Garuda and Ubuntu as well. I don't care about backuping and restoring time. It's really easy , even from command line to restore. A couple of times it realy seved me and my data!

I really give a shot to snapper, but it failed in my case. Why many people choose it on top of timeshift? I was reading about that but either I'm too lame (more probably :stuck_out_tongue: ) or didn't get correctly snapper's adventage. Also watched on YT videos regarding snapper, but they seams outdated. In case of garuda we have lovely app and believe it's more advanced than versions which were presented..

Marked down, thank you filo :wink:
Guessing that command (if similar situation occurs ) has to be put from root terminal (mean CTRL+ALT+F3). Otherwise I'll receive "permission error" :slight_smile:

Go to TTY and login as root, not with your user account name.
Then you don't need sudo with commands. Just be careful with root, when using paths in command line, since by default starts in /root/ folder. Always check/confirm for correct path existence.

1 Like

image

Good reminder petsman! Thank you. That's true it's very easy to forget that step ! So I'm guessing in TTY it's better to login like above as my main @USER.

? I never got this.

Check if root files in /home/$USER with

find $HOME ! -user $USER -type f

Remove with

sudo chown -R $USER: $HOME

And please, do not post pictures from terminal outputs.

1 Like

Better than what?
In which case would you choose to login like this?

1 Like

Simple - at situation like mine when I was unable do to anything else :slight_smile:

Currently it's empty. I wasn't even expect anything right now. Believe something might appear one similar case with failed upgrading will happen.

Your home directory is not included in snapshots by default. If there is a permissions problem in your home directory trying to fix it by restoring from a snapshot will have no effect.

Generally, the most common reason for user permissions being screwed up is running terminal commands or GUI programs as root. Don't do that. :wink:

3 Likes

Yes you are right. However as a root I do usual things, nothing fancy or dangerous.

I have to say it again : problems started after system upgrade. Yes, I used then sudo pacman -Syu, because I've always done it that way. As a Arch based distro for me it's obviouse.

With root privillages I also set up docker (which was working just fine from months). Yes, I preffer docker more than podman, which for me seams to be limited.

Another case when I used higher level rights: set up remote connection.
Probably the biggest change on my side was uninstalling snapper and installing timeshift as replacement.

And I think that's it. Don't remember other needs.

In my case from last 2-3 months I had 3 times that particular situation when stable system once upgraded just littearly crashed (from my point of view). Scenarrio was always the same. That's why thought it's worth to mention about the case which I experienced.

TBF the last time I faced this was when I tried adding my user to a group using usermod but apparently I forgot the -a flag, which completely broke my user since I was removed from all groups apart from the one I tried to add, resulting in exactly this behaviour.

@zawier What is the output of id?

1 Like

This requires some attention, IMHO. It shouldn't happen as a pattern, so you should find the real pattern. If it happens in all system upgrades, or only in those where some specific packages are upgraded, so you need to find which one(s).

An unusual behavior I can spot is from PEBCAC.

This is not a standard Garuda partitioning scheme, where there are several btrfs subvolumes, as you probably know.

If login as $USER is not possible in TTY and this su - $USER method works, then something is wrong or needs investigation.

  • check user folder and contents ownership and permissions
  • check $USER groups
  • check sudoers settings
  • check journal for relevant messages
  • more, but we hope the above will be enough

Use the above to see what's wrong, or post here to get some advice.

5 Likes

In my case only once I used it
sudo usermod -aG docker zawier

I have a copy of all terminal history commands. I'm sure that's the only one time.

╰─λ id
uid=1000(zawier) gid=1001(zawier) groups=1001(zawier),3(sys),50(games),96(scanner),209(cups),956(sambashare),9
57(plugdev),960(docker),971(realtime),972(libvirt),985(video),991(lp),992(kvm),994(input),998(wheel),1000(auto
login)

Bying honest - I don't have an idea. Just trying to keep up with updates and rather don't check packages one by one if you mean that.

Yeap you are right it isn't. And a reason of thet is simple: over 1 year ago when when decided to give a try to Garuda distro and my main system was Windows. Then I didn't want to remove it (just in case). So I've shrinked Win partition to half and other half gave to Linux.

I've needed a boot partition for grub & other option ( I have got also Macrionium Reflect installed , which could be run up while computer turning on).
Over a year ago also I've noticed problem to set up Garuda side by side using included installer. The problem was with partitions. But I have figured it out that when I do it manually it just works.

After some time bought another ssd drive, copied a garuda's data and from that time I have 2 ssds with 2 systems. Previously selecting system was handled by bootloader (but that was real pain in case when one of the system was reinstalled of something happened with grub..).
On my PC case have got turn on/off swittcher for 6 devices (hard drives / dvd rom etc..). And that sollution is the best choice I've made.

I'd love to check it as well! Let's go for it. :slight_smile: Do you have any specific commands which you are interesed in particular?

╰─λ groups zawier
sys games scanner wheel input kvm lp video libvirt realtime autologin docker cups plugdev sambashare zawier
╰─λ sudo -l
[sudo] password for zawier:
Matching Defaults entries for zawier on zawier-garuda:
editor=/usr/bin/micro, insults, pwfeedback, env_keep+=QT_GRAPHICSSYSTEM

Runas and Command-specific defaults for zawier:
Defaults!/etc/ctdb/statd-callout !requiretty

User zawier may run the following commands on zawier-garuda:
(ALL) ALL

Hopefully perhaps that might help:

✦  ╰─λ journalctl -p 3 -xb
cze 25 23:57:05 zawier-garuda kernel: platform gpio_ich.2.auto: failed to claim resource 0: [io  0x0480-0x04ff]
cze 25 23:57:04 zawier-garuda systemd-udevd[327]: host9: /usr/lib/udev/rules.d/50-sata.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.1/ata10/host9/scsi_host/>
cze 25 23:57:04 zawier-garuda systemd-udevd[327]: host8: /usr/lib/udev/rules.d/50-sata.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.1/ata9/host8/scsi_host/h>
cze 25 23:57:05 zawier-garuda systemd-tmpfiles[473]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
cze 25 23:57:07 zawier-garuda colord-sane[600]: io/hpmud/pp.c 627: unable to read device-id ret=-1
cze 25 23:57:11 zawier-garuda kernel: tda1004x: no firmware upload (timeout or file not found?)
cze 25 23:57:11 zawier-garuda kernel: tda1004x: firmware upload failed
cze 25 23:57:09 zawier-garuda sddm-helper[1177]: gkr-pam: couldn't unlock the login keyring.
cze 25 23:57:09 zawier-garuda nmbd[1530]: [2022/06/25 23:57:09.692927,  0] ../../source3/nmbd/nmbd.c:901(main)
cze 25 23:57:09 zawier-garuda nmbd[1530]:   nmbd version 4.16.2 started.
cze 25 23:57:09 zawier-garuda nmbd[1530]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
cze 25 23:57:09 zawier-garuda smbd[1551]: [2022/06/25 23:57:09.867338,  0] ../../source3/smbd/server.c:1741(main)
cze 25 23:57:09 zawier-garuda smbd[1551]:   smbd version 4.16.2 started.
cze 25 23:57:09 zawier-garuda smbd[1551]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
cze 25 23:57:10 zawier-garuda systemd[1209]: /run/user/1000/systemd/generator.late/[email protected]:18: WorkingDirectory= path is not absolute, ignoring: 
cze 25 23:57:13 zawier-garuda systemd[1209]: Failed to start BTRFS Assistant Snapper check.
░░ Subject: Zadanie uruchamiania dla jednostki UNIT się nie powiodło
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Zadanie uruchamiania dla jednostki UNIT zostało ukończone z niepowodzeniem.
░░ 
░░ Identyfikator zadania: 128, wynik zadania: failed.
cze 25 23:57:21 zawier-garuda pipewire[4005]: spa.v4l2: '/dev/video2' VIDIOC_ENUM_FRAMESIZES: Niewłaściwy ioctl dla urządzenia
cze 25 23:57:32 zawier-garuda nmbd[1530]: [2022/06/25 23:57:32.745751,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
cze 25 23:57:32 zawier-garuda nmbd[1530]:   *****
cze 25 23:57:32 zawier-garuda nmbd[1530]: 
cze 25 23:57:32 zawier-garuda nmbd[1530]:   Samba name server ZAWIER-GARUDA is now a local master browser for workgroup WORKGROUP on subnet 192.168.3.10
cze 25 23:57:32 zawier-garuda nmbd[1530]: 
cze 25 23:57:32 zawier-garuda nmbd[1530]:   *****
cze 25 23:59:03 zawier-garuda sudo[11261]:   zawier : a password is required ; TTY=pts/1 ; PWD=/home/zawier ; USER=root ; COMMAND=/usr/bin/true
cze 26 00:00:12 zawier-garuda sudo[15514]:   zawier : a password is required ; TTY=pts/1 ; PWD=/home/zawier ; USER=root ; COMMAND=/usr/bin/true
cze 26 00:00:17 zawier-garuda sudo[15537]:   zawier : a password is required ; TTY=pts/1 ; PWD=/home/zawier/usbimager ; USER=root ; COMMAND=/usr/bin/true
cze 26 00:00:19 zawier-garuda sudo[15912]:   zawier : a password is required ; TTY=pts/1 ; PWD=/home/zawier/usbimager ; USER=root ; COMMAND=/usr/bin/true
cze 26 00:00:26 zawier-garuda sudo[15943]:   zawier : a password is required ; TTY=pts/1 ; PWD=/home/zawier/usbimager/src ; USER=root ; COMMAND=/usr/bin/true
cze 26 00:00:44 zawier-garuda sudo[16299]:   zawier : a password is required ; TTY=pts/1 ; PWD=/home/zawier/usbimager/src ; USER=root ; COMMAND=/usr/bin/true
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc92e40: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcb245e: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcd5175: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcf6d64: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd13d87: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd30520: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd4af24: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd666a0: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd84ad1: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdda17ab: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xddc2ddd: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdde4d27: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde08614: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde2ba6c: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde4db12: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde6eb7a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde91bde: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdeb417d: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xded740a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdefb70a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf1dfc0: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf3b772: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf5e5b3: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf7b9eb: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf9986b: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdfbb021: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdfd9e02: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdffb81e: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe01b54d: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe03c284: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe05bfa8: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe07c0cf: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe09c360: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0b6d43: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0d8a6a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0faf98: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe11b06f: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe13bf20: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc92e40: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcb245e: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcd5175: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcf6d64: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd13d87: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd30520: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd4af24: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd666a0: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd84ad1: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdda17ab: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xddc2ddd: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdde4d27: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde08614: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde2ba6c: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde4db12: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde6eb7a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde91bde: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdeb417d: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xded740a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdefb70a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf1dfc0: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf3b772: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf5e5b3: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf7b9eb: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf9986b: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdfbb021: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdfd9e02: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdffb81e: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe01b54d: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe03c284: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe05bfa8: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe07c0cf: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe09c360: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0b6d43: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0d8a6a: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0faf98: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe11b06f: -5
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:02:03 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe13bf20: -5
cze 26 00:02:51 zawier-garuda nmbd[1530]: [2022/06/26 00:02:51.981022,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
cze 26 00:02:51 zawier-garuda nmbd[1530]:   *****
cze 26 00:02:51 zawier-garuda nmbd[1530]: 
cze 26 00:02:51 zawier-garuda nmbd[1530]:   Samba name server ZAWIER-GARUDA is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
cze 26 00:02:51 zawier-garuda nmbd[1530]: 
cze 26 00:02:51 zawier-garuda nmbd[1530]:   *****
cze 26 00:06:05 zawier-garuda sudo[20452]:   zawier : a password is required ; TTY=pts/2 ; PWD=/home/zawier ; USER=root ; COMMAND=/usr/bin/true
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc92e40: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcb245e: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcd5175: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdcf6d64: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd13d87: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd30520: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd4af24: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd666a0: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdd84ad1: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdda17ab: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xddc2ddd: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdde4d27: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde08614: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde2ba6c: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde4db12: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde6eb7a: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xde91bde: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdeb417d: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xded740a: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdefb70a: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf1dfc0: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf3b772: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf5e5b3: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf7b9eb: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdf9986b: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdfbb021: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdfd9e02: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdffb81e: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe01b54d: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe03c284: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe05bfa8: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe07c0cf: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe09c360: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0b6d43: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0d8a6a: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe0faf98: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe11b06f: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xe13bf20: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc83bcb: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: Failed to read block 0xdc92e40: -5
cze 26 00:08:09 zawier-garuda kernel: SQUASHFS error: lzo decompression failed, data probably corrupt

From what I was able to tell, this does not look proper: Why would it log into your user as root.

TBF would just reinstall the root partition of garuda. This would be too much hassle for me to be willing to deal with.

Could you try to cat /etc/passwd - Maybe some home directories got messed up in there

Sure, here you have:

File: /etc/passwd
root:x:0:0::/root:/bin/bash
bin:x:1:1::/:/usr/bin/nologin
daemon:x:2:2::/:/usr/bin/nologin
mail:x:8:12::/var/spool/mail:/usr/bin/nologin
ftp:x:14:11::/srv/ftp:/usr/bin/nologin
http:x:33:33::/srv/http:/usr/bin/nologin
nobody:x:65534:65534:Nobody:/:/usr/bin/nologin
dbus:x:81:81:System Message Bus:/:/usr/bin/nologin
systemd-coredump:x:981:981:systemd Core Dumper:/:/usr/bin/nologin
systemd-network:x:980:980:systemd Network Management:/:/usr/bin/nologin
systemd-oom:x:979:979:systemd Userspace OOM Killer:/:/usr/bin/nologin
systemd-journal-remote:x:978:978:systemd Journal Remote:/:/usr/bin/nologin
systemd-resolve:x:977:977:systemd Resolver:/:/usr/bin/nologin
systemd-timesync:x:976:976:systemd Time Synchronization:/:/usr/bin/nologin
uuidd:x:68:68::/:/usr/bin/nologin
avahi:x:975:975:Avahi mDNS/DNS-SD daemon:/:/usr/bin/nologin
named:x:40:40:BIND DNS Server:/:/usr/bin/nologin
git:x:974:974:git daemon user:/:/usr/bin/git-shell
rpc:x:32:32:Rpcbind Daemon:/var/lib/rpcbind:/usr/bin/nologin
tss:x:973:973:tss user for tpm2:/:/usr/bin/nologin
dnsmasq:x:969:969:dnsmasq daemon:/:/usr/bin/nologin
geoclue:x:968:968:Geoinformation service:/var/lib/geoclue:/usr/bin/nologin
libvirt-qemu:x:967:967:Libvirt QEMU user:/:/usr/bin/nologin
minetest:x:966:966:minetest:/var/lib/minetest:/usr/bin/nologin
murmur:x:122:122:Murmur User:/var/db/murmur:/usr/bin/nologin
nm-openconnect:x:965:965:NetworkManager OpenConnect:/:/usr/bin/nologin
nm-openvpn:x:964:964:NetworkManager OpenVPN:/:/usr/bin/nologin
ntp:x:87:87:Network Time Protocol:/var/lib/ntp:/bin/false
ldap:x:439:439:LDAP Server:/var/lib/openldap:/usr/bin/nologin
openvpn:x:963:963:OpenVPN:/:/usr/bin/nologin
polkitd:x:102:102:PolicyKit daemon:/:/usr/bin/nologin
rtkit:x:133:133:RealtimeKit:/proc:/usr/bin/nologin
sddm:x:962:962:Simple Desktop Display Manager:/var/lib/sddm:/usr/bin/nologin
usbmux:x:140:140:usbmux user:/:/usr/bin/nologin
ice:x:101:101:Ice User:/var/lib/ice:/usr/bin/nologin
zawier:x:1000:1001:zawier:/home/zawier:/bin/bash
qemu:x:961:961:QEMU user:/:/usr/bin/nologin
x2gouser:x:111:111:x2gouser:/var/lib/x2go:/usr/bin/nologin
x2goprint:x:112:112:x2goprint:/var/spool/x2go:/usr/bin/nologin
saned:x:959:959:SANE daemon user:/:/usr/bin/nologin
colord:x:958:958:Color management daemon:/var/lib/colord:/usr/bin/nologin
cups:x:209:209:cups helper user:/:/usr/bin/nologin
tor:x:43:43::/var/lib/tor:/usr/bin/nologin
deluge:x:955:955:Deluge BitTorrent daemon:/srv/deluge:/usr/bin/nologin

What do you mean regarding:

?