System no longer booting properly

Support System Updates
1

Yesterday I updated my system via Pamac, mostly went as normal, other than it telling me at the end when one of the AUR packages failed that I couldn’t update due to some authentication issue, I don’t clearly remember what the error said, I thought little of it because a lot of my AUR packages give my trouble at this point.

I tried rebooting after the update, and after the GRUB screen I kept getting this “failed to load kernel modules” error. I tried going to fallback kernels, and no matter what I did, it kept happening.

I searched up the error and everyone kept saying I would need to try to boot from a live USB (After which the solutions become vague and confusing)

After some issues with my USB, I eventually got the machine to boot from the USB, but now I’m kinda lost on what to do next, each solution I find online is confusing and different and it’s hard to tell where to start.

Any help would be greatly appreciated.

2

They could be more clear here if we knew something about your system.

inxi -c0zv8

after you booted from your USB

lsblk -f
and/or
blkid
would also help

Next is to chroot -
how to do this will depend on whether your system is using BTRFS or ext4 as a file system and whether it is encrypted or not.

Generally:
you would chroot, use pacman (not pamac) to update the system,
pacman-mirrors -f
pacman -Syu
watch for the result
and, because of your kernel issues, (re)install a kernel
pacman -S linux612 (for example)
regenerate the initrd
mkinitcpio -P
and update the boot loader
update-grub
exit
to exit the chroot environment
and reboot

… this will not do anything re your AUR packages, but the base system should be o.k. then …

…
we need to see or know what you see or there can only be vague general recommendations like this

2 Likes
3

Well that first command spit out a lot, probably more than even I remember about my own PC, and I built it.

System:
  Kernel: 6.18.8-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_XFCE_2602 quiet
    systemd.show_status=1 splash apparmor=1 security=apparmor driver=nonfree
    nouveau.modeset=0 i915.modeset=1 radeon.modeset=1
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.51 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: Z170I PRO GAMING v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: 2002 date: 09/19/2016
Battery:
  Device-1: ps-controller-battery-90:fb:a6:dc:4b:b1 model: N/A serial: N/A
    charge: N/A status: full
  Device-2: wacom_battery_0 model: Wacom Intuos BT M serial: N/A
    charge: 100% status: discharging
