System continues to be really unstable

Support
1

I posted recently about issues I had with Manjaro where I ended up suffering some data loss because Manjaro failed mid-update (of Vivaldi browser). How that started was that after a reboot I got the message that there was a failure to mount UUID=xxx on real root, and i was dropped into an emergency shell.

Following the advice in that thread, I installed Manjaro on another nvme drive, but the instability has persisted. It would occasionally boot up competely normal, I was able to add software and customise KDE, no issues, but every reboot was a lottery as to whether it would work or not. Well, I just tried to reboot, and after logging in, Manjaro crashed. Now I’m straight back at the emergency shell, with a failure to mount real root.

I had previously updated to latest (6.17) kernel and used it with (seemingly) no issues. I can get into Grub, but i get the same result whether i pick 6.17, 6.17-fallback, 6,12 (the LTS kernel that came with the installer) or 6.12-fallback.

I’ve loaded up the live USB (and there have been times these last couple of days when I couldn’t even load up the live USB!), but manjaro-chroot -a is failing.

output of dmesg -T --level=emerg,alert,crit,err,warn after the failed chroot attempt:

[Sat Dec  6 18:52:36 2025] hub 12-0:1.0: config failed, hub doesn't have any ports! (err -19)
[Sat Dec  6 18:52:39 2025] nvme nvme1: missing or invalid SUBNQN field.
[Sat Dec  6 18:52:39 2025] nouveau 0000:01:00.0: unknown chipset (1b2000a1)
[Sat Dec  6 18:52:42 2025] EXT4-fs (nvme0n1p2): ext4_check_descriptors: Block bitmap for group 192 not in group (block 3979272452257567583)!
[Sat Dec  6 18:52:42 2025] EXT4-fs (nvme0n1p2): group descriptors corrupted!
[Sat Dec  6 18:52:42 2025] EXT4-fs error (device nvme0n1p3): ext4_mark_recovery_complete:6246: comm mount: Orphan file not empty on read-only fs.
[Sat Dec  6 18:52:42 2025] EXT4-fs (nvme0n1p3): mount failed
[Sat Dec  6 18:52:43 2025] FAT-fs (sda): bogus number of reserved sectors
[Sat Dec  6 18:52:43 2025] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (sda): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] FAT-fs (nvme2n1): bogus number of reserved sectors
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme2n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme2n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme2n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] FAT-fs (nvme1n1): bogus number of reserved sectors
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme1n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme1n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme1n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] FAT-fs (nvme0n1): bogus number of reserved sectors
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme0n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme0n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme0n1): VFS: Can't find ext4 filesystem
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme0n1p2): ext4_check_descriptors: Block bitmap for group 192 not in group (block 3979272452257567583)!
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme0n1p2): group descriptors corrupted!
[Sat Dec  6 18:52:43 2025] EXT4-fs error (device nvme0n1p3): ext4_mark_recovery_complete:6246: comm mount: Orphan file not empty on read-only fs.
[Sat Dec  6 18:52:43 2025] EXT4-fs (nvme0n1p3): mount failed
[Sat Dec  6 18:52:44 2025] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[Sat Dec  6 18:52:49 2025] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[Sat Dec  6 18:53:11 2025] nvme nvme0: using unchecked data buffer
[Sat Dec  6 18:53:11 2025] block nvme0n1: No UUID available providing old NGUID
[Sat Dec  6 18:53:12 2025] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[Sat Dec  6 18:53:15 2025] usb 3-9.4: Failed to query (GET_RES) UVC control 10 on unit 2: 0 (exp. 2).
[Sat Dec  6 18:53:15 2025] usb 3-9.4: Failed to query (GET_RES) UVC control 10 on unit 2: 0 (exp. 2).
[Sat Dec  6 18:59:39 2025] EXT4-fs (nvme0n1p2): ext4_check_descriptors: Block bitmap for group 192 not in group (block 3979272452257567583)!
[Sat Dec  6 18:59:39 2025] EXT4-fs (nvme0n1p2): group descriptors corrupted!
[Sat Dec  6 19:01:52 2025] EXT4-fs (nvme0n1p2): ext4_check_descriptors: Block bitmap for group 192 not in group (block 3979272452257567583)!
[Sat Dec  6 19:01:52 2025] EXT4-fs (nvme0n1p2): group descriptors corrupted!

Inxi output (keep in mind this is from the live usb)

