after latest update, gets stuck on boot with the message sbin/init not found. Tried booting into snapshots, but same on all of them. Boots if I choose the 2nd boot option under advanced boot (fallback initramfs).
here's my garuda-inxi :
System:
Kernel: 6.2.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=cbcd5203-0aca-4432-a2a8-6232734fd154 rw rootflags=subvol=@
rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.2 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: STRIX Z270G GAMING v: Rev 1.xx
serial: <superuser required> UEFI: American Megatrends v: 1009
date: 07/23/2017
CPU:
Info: model: Intel Core i7-7700K bits: 64 type: MT MCP arch: Kaby Lake
gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 9 microcode: 0xF0
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled 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: 2411 high: 4500 min/max: 800/4500 scaling:
driver: intel_pstate governor: performance cores: 1: 2682 2: 2034 3: 2095
4: 2547 5: 4500 6: 2014 7: 1950 8: 1471 bogomips: 67200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: eVga.com.
driver: nvidia v: 525.89.02 alternate: nouveau,nvidia_drm non-free: 525.xx+
status: current (as of 2023-02) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.0 chip-ID: 10de:1b06 class-ID: 0300
Device-2: Logitech C922 Pro Stream Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-2:3 chip-ID: 046d:085c
class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 90 s-size: 542x301mm (21.34x11.85")
s-diag: 620mm (24.41")
Monitor-1: DP-4 res: 1920x1080 dpi: 90 size: 544x303mm (21.42x11.93")
diag: 623mm (24.52") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.89.02 renderer: NVIDIA GeForce GTX 1080
Ti/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 1-2:3 alternate: snd_soc_avs
chip-ID: 046d:085c bus-ID: 00:1f.3 class-ID: 0102 serial: <filter>
chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA GP102 HDMI Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:10ef class-ID: 0403
Device-3: Logitech C922 Pro Stream Webcam type: USB
driver: snd-usb-audio,uvcvideo
Sound API: ALSA v: k6.2.2-zen1-1-zen running: yes
Sound Interface: sndio v: N/A running: no
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.66 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: ASUSTeK driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 04:00.0 chip-ID: 168c:003e class-ID: 0280 temp: 53.0 C
IF: wlp4s0 state: up mac: <filter>
Bluetooth:
Device-1: ASUSTek Qualcomm Bluetooth 4.1 type: USB driver: btusb v: 0.8
bus-ID: 1-7:5 chip-ID: 0b05:1825 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: <filter>
Drives:
Local Storage: total: 580.36 GiB used: 66.67 GiB (11.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 3B7QCXE7 temp: 34.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1
size: 114.6 GiB block-size: physical: 512 B logical: 512 B type: N/A
serial: <filter> rev: 1.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 66.67 GiB (14.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 66.67 GiB (14.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 66.67 GiB (14.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 66.67 GiB (14.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.55 GiB used: 512 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A gpu: nvidia temp: 34 C
Fan Speeds (RPM): cpu: 1040 gpu: nvidia fan: 0%
Info:
Processes: 258 Uptime: 15m wakeups: 1 Memory: 15.55 GiB
used: 3.08 GiB (19.8%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 1916 libs: 542 tools: octopi,paru Shell: fish v: 3.6.0 default: Bash
v: 5.1.16 running-in: konsole inxi: 3.3.25
Garuda (2.6.15-1):
System install date: 2023-02-08
Last full system update: 2023-03-08
Is partially upgraded: No
Relevant software: snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot: No/Undetected
Failed units:
1 Like
Naman
March 8, 2023, 7:55pm
2
That means somehow systemd binary is not available. (in /lib/systemd) ( Because sbin/init links to that file )
Did you mess up with it?
Please post output of
history
As text, enclosed in 3 ~ .
1 Like
2023-03-08 06:42:49 reboot
2023-03-08 06:41:42 sudo garuda-update
2023-03-05 04:04:09 ls
2023-03-05 04:02:59 sudo pacman -Syu
2023-03-05 04:02:36 pacman -Syu
2023-03-05 04:02:23 pacman
2023-03-05 03:55:31 man pacman
2023-03-05 03:53:22 fastfetch
2023-03-05 03:49:28 cleanup
2023-03-05 03:48:19 grubup
2023-03-05 03:47:27 upd
2023-03-05 03:40:03 fastfetch --help
2023-03-05 03:28:54 fastfetch --gen-config
2023-03-05 03:18:48 fastfetch --list-presets
2023-03-05 03:05:27 fastfetch -l garuda-linux
2023-03-05 03:05:14 fastfetch -l garuda
2023-03-05 03:04:22 fastfetch --list-logos
2023-03-05 03:03:42 fastfetch -l garudadragon
2023-03-05 02:54:20 fastfetch --list-config-paths
2023-03-05 02:53:59 fastfetch--list-config-paths
2023-03-05 02:51:27 fastfetch --print-logos
2023-03-05 00:19:21 garuda-update
2023-02-24 23:24:28 cd ventoy-1.0.88/
2023-02-24 23:23:55 cd Documents/
2023-02-24 23:14:11 pacman -Rns ventoy-bin
2023-02-24 22:33:28 ps
2023-02-23 21:52:28 exit
2023-02-23 21:52:20 ls -a
2023-02-23 21:52:00 cd ventoy
2023-02-23 21:51:29 sudo mount /dev/sda1 ventoy/
2023-02-23 21:50:56 mount /dev/sda1 ventoy/
2023-02-23 21:50:13 cd Desktop/
2023-02-23 21:50:00 cd desktop
2023-02-23 21:49:46 ch
2023-02-23 21:48:55 cd /dev/sda1
2023-02-23 21:48:32 ls /dev/sda1
2023-02-23 21:47:28 VentoyPlugson.sh
2023-02-23 21:45:07 pacman -Ss VentoyPlugson
2023-02-23 21:42:54 sudo bash VentoyPlugson.sh /dev/sdX
2023-02-22 23:45:50 sudo pacman -Rns multibootusb
2023-02-22 23:45:16 pacman -Rns multibootusb
2023-02-22 05:00:43 cd ..
2023-02-22 05:00:15 pwd
2023-02-22 04:49:36 cd cursors
2023-02-22 04:49:24 cd cursor
2023-02-22 04:48:51 cd breeze_cursors/
2023-02-22 04:48:27 cd icons
2023-02-22 04:47:41 cd -a
2023-02-22 04:47:15 cd /usr/share/icons/
2023-02-22 04:45:52 ls /usr/share/icons/
2023-02-22 03:52:08 sudo pacman -Rns latte-dock
2023-02-22 03:51:52 sudo
2023-02-22 03:51:36 pacman -Rns latte-dock
2023-02-22 03:51:02 pacman -Ss latte
2023-02-22 01:01:08 cd desk
2023-02-22 00:45:22 paru -Syu ventoy-bin
2023-02-21 20:27:56 sudo systemctl enable --now cups
2023-02-21 20:26:38 sudo pacman -Syu cups
2023-02-21 20:25:59 sudo pacman -Rns cups
2023-02-21 20:24:00 pacman -Syu cups
2023-02-21 20:15:14 paru -Rns cnijfilter-common
2023-02-21 20:12:32 paru -Syu cnijfilter-common
2023-02-21 20:12:01 sudo paru -Rns cnijfilter-common
2023-02-21 20:07:08 sudo paru -Syu cnijfilter-common
2023-02-21 20:00:33 man paru
2023-02-21 09:56:11 sudo paru -Ss multibootusb
2023-02-21 09:55:34 sudo paru -Syu multibootusb
2023-02-21 09:53:32 sudo paru -Syu MultiBootUSB
2023-02-20 05:21:04 sudo garuda-boot-options
2023-02-20 05:20:27 garuda-boot-options
2023-02-20 05:19:21 sudo paru -Syu grub-customizer
2023-02-20 04:44:01 git clone https://github.com/ChrisTitusTech/Top-5-Bootloader-Themes
2023-02-20 02:17:03 sudo update-grub
2023-02-20 01:50:11 sudo update-grub2
2023-02-18 07:08:40 sudo pacman -Rns roccat-tools-konepure
2023-02-18 06:59:05 sudo paru -Syu roccat-tools-konepure
2023-02-17 00:46:47 clear
2023-02-17 00:46:39 pacman -Ss xkill
2023-02-17 00:46:16 pacmin -Ss xkill
2023-02-16 01:05:57 man chmod
2023-02-16 01:04:59 ls -lah
2023-02-16 01:04:45 cd ~
2023-02-16 00:56:48 man rmdir
2023-02-16 00:56:02 rmdir /eruption
2023-02-16 00:55:38 sudo rmdir /etc/eruption
2023-02-16 00:55:15 sudo rm eruption.conf.pacsave
2023-02-16 00:53:49 sudo rmdir /etc/eruption --ignore-fail-on-non-empty
2023-02-16 00:52:08 sudo rmdir /etc/eruption -rf
2023-02-16 00:49:54 rmdir /etc/eruption
2023-02-16 00:18:58 htop
2023-02-15 06:27:36 sudo pacman -Rns $(pacman -Qdtq)
2023-02-15 06:26:38 sudo pacman -Rns
2023-02-15 06:25:58 pacman -Rns
2023-02-15 06:25:23 pacman -Qdtq
2023-02-15 06:24:49 pacman -Qdt
2023-02-15 06:24:02 sudo pacman -Rsc eruption
2023-02-14 19:58:15 shutdown
2023-02-14 19:57:24 sudo systemctl enable --now eruption.service
2023-02-14 19:57:08 systemctl --user enable --now eruption-process-monitor.service
2023-02-14 19:56:57 systemctl --user enable --now eruption-audio-proxy.service
2023-02-14 19:56:39 systemctl --user enable --now eruption-fx-proxy.service
2023-02-14 19:50:21 paru -Syu aur/eruption
2023-02-14 19:49:20 sudo paru -Syu aur/eruption
2023-02-14 19:46:44 sudo pacman -U 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-keyring.pkg.tar.zst' 'ht
tps://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-mirrorlist.pkg.tar.zst'
2023-02-14 19:46:18 sudo pacman-key --lsign-key FBA220DFC880C036
2023-02-14 19:45:51 sudo pacman-key --recv-key FBA220DFC880C036 --keyserver keyserver.ubuntu.com
2023-02-14 05:15:38 sudo pacman -Ss etcher-bin
2023-02-14 05:15:13 pacman -Ss balena etcher
2023-02-14 05:05:29 pacman -Ss balena
2023-02-14 05:02:35 pacman -Ss etcher
2023-02-14 04:35:44 sudo pacman -Syu etcher-bin
2023-02-14 04:24:44 sudo pacman-key --recv-key FBA220DFC880C036 --keyserver keyserver.ubuntu.com
2023-02-14 04:24:19 pacman-key --recv-key FBA220DFC880C036 --keyserver keyserver.ubuntu.com
2023-02-14 02:53:18 eruption
2023-02-14 02:50:21 paru -Syu aur/eruption
systemctl --user enable --now eruption-fx-proxy.service
systemctl --user enable --now eruption-audio-proxy.service
systemctl --user enable --now eruption-process-monitor.service
sudo systemctl enable --now eruption.service
2023-02-11 03:28:03 sudo firewall-cmd --permanent --zone=public --add-service=kdeconnect
sudo firewall-cmd --reload
2023-02-11 03:27:40 sudo iptables -I INPUT -i <yourinterface> -p udp --dport 1714:1764 -m state --state NEW,ES
TABLISHED -j ACCEPT
sudo iptables -I INPUT -i <yourinterface> -p tcp --dport 1714:1764 -m state --state NEW,ESTABLISHED -j ACCEPT
sudo iptables -A OUTPUT -o <yourinterface> -p udp --sport 1714:1764 -m state --state NEW,ESTABLISHED -j ACCEPT
sudo iptables -A OUTPUT -o <yourinterface> -p tcp --sport 1714:1764 -m state --state NEW,ESTABLISHED -j ACCEPT
2023-02-11 03:26:28 firewall-config
2023-02-11 03:25:37 sudo ufw allow 1714:1764/udp
sudo ufw allow 1714:1764/tcp
sudo ufw reload
2023-02-11 03:24:49 sudo firewall-cmd --permanent --zone=public --add-service=kdeconnect
2023-02-11 03:10:56 killall kdeconnectd
mv ~/.config/kdeconnect ~/.config/kdeconnect.bak
2023-02-11 03:10:00 netcat -z -v <108.231.200.32> 1714-1764
2023-02-11 03:06:58 netcat -z -v <192.168.1.68> 1714-1764
2023-02-11 03:02:50 sudo netstat -tunelp | grep -i kdeconnect
Also checked and the executable is still there.
I would strictly advice you not to use pacman -Syu and use garuda-update only in future updates.
I honestly don't even remember entering that or why I would have unless it was just out of habit, but I'll make sure I don't anymore.
Could have possibly been me using auto fill and not paying attention.
Hmm, that’s an interesting clue. Have you tried rebuilding your initramfs? Paste the input and output into the thread:
mkinitcpio -P
Then try booting with the normal image again.
2 Likes
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen.img
==> Starting build: 6.2.2-zen1-1-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'fallback'
-> -k /boot/vmlinuz-linux-zen -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-zen-fallback.img -S autodetect
==> Starting build: 6.2.2-zen1-1-zen
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
-> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-zen-fallback.img
==> Image generation successful
boots up again now. Thanks!
1 Like
Are you dual booting with your machine? The latest update to Arch Linux apparently broke it due to one kernel change.
Brodie Robertson talked about this a day or so ago on his YouTube channel. There is a solution. See if this fixes it for you:
1 Like
Hi @iBolski , it's nice you are trying to be helpful, but the video you watched is not related to this issue in any way.
Also the issue was already solved. Maybe you didn't read the thread before posting?
2 Likes
Thank you for the sentiment. And no, unrelated, I'm only booting Linux. I would be curious to know what may have caused the issue to begin with so that I might avoid it in the future.
I do not know for certain, but it is possible something needed was accidentally removed during one of these many recursive package removal commands in your history:
Especially the -c option needs to be used with care; it is very easy to accidentally remove stuff you actually need.
-c, --cascade
Remove all target packages, as well as all packages that depend on one or more target packages. This operation is recursive and must be used with care, since it can remove many potentially needed packages.
Like I said, I don’t know for certain that is what happened but it seems likely.
As far as why your snapshots did not work, each time you trigger a Pacman exchange there is a hook that generates a snapshot before and after. At some point your initramfs image was not sufficient to boot your system and needed to be rebuilt, but the bad image kept getting snapshotted by the Pacman hook before the rebuild happened. All of the “good” snapshots were overwritten in the process.
I think all of us in the forum have at one point or another deleted something important by mistake.
1 Like
Have multiple boot machines have not checked to see if Garuda breaks after update.
PopOS installed Kernel 6.2 & still boots with no problems.
Although can not check Garuda because having this same issue again.
This time it will not update & Update Remote Fix does not fix the issue.
Also Snapper breaks as was happening before as well.
Will reinstall Garuda & see if it works.
Your issue is not related to the post iBolski shared, which is not related to this thread at all so this is an off-topic response to an off-topic response.
3 Likes
A post was merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)
A post was merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)
This topic is getting a lot of off-topic attention for some reason so I'll just close it down here since it is already solved.
Luckily it was an easy fix.