Memory:
  System RAM: total: 32 GiB available: 31.28 GiB used: 3.44 GiB (11.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous size: 16 GiB
    speed: 3200 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CMK32GX4M2B3200C16 serial: N/A
  Device-2: DIMM_B1 type: DDR4 detail: synchronous size: 16 GiB
    speed: 3200 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CMK32GX4M2B3200C16 serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-6700 bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    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: 800 min/max: 800/4000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 bogomips: 54398
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  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: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort mitigation: TSX disabled
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ZOTAC driver: nvidia
    v: 575.64.05 alternate: nouveau,nova_core,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-11; EOL~2026-12-xx) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s ports: active: none off: DP-1,DP-2
    empty: DP-3,DVI-D-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1b81
    class-ID: 0300
  Display: x11 server: X.org v: 1.21.1.21 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 5120x1080 s-size: <missing: xdpyinfo>
  Monitor-1: DP-1 mapped: DP-0 note: disabled pos: right
    model: LG (GoldStar) ULTRAWIDE serial: <filter> built: 2018 res:
    mode: 2560x1080 hz: 60 scale: 100% (1) dpi: 97 gamma: 1.2 chroma: red:
    x: 0.651 y: 0.333 green: x: 0.306 y: 0.631 blue: x: 0.149 y: 0.059 white:
    x: 0.314 y: 0.329 size: 673x284mm (26.5x11.18") diag: 730mm (28.8")
    modes: 2560x1080, 1920x1080, 1680x1050, 1600x900, 1280x1024, 1152x864,
    1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480
  Monitor-2: DP-2 note: disabled pos: primary,left
    model: LG (GoldStar) ULTRAWIDE serial: <filter> built: 2018 res:
    mode: 2560x1080 hz: 60 scale: 100% (1) dpi: 97 gamma: 1.2 chroma: red:
    x: 0.651 y: 0.333 green: x: 0.306 y: 0.631 blue: x: 0.149 y: 0.059 white:
    x: 0.314 y: 0.329 size: 673x284mm (26.5x11.18") diag: 730mm (28.8")
    modes: 2560x1080, 1920x1080, 1680x1050, 1600x900, 1280x1024, 1152x864,
    1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast surfaceless: drv: nvidia x11: drv: nvidia
    inactive: gbm,wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64.05
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
    memory: 7.81 GiB
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA GP104 High Definition Audio vendor: ZOTAC
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-3: Focusrite-Novation Focusrite Scarlett 2i2 2nd Gen
    driver: snd-usb-audio type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
    bus-ID: 1-8:5 chip-ID: 1235:8202 class-ID: 0102
  API: ALSA v: k6.18.8-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
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: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  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: 05:00.0 chip-ID: 168c:003e class-ID: 0280 temp: 63.0 C
  IF: wlp5s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: ASUSTek Qualcomm Bluetooth 4.1 driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-13:8 chip-ID: 0b05:1825
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 4.79 TiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 2B7QCXE7 temp: 28.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD40EZRZ-00WN9B0 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A80 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: PNY model: USB 3.0 FD size: 14.46 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> fw-rev: PMAP
    scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Optical-1: /dev/sr0 vendor: ASUS model: DRW-24B1ST j rev: 1.01
    dev-links: cdrom
  Features: speed: 48 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 127.5 GiB fs: ext4 label: N/A
    uuid: 619a8be6-e8a8-4850-b966-911e934867f4
  ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 512 MiB fs: vfat label: N/A
    uuid: 21EC-C30C
  ID-3: /dev/sda1 maj-min: 8:1 size: 745.21 GiB fs: ext4 label: N/A
    uuid: 7869f405-4d65-4055-9923-1418549db768
  ID-4: /dev/sdb1 maj-min: 8:17 size: 96 GiB fs: swap label: N/A
    uuid: b3fd424e-fa6a-45e0-84e3-f85628280ba2
  ID-5: /dev/sdb2 maj-min: 8:18 size: 2.54 TiB fs: ext4 label: N/A
    uuid: 19a4d430-dfa4-4a27-b4aa-e0552dafca47
  ID-6: /dev/sdb3 maj-min: 8:19 size: 1 TiB fs: ext4 label: N/A
    uuid: 41ee3101-2ea9-495d-bc6b-ee820e99c907
  ID-7: /dev/sdc1 maj-min: 8:33 size: 5.03 GiB fs: iso9660
  ID-8: /dev/sdc2 maj-min: 8:34 size: 4 MiB fs: vfat label: MISO_EFI
    uuid: 7E34-5BA9
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-5:2 info: Wacom CTL-6100WL [Intuos BT (M)] type: HID
    driver: usbhid,wacom interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 056a:0378 class-ID: 0300
    serial: <filter>
  Device-2: 1-6:3 info: Sony DualShock 4 [CUH-ZCT1x] type: HID
    driver: playstation,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 054c:05c4 class-ID: 0300
  Device-3: 1-7:4 info: Cyber Power System CP1500 AVR UPS type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 2mA chip-ID: 0764:0501 class-ID: 0300
    serial: <filter>
  Device-4: 1-8:5 info: Focusrite-Novation Focusrite Scarlett 2i2 2nd Gen
    type: audio driver: snd-usb-audio interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 1235:8202 class-ID: 0102
  Device-5: 1-9:6 info: Glorious GMMK Pro ANSI type: keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 320f:5044 class-ID: 0300
  Device-6: 1-10:7 info: SteelSeries ApS Rival 3 type: mouse,HID
    driver: hid-generic,usbhid interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 400mA chip-ID: 1038:1824 class-ID: 0300
  Device-7: 1-13:8 info: ASUSTek Qualcomm Bluetooth 4.1 type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 0b05:1825 class-ID: e001
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-2:2 info: PNY USB 3.0 FD type: mass storage
    driver: usb-storage interfaces: 1 rev: 3.2 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 power: 504mA chip-ID: 154b:00ed class-ID: 0806
    serial: <filter>
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A gpu: nvidia temp: 42 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
  Packages: pm: pacman pkgs: 1132 libs: 317 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    2: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    3: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    4: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    5: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    6: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    7: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    8: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    9: https://mirror.dimensiondata.com/mirrors/manjaro.org/stable/$repo/$arch
    10: https://mirrors2.manjaro.org/stable/$repo/$arch
    11: https://manjaro.ynh.ovh/stable/$repo/$arch
    12: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    13: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    14: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    15: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    16: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    17: https://mirror.23m.com/manjaro/stable/$repo/$arch
    18: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    19: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    20: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
    21: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    22: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    23: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    24: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    25: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    26: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    27: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
    28: https://manjaro.syxpi.fr/manjaro/stable/$repo/$arch
    29: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    30: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    31: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    32: https://mirror.bakertelekom.fr/manjaro/stable/$repo/$arch
    33: https://manjaro.grena.ge/stable/$repo/$arch
    34: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    35: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    36: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    37: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    38: https://manjaro.nic.cz/stable/$repo/$arch
    39: https://mirror.mobinhost.com/manjaro/stable/$repo/$arch
    40: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    41: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    42: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    43: https://mirror.komelt.dev/manjaro/stable/$repo/$arch
    44: https://mirror.meowsmp.net/manjaro/stable/$repo/$arch
    45: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    46: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    47: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    48: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
    49: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    50: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
    51: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    52: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    53: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
    54: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    55: https://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    56: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    57: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    58: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    59: https://mirror.init7.net/manjaro/stable/$repo/$arch
    60: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    61: https://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    62: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    63: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    64: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    65: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    66: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    67: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    68: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    69: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    70: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    71: https://bd.mirror.vanehost.com/Manjaro/stable/$repo/$arch
    72: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    73: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    74: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    75: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/stable/$repo/$arch
    76: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    77: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    78: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    79: https://mirror.leitecastro.com/manjaro/stable/$repo/$arch
    80: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    81: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    82: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    83: https://manjaro.mirror.ac.za/stable/$repo/$arch
    84: https://mirror.nju.edu.cn/manjaro/stable/$repo/$arch
    85: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    86: https://mirrors.aliyun.com/manjaro/stable/$repo/$arch
    87: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    88: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    89: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    90: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    91: https://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    92: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    93: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    94: https://manjaro.kurdy.org/stable/$repo/$arch
    95: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    96: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
    97: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    98: https://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    99: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    100: https://mirrors.pku.edu.cn/manjaro/stable/$repo/$arch
    101: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    102: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    103: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    104: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    105: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    106: https://mirror.zetup.net/manjaro/stable/$repo/$arch
    107: https://ftp.riken.jp/Linux/manjaro/stable/$repo/$arch
    108: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    109: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    110: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    111: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    112: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
    113: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    114: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    115: https://linorg.usp.br/manjaro/stable/$repo/$arch
    116: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    117: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
    118: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    119: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    120: https://manjaro.mirror-services.net/pub/stable/$repo/$arch
    121: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    122: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    123: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    124: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    125: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 243
  1: cpu: 0.6% command: Xorg pid: 8833 mem: 101.4 MiB (0.3%)
  2: cpu: 0.4% command: xfdesktop pid: 9056 mem: 126.9 MiB (0.3%)
  3: cpu: 0.3% command: init pid: 1 mem: 15.2 MiB (0.0%)
  4: cpu: 0.3% command: gpg-agent pid: 1083 mem: 4.34 MiB (0.0%)
  5: cpu: 0.2% command: xfwm4 pid: 8966 mem: 131.0 MiB (0.4%)
  Memory top: 5 of 243
  1: mem: 131.0 MiB (0.4%) command: xfwm4 pid: 8966 cpu: 0.2%
  2: mem: 126.9 MiB (0.3%) command: xfdesktop pid: 9056 cpu: 0.4%
  3: mem: 101.4 MiB (0.3%) command: Xorg pid: 8833 cpu: 0.6%
  4: mem: 73.7 MiB (0.2%) command: xfce4-session pid: 8892 cpu: 0.0%
  5: mem: 66.5 MiB (0.2%) command: blueman-applet started-by: python
    pid: 9300 cpu: 0.1%
Info:
  Processes: 243 Power: uptime: 12m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.44 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 258
    default: graphical tool: systemctl
  Compilers: N/A Shell: Zsh v: 5.9 running-in: xfce4-terminal inxi: 3.3.40

The second command is pretty standard, reletive to my somewhat idiosyncratic setup. For context, this machine was built back when NVME drives were new, and expensive, so I put all my boot stuff on the NVME drive, and mounted my /home folder in the SATA SSD which was cheaper, and since thats where the bulk of my files would actually be, the way people used to do SATA SSD boot drives with HDD storage for their files/games back before that.

NAME FSTYPE FSVER LABEL             UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                                0   100% /run/miso/sfs/livefs
loop1
     squash 4.0                                                                0   100% /run/miso/sfs/mhwdfs
loop2
     squash 4.0                                                                0   100% /run/miso/sfs/desktopfs
loop3
     squash 4.0                                                                0   100% /run/miso/sfs/rootfs
sda                                                                                     
└─sda1
     ext4   1.0                     7869f405-4d65-4055-9923-1418549db768                
sdb                                                                                     
├─sdb1
│    swap   1                       b3fd424e-fa6a-45e0-84e3-f85628280ba2                
├─sdb2
│    ext4   1.0                     19a4d430-dfa4-4a27-b4aa-e0552dafca47                
└─sdb3
     ext4   1.0                     41ee3101-2ea9-495d-bc6b-ee820e99c907                