System:
  Kernel: 6.12.48-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=gb
    tz=Europe/London misobasedir=manjaro misolabel=MANJARO_KDE_25010 quiet
    systemd.show_status=1 splash driver=free nouveau.modeset=1 i915.modeset=1
    radeon.modeset=1
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.18.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: X870E Nova WiFi
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: 3.50 date: 09/18/2025
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 64 GiB available: 60.41 GiB used: 4.37 GiB (7.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: no module installed
  Device-2: Channel-A DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 32 GiB speed: spec: 4800 MT/s actual: 6000 MT/s
    volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CMK64GX5M2B6000Z30 serial: N/A
  Device-3: Channel-B DIMM 0 type: no module installed
  Device-4: Channel-B DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 32 GiB speed: spec: 4800 MT/s actual: 6000 MT/s
    volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: Corsair part-no: CMK64GX5M2B6000Z30 serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 9800X3D bits: 64 type: MT MCP arch: Zen 5 gen: 5
    level: v4 note: check built: 2024+ process: TSMC n4 (4nm) family: 0x1A (26)
    model-id: 0x44 (68) stepping: 0 microcode: 0xB404032
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
    desc: 8x1024 KiB L3: 96 MiB desc: 1x96 MiB
  Speed (MHz): avg: 601 min/max: 600/5269 boost: enabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 601 2: 601 3: 601
    4: 601 5: 601 6: 601 7: 601 8: 601 9: 601 10: 601 11: 601 12: 601 13: 601
    14: 601 15: 601 16: 601 bogomips: 150162
  Flags: 3dnowprefetch abm adx aes amd_lbr_pmc_freeze amd_lbr_v2 aperfmperf
    apic arat avic avx avx2 avx512_bf16 avx512_bitalg avx512_vbmi2
    avx512_vnni avx512_vp2intersect avx512_vpopcntdq avx512bw avx512cd
    avx512dq avx512f avx512ifma avx512vbmi avx512vl avx_vnni bmi1 bmi2 bpext
    bus_lock_detect cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov
    cmp_legacy constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local
    cqm_mbm_total cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists erms
    extapic extd_apicid f16c flush_l1d flushbyasid fma fpu fsgsbase fsrm fxsr
    fxsr_opt gfni ht hw_pstate ibpb ibrs ibrs_enhanced ibs invpcid irperf
    lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    movdir64b movdiri msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx ospke
    osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb perfctr_core
    perfctr_llc perfctr_nb perfmon_v2 pfthreshold pge pku pni popcnt pse
    pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp
    succor svm svm_lock syscall tce topoext tsc tsc_adjust tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vnmi vpclmulqdq wbnoinvd wdt x2avic xgetbv1 xsave xsavec xsaveerptr
    xsaveopt xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Enhanced / Automatic IBRS; IBPB:
    conditional; STIBP: always-on; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace

Genuinely not sure how to fix this and get to a stable system. Last time I got here, I ran fsck on the root partition, which ended up messing up my home partition (I don’t know how that works).

Additional info - I have an NVIDIA GPU (I ran mhwd -a PCI nonfree 0300) and also have an AMD iGPU - I do notice AMDGPU a lot in the journalctl logs, which, I’m not sure why it’s being used?

Please do share your thoughts on how I can rescue my current setup, and also diagnose and fix the underlying general instability?

2

Hi @nihalfm,

I read the post you mentioned and you did not boot on the live environment and without mounting the partitions. May be you can list them and run the following command:

fsck - y /dev/nvme0n1p2

You can find a similar post with the same problem with a quick search on the web, from many others I choose this:

‘[SOLVED] Emergency mode-ext4 checksum and group descriptions corrupted / Newbie Corner / Arch Linux Forums

Hope it helps, regards

3

Does / on that NVMe drive have a btrfs filesystem?

manjaro-chroot does not work with a btrfs filesystem – you would need to enter a chroot environment manually.

I imagine someone might have given you the following link in the previous topic you mentioned:

This shows the general procedure to follow in order to recover from an incomplete or interrupted update.

More importantly, it also gives the general procedure to enter a chroot environment manually when the filesystem is btrfs.

Once in that environment, one can perform actions necessary to ensure an update completes successfully.

Additionally, as chroot inserts you directly into your system as the Super User (root), you are able to perform most other general maintenance and repair procedures that may be necessary.

Your Home directory heirarchy is by default a directory below the root / level – hence /home. One can choose to have /home on a separate partition, but this must usually be done manually during Manjaro installation – the manual partitioning method must be used.

This begins to look like a hardware issue, although it might be that your hardware is simply *too new for the latest kernels.

General Linux compatibility doesn’t seem to be an issue:

https://linux-hardware.org/?id=board:asrock-x870e-nova-wifi

I note that your inxi output is incomplete. Particularly conspicuous by it’s absence is the entire section devoted to storage. Note that inxi -zv8 would have shown that regardless of being run from the Live environment.

Please provide the output of;

lsblk -af

In closing, perhaps check:

  • that your SATA cables are properly and securely connected
  • that your RAM modules are likewise securely seated in their slots
  • that your power supply (PSU) sufficient for all connected devices
  • that your BIOS is properly configured

You may find your mainboard manuals useful in determining whether something is misconfigured:

Regards.

2 Likes
4

From the output you present - it looks very much like an issue with the system itself.

Your dmesg output exhibiting multiple disk failures

It is impossible to deduce what or why - it looks very much like the communication with your disk devices are failing

  • sda
  • nvme2n1
  • nvme1n1
  • nvme0n1

This points toward the system’s main board - either configuration or it is failing or outright flawed.

One can only speculate

  • is the APU / CPU is undervolted?
  • is the PSU faulty, causing failure?
  • does the PSU provide enough juice to the system?
  • is there a bad soldering point causing power fluctuations?

This could be anything… almost impossible to troubleshoot in an online forum.

From the AMD web it looks like there is graphical capabilities builtin which makes it possible to troubleshoot without the Nvidia device.

This is only suggestions - ideas - brainstorming - read your board manual

  • Disassemble the system
  • Removing all disks and the Nvidia GPU
  • Inspect the main board closely for visible defects
  • Check the CPU seating (if possible)
  • Check all connectors to the mainboard
  • Boot the system from a live USB using the onboard GPU
  • Test your ram one by one in each slot
  • Test the nvme disks one by one in each slot

You may try a rescue ISO or Plasma with kernel 6.18 from my private ISO repo on manjaro.dk

2 Likes