OS loading from boot menu breaks after an update

OS loading from boot menu breaks after an update. Usually two successive updates one day after the other. Always clear packages using "Stacer" after each update. Trying every Snap now does not work. Was able to use really old Snaps initially now those also do not work.

Much appreciated.

System:
Kernel: 6.1.6-hardened2-1-hardened arch: x86_64 bits: 64 compiler: gcc
v: 12.2.0 parameters: pti=on page_alloc.shuffle=1
BOOT_IMAGE=/@/boot/vmlinuz-linux-hardened
root=UUID=05bceb4d-b058-461f-b1fc-5c0e56056f6b rw [email protected]
quiet
cryptdevice=UUID=fb551a59-b1f6-4fb4-a902-0a18c46bbd4c:luks-fb551a59-b1f6-4fb4-a902-0a18c46bbd4c
root=/dev/mapper/luks-fb551a59-b1f6-4fb4-a902-0a18c46bbd4c quiet splash
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.26.5 tk: Qt v: 5.15.8 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X412DAP_F412DA
v: 1.0 serial: <superuser required>
Mobo: ASUSTeK model: X412DAP v: 1.0 serial: <superuser required>
UEFI: American Megatrends v: X412DAP.300 date: 12/25/2019
Battery:
ID-1: BAT0 charge: 18.6 Wh (61.6%) condition: 30.2/37.1 Wh (81.4%)
volts: 7.8 min: 7.8 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
status: discharging cycles: 62
CPU:
Info: model: AMD Ryzen 3 3250U with Radeon Graphics bits: 64 type: MT MCP
arch: Zen/Zen+ note: check gen: 1 level: v3 note: check built: 2019
process: GF 12nm family: 0x17 (23) model-id: 0x18 (24) stepping: 1
microcode: 0x8108109
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 192 KiB desc: d-2x32 KiB; i-2x64 KiB L2: 1024 KiB desc: 2x512 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1400 min/max: 1400/2600 boost: enabled scaling:
driver: acpi-cpufreq governor: powersave cores: 1: 1400 2: 1400 3: 1400
4: 1400 bogomips: 20769
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Picasso/Raven 2 [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
ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:15d8
class-ID: 0300 temp: 54.0 C
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu 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: eDP-1 mapped: eDP model: BOE Display 0x07f6 built: 2018
res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 size: 309x174mm (12.17x6.85")
diag: 355mm (14") ratio: 16:9 modes: max: 1920x1080 min: 640x480
API: OpenGL v: 4.6 Mesa 22.3.3 renderer: AMD Radeon Vega 3 Graphics
(raven2 LLVM 15.0.7 DRM 3.49 6.1.6-hardened2-1-hardened)
direct render: Yes
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.1
chip-ID: 1002:15de class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_pci_acp3x
v: kernel
alternate: snd_rn_pci_acp3x,snd_pci_acp5x,snd_pci_acp6x,snd_acp_pci,snd_rpl_pci_acp6x,snd_pci_ps,snd_sof_amd_renoir,snd_sof_amd_rembrandt
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.5 chip-ID: 1022:15e2
class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound API: ALSA v: k6.1.6-hardened2-1-hardened running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
Message: No PCI device data found.
Device-1: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152
bus-ID: 2-1.4:3 chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
IF: enp3s0f3u1u4 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 15.61 GiB (6.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLQ256HAJD-00000 size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: FXV7000Q temp: 18.9 C scheme: GPT
Partition:
ID-1: / raw-size: 45.9 GiB size: 45.9 GiB (100.00%) used: 15.35 GiB (33.5%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fb551a59-b1f6-4fb4-a902-0a18c46bbd4c
ID-2: /boot/efi raw-size: 500 MiB size: 499 MiB (99.80%)
used: 259.4 MiB (52.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 45.9 GiB size: 45.9 GiB (100.00%)
used: 15.35 GiB (33.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fb551a59-b1f6-4fb4-a902-0a18c46bbd4c
ID-4: /var/log raw-size: 45.9 GiB size: 45.9 GiB (100.00%)
used: 15.35 GiB (33.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fb551a59-b1f6-4fb4-a902-0a18c46bbd4c
ID-5: /var/tmp raw-size: 45.9 GiB size: 45.9 GiB (100.00%)
used: 15.35 GiB (33.5%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-fb551a59-b1f6-4fb4-a902-0a18c46bbd4c
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 5.75 GiB used: 572.2 MiB (9.7%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 54.9 C mobo: N/A gpu: amdgpu temp: 54.0 C
Fan Speeds (RPM): cpu: 0
Info:
Processes: 228 Uptime: 1h 2m wakeups: 50878 Memory: 5.75 GiB
used: 2.25 GiB (39.1%) Init: systemd v: 252 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1255
libs: 329 tools: octopi,paru Shell: fish v: 3.6.0 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.24
Garuda (2.6.14-1):
System install date:     2023-01-04
Last full system update: 2023-01-21 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio
Windows dual boot:       No/Undetected
Failed units:            dev-nvme0n1p2.swap

This system is not accessible so it is not possible to get stats currently.

Will be resetting this system and will post stats after this occurs.

Much appreciated.

Uhm, and what exactly happens when you try to boot? I need you to outline exactly what happens as well as show what recovery mode etc boots into..

Fails at "Loading initial ramdisk"

hangs there indefinitely; after checking encryption; loading boot menu

Advanced options of Zen / all failback / Xanmod / hardened all fail; as well as all snapshots.

Snapper update might have fixed this; have not checked snaps yet; looks like they are being over written with the snap from the date that is corrupted.

Reinstalling the system at this point now breaks being able to reinstall the system until a new iso is released will not be able to fix at least one system & maybe two so waiting for that.
Much appreciated.

Also update remote fix is no longer fixing the the issue of this bug report that was closed.

Remote attacker will just find new bugs to exploit; happy to keep posting; will make Linux, Arch, KDE more secure. Much appreciated.

This will reset a few configuration files like pacman.conf 🛑Are you sure? (y/n)
y
--2023-01-24 16:53:16--  https://pkgbuild.com/~morganamilo/pacman-static/x86_64/bin/pacman-static
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving pkgbuild.com (pkgbuild.com)... 78.46.178.133, 2a01:4f8:c2c:51e2::1
Connecting to pkgbuild.com (pkgbuild.com)|78.46.178.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4606712 (4.4M) [application/octet-stream]
Saving to: ‘/tmp/tmp.LjPSZ8MkBY’

/tmp/tmp.LjPSZ8MkBY         100%[=========================================>]   4.39M  3.80MB/s    in 1.2s

2023-01-24 16:53:19 (3.80 MB/s) - ‘/tmp/tmp.LjPSZ8MkBY’ saved [4606712/4606712]


.--.                  Pacman v6.0.1 - libalpm v13.0.1
/ _.-' .-.  .-.  .-.   Copyright (C) 2006-2021 Pacman Development Team
\  '-. '-'  '-'  '-'   Copyright (C) 2002-2006 Judd Vinet
'--'
This program may be freely redistributed under
the terms of the GNU General Public License.

--2023-01-24 16:53:19--  https://gitlab.com/garuda-linux/tools/garuda-tools/-/raw/master/data/pacman-default.conf
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving gitlab.com (gitlab.com)... 172.65.251.78, 2606:4700:90:0:f22e:fbec:5bed:a9b9
Connecting to gitlab.com (gitlab.com)|172.65.251.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2515 (2.5K) [text/plain]
Saving to: ‘/etc/pacman.conf’

/etc/pacman.conf            100%[=========================================>]   2.46K  --.-KB/s    in 0s

2023-01-24 16:53:19 (10.3 MB/s) - ‘/etc/pacman.conf’ saved [2515/2515]

--2023-01-24 16:53:19--  https://archlinux.org/mirrorlist/all/
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving archlinux.org (archlinux.org)... 95.217.163.246, 2a01:4f9:c010:6b1f::1
Connecting to archlinux.org (archlinux.org)|95.217.163.246|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 48600 (47K) [text/plain]
Saving to: ‘/etc/pacman.d/mirrorlist’

/etc/pacman.d/mirrorlist    100%[=========================================>]  47.46K   276KB/s    in 0.2s

2023-01-24 16:53:21 (276 KB/s) - ‘/etc/pacman.d/mirrorlist’ saved [48600/48600]

--2023-01-24 16:53:21--  https://aur.chaotic.cx/mirrorlist.txt
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving aur.chaotic.cx (aur.chaotic.cx)... 185.199.108.153, 185.199.111.153, 185.199.109.153, ...
Connecting to aur.chaotic.cx (aur.chaotic.cx)|185.199.108.153|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2822 (2.8K) [text/plain]
Saving to: ‘/etc/pacman.d/chaotic-mirrorlist’

/etc/pacman.d/chaotic-mirro 100%[=========================================>]   2.76K  --.-KB/s    in 0s

2023-01-24 16:53:22 (13.5 MB/s) - ‘/etc/pacman.d/chaotic-mirrorlist’ saved [2822/2822]

gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/6DE85F3148560A600472507C635ABE8795AA4579.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from archlinux.gpg...
==> Appending keys from chaotic.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signed 12 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
-> Disabled 60 keys.
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  12  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  12  signed:  95  trust: 0-, 0q, 0n, 12m, 0f, 0u
gpg: depth: 2  valid:  75  signed:  26  trust: 75-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-03-30
gpg: key A6234074498E9CEE: 4 duplicate signatures removed
gpg: key A6234074498E9CEE: 1 signature reordered
gpg: key A6234074498E9CEE: "Christian Hesse <[email protected]>" 6 signatures cleaned
gpg: key FBA220DFC880C036: "Nico Jensch (Chaotic-AUR) <[email protected]>" not changed
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  12  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  12  signed:  95  trust: 0-, 0q, 0n, 12m, 0f, 0u
gpg: depth: 2  valid:  75  signed:  26  trust: 75-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-03-30
gpg: Total number processed: 2
gpg:              unchanged: 1
gpg:     signatures cleaned: 6
-> Locally signed 2 keys.
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  13  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  13  signed:  94  trust: 1-, 0q, 0n, 12m, 0f, 0u
gpg: depth: 2  valid:  74  signed:  26  trust: 74-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2023-03-30
rm: cannot remove '/var/cache/pacman/pkg/*': No such file or directory
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
:: Synchronizing package databases...
garuda is up to date
core                                  152.1 KiB   207 KiB/s 00:01 [------------------------------------] 100%
extra                                1745.9 KiB  1446 KiB/s 00:01 [------------------------------------] 100%
community                               7.2 MiB  6.39 MiB/s 00:01 [------------------------------------] 100%
multilib                              164.9 KiB   250 KiB/s 00:01 [------------------------------------] 100%
chaotic-aur                             2.3 MiB  5.02 MiB/s 00:00 [------------------------------------] 100%
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: failed to synchronize all databases (unexpected error)

Please always post any text as text, not as an image.
You know how it works. :slight_smile:


BTW, I update several PC, with different Garuda Linux DE, two times everyday and nothing break.


Did you try standard zen kernel, other kernel like lts and mainline?


Seems “Stacer” broke more than it help.

5 Likes

Tried multiple kernels after the first break as hardened & XanMod were installed; after reinstalling OS it was not possible to boot; now thinking it might be due to Gurada accessing POP OS on other harddrive or due to payload drop onto the drive. Firmware & bios hacking might play a part too besides update cache payload deploy.

Stacer was being attacked at install; this is not a normal circumstance; have been made aware they are behind on bug reports. Thing that made it worse was installing Stacer pre updates to try to bypass the install being exploited. Can not fix this system until a new ISO is released & one is due.

JavaScript is even more exploitable seems like.

Much appreciated.