sdc  iso966 Jolie MANJARO_XFCE_2602 2026-02-06-11-06-10-00                     0   100% /run/miso/bootmnt
├─sdc1
│    iso966 Jolie MANJARO_XFCE_2602 2026-02-06-11-06-10-00                              
└─sdc2
     vfat   FAT12 MISO_EFI          7E34-5BA9                                           
sr0                                                                                     
nvme0n1
│                                                                                       
├─nvme0n1p1
│    ext4   1.0                     619a8be6-e8a8-4850-b966-911e934867f4                
└─nvme0n1p2
     vfat   FAT32                   21EC-C30C

Nothing complicated beyond that, EXT.4, no encryption.

chroot is something I don’t feel like I fully understand. is that like a way to log into the actual system while it’s not running, sorta like SSH into a Raspberry Pi? This is usually where I get confused

1 Like
4

No. A chroot still has you running the system that you booted from, but within the session of the chroot environment, the system thinks that its system drive is the one you’ve chroot’ed into. This enables you to use the package manager on the installed drive as if you were running natively off that system. It will also recognize the user accounts on the installed system when it comes to file ownership and permissions.

Certain things will however not work because they operate at a deeper level and therefore still have a reliance on the system you’ve chroot’ed from — e.g. things which require polling the running kernel, which will of course be the kernel of (in this case) the live USB session.

There was a polkit change a short while ago, which caused privilege escalation authentication issues with pamac and other such applications for people running an older kernel. Apparently one needs at a bare minimum a 6.6 LTS kernel, but the advice is to use 6.12 LTS, 6.18 LTS, or a later kernel.

That said, AUR packages should regularly be rebuilt. Some of your AUR packages may also no longer be in the AUR, in which case it is best to remove them.

It is possible that your filesystem got corrupted. Given that your system has — at least, if I’m reading you correctly — never been reinstalled, I presume that you’d still be using ext4 as the filesystem, and ext4 is quite susceptible to corruption from unclean shutdowns. Fixing this would require a repair from a live USB or CD/DVD, but without a chroot — as the matter of fact, the filesystem mustn’t even be mounted.

Another possibility — which would require a chroot — is that your system is in a partial upgrade state due to an interrupted or failed update procedure.

If it was the update that failed, here’s a procedure on how to fix that… :backhand_index_pointing_down:

4 Likes
5

You don’t need to fully understand it, but it certainly helps.
When you boot from your USB, where you put your ISO, you end up with a running system, which has got a file system.
The root of that file system is the directory / and every other is attached to it.
You can see that, for instance, with:
ls -hl /
or
ls /
or
tree -L 1 /

That is why each PATH is starting with /

chroot means: change root

When you chroot, you change the file system root from your current system, which is running from the ISO, to the other one on your hard disk, which, in your case, you cannot boot anymore.

I hope I could clarify the concept a bit.

4 Likes
6

Yes, but only within that shell session. The rest of the system is still running off the live USB.

3 Likes
7

OK so…this is a lot…I appreciate the explanations, and I think I might understand a little more about Chroot. The only question now for me is for my specific case, how do I put it into action? What should I be doing next to save my system?

In the live environment, in the file manager I can see all of my drives, so it seems like the file system SHOULD be intact. But yeah, I’ve been running this single install of Manjaro consistently since 2017. I don’t think it was an unclean shutdown though, it’s not like I pulled the plug on my computer or something, it’s frankly probably seen worse than this.

I’ll follow the steps in this guide that @Aragorn posted, then report back with the result

2 Likes
8

… not to confuse things, just as an addition:

You have two what probably are spinning disks
/dev/sda and /dev/sdb

sda with one ext4 partition
sdb with two ext4 partitions and one swap partition

and then an ssd (nvme) with one ext4 partition and what is likely the ESP (vfat file system)

Only you know which is which - but it is easy to figure out if you don’t know.
Just mount each partition and look at the contents.
On one of them there is /etc/fstab - this will tell you which partition goes where.

manjaro-chroot -a
may be all you need, it will likely do the job of “chrooting” for you correctly

2 Likes
9

So I followed that tutorial…and now when trying to reboot, theres no grub screen, it just goes to a blinking cursor and stays there indefinitely…Me thinks something went wrong…I followed it to the letter, and t seemed like everything ran like it was supposed to? But I guess not?

10

What is not in that tutorial is:
reinstalling a kernel and recreating the initrd for already installed kernels

Have a look at my first post here in the thread:

System no longer booting properly - #2 by Nachlese

… what I wrote after “Generally”

Did you do that?

(re)install linux618 instead of linux612 (which was the example)
or both of them …

If you are unsure - provide full output of each step
so we can tell where something might have not gone as it should have and why.

1 Like
11

Just tried what you said in “Generally”, no dice

I’ll go through the process again, and give you the outputs

For manjaro-chroot -a:

grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
==> Mounting (ManjaroLinux) [/dev/nvme0n1p1]
 --> mount: [/mnt]
 --> mount: [/mnt/home]
 --> mount: [/mnt/boot/efi]
 --> mount: [/mnt/media/Sync]
 --> mount: [/mnt/media/Backups]

For pacman -Syu (I assume you don’t care about the mirrors output)

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
warning: archlinux-keyring: local (20260206-1) is newer than core (20260107-2.0)
warning: libc++abi: ignoring package upgrade (14.0.6-1 => 21.1.6-1)
 there is nothing to do

For pacman -S linux618

resolving dependencies...
looking for conflicting packages...

Packages (1) linux618-6.18.8-1

Total Download Size:   144.64 MiB
Total Installed Size:  150.81 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 linux618-6.18.8-...   144.6 MiB  30.7 MiB/s 00:05 [######################] 100%
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) installing linux618                          [######################] 100%
Optional dependencies for linux618
    linux-firmware: firmware images needed for some devices [installed]
    scx-scheds: to use sched-ext schedulers
    wireless-regdb: to set the correct wireless channels of your country
    [installed]
ldconfig: /usr/lib/libndi.so.4 is not a symbolic link

:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux618.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.18-x86_64 -g /boot/initramfs-6.18-x86_64.img
==> Starting build: '6.18.8-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.18-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found linux image: /boot/vmlinuz-6.18-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.18-x86_64.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-x86_64.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

For mkinitcpio -P

==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: '5.10.248-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.10-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: '5.10.248-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [block]
==> 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'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.10-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.198-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: '5.15.198-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [block]
==> 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'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64.img
==> Starting build: '6.1.161-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
==> Starting build: '6.12.68-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux618.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.18-x86_64 -g /boot/initramfs-6.18-x86_64.img
==> Starting build: '6.18.8-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.18-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful

For update-grub

Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found linux image: /boot/vmlinuz-6.18-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.18-x86_64.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-x86_64.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

Unknown device type is a little concerning there at the end, otherwise I’m in above my head here

12

Everything looks completely normal and as it should.
You might glean some info from disabling the splash screen so that you can see the messages during boot (or just hit ESC after the boot menu)

Perhaps the system is booting but just the login screen not showing …
can you get to a TTY? (CTRL+ALT+F3 - or any Fx from 1 to 6)

Since there is NVIDIA graphics involved I’ll preliminary blame this :wink:
I have no experience with it but have too often read here about people having issues.
I do not have any further advice.

You have five different kernels installed.
Did you try with each one?

1 Like
13

Well, the cursor I get blinks in a very different way than it normally does, the cursor is bigger than normal like zoomed in, and it’s indented by a line. No idea if that is relevant information

I already have the splash screen disabled, it all basically blurs by, even on a machine this old.

The thing is, I’m not getting the normal Grub screen I am used to seeing that usually lets me pick kernels and so on. I WAS getting it initially, but ever since booting to the live environment, it’s been doing the big blinky cursor

I can try to see if I can access a TTY. See what works

Edit: Negative on the TTYs, no response

Yeah, I tried the older kernels back when I had access to Grub, now I haven’t even been able to try them

14

There is a package called install-grub.
It’s not present by default, I think.
I’d go into chroot again and install it and then run it.
Perhaps that will improve things - but it is just a guess.
It won’t make things worse, though.

2 Likes
15

So I just ran install-grub. I’m posting the output here incase it doesn’t work, for the sake of complete transparency

Grub will be installed on: EFI
Installing for x86_64-efi platform.
Installation finished. No error reported.
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found linux image: /boot/vmlinuz-6.18-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.18-x86_64.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-x86_64.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
Warning: GRUB bootloader at '/boot/efi/EFI/Manjaro' was updated.
Your booted entry '' is not the same as 'Manjaro'.
This may be a rescue ISO, but if not check your EFI boot priority.

Lets hope we don’t need this

16

Annnnnnd…so close…

So that DID fix the issue with Grub, so we have that back. TTYs are once again available as well, so I’d call that progress.

But we’re back to the old blinking cursor from before, not the huge one we had when Grub was shot. There was no kernel error either, it just goes straight to the tiny blinking cursor in the upper corner like before

This feels very fixable… I am just not sure what to do next

1 Like
17

It looks like an issue with your graphics (Nvidia) driver to me.
But that is speculation! -
And I can’t help with that because I do not have this kind of hardware and never had.
Zero experience.

There should be clues in the system logs
journalctl …

mhwd is the Manjaro tool to deal with that
is all I can say

1 Like
18

@Knightshousegames You could try booting with the Open Source Nouveau driver. Maybe that will get you back to a Graphical desktop.

1 Like
19

Well, when I’ve booted into the live environment, I used the Proprietary drivers, which I assume means the Nvidia drivers? On there it least it booted fine

@tracyanne How would I go about doing this to test it?

20

This will probably be the last comment from me here.

I certainly do not know.
All I can say is that there are a lot of threads here on the forum dealing with apparently similar issues.
Looking at the system logs
journalctl -b 0 …
for the current (or -b 1 for the last boot)
to maybe find pertinent information
would be what I’d try first.

… you have five kernels to choose from - have you tried all five with the same result?
(I’d reduce the amount to two or three at most … you are not, realistically, deciding between five choices on each boot …)

1 Like