Stuck in emergency mode, without any update

noobToLinux · 30 July 2026 16:27

Hello. As the titles says, I am stuck in the emergency mode.

I have seen other posts about the same issue but happened after some system update, but that is not my case.

In my case, I started using manjaro as usual (and yesterday I had the system updated and had no issues).

I boot the PC as always.
I log in to Gmail on firefox, to GitHub.
I enter YouTube, the screen freeze.
I shutdown the PC (holding the power button).
I boot the PC again.
Spam F12 to select boot option (I always do).
Enter the Grub
Select Kernel 6.18 ( I also have 6.12 but I have the same issue)
Starts booting, appears those log messages, but at one point they fail.

I write the last logs since I can’t copy and paste:

[  OK  ] Reached target Basic System
[    **] A start job is running for File System Check on /dev/disk/by-uuid/some-id
[FAILED] Failed to start File System Check on "same_path as before"
See systemctl status systemd-fsck-root.service for details
[DEPEND] Dependency failed for /sysroot.
[DEPEND] Dependecy failed for Initrd Root File System
[DEPEND] Dependency failed for Mountpoints Configured in the Real Root.
[  OK  ] Stopped target Basic System
[  OK  ] Reached target Initrd File Systems
[  OK  ] Started Emergency Shell
[  OK  ] Reached target Emergency Mode
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, or "exit" to continue bootup.

Cannot open access to console, the root account is locked. See sulogin(8) man page for more details.

Press Enter to continue.

If I press enter it retrys the same, and happens again.

I have Linux Mint on USB to live, but I hadn’t tried anything with it cause I don’t know if it will break something or not.

Also, I hope it is not malware, since I barely install anything and I always double check everything I install. The most recent download was a pydantic python package and spyder IDE, but it was before the last system update.

Thanks in advance

BG405 · 30 July 2026 16:36

I’d certainly recommend getting the latest official Manjaro .ISO rather than trying to do repairs from a Debian/Ubuntu based distro. That way, you’ll have access to the manjaro-chroot tool

I also recommend this:

When you are in the chroot environment (manjaro-chroot -a should do this automagically) you’ll then be able to provide some System Info (inxi -zv8c0).

noobToLinux · 30 July 2026 16:59

Hello, and thanks for the reply, I will try it tomorrow if I can.

Just an update. I was on windows now, and enter a discord channel and the system froze again, idk if it was just a coincidence or the issue is related, I rebooted and try again and no issue this time.

The PC might be dusty and needs a proper cleanup. Do you think that could be the issue?

BG405 · 30 July 2026 17:09

This is a possibility so worth checking. I’d also suggest keeping an eye on the temperature sensors.

Teo · 30 July 2026 17:11

For a sudden freeze, the reason is hardware related. Overheating, overclocking, undervoltage, bad PSU, bad memory, could be pretty much anything. At least you can monitor the temperatures.

For not booting, the reason was the corrupt filesystem - either by the freeze or by the power cut.

journalctl |grep "manjaro systemd-fsck"

should tell you if the filesystem check was successful. It probably took one reboot to replay the journal but on the last successful reboot, after repairing you should see something like

Jul 30 17:16:03 manjaro systemd-fsck[157]: /dev/nvme0n1p5: clean, 1698248/9666560 files, 24479465/38638080 blocks

If you are on BTRFS it might be different, i do not know.

BG405 · 30 July 2026 17:16

@noobToLinux I’d also recommend this, for when you have your system back up and running:

This will help to prevent (further) corruption which can be caused by a forced power-off, assuming the Kernel is still “alive”.

noobToLinux · 30 July 2026 17:29

Is it repairable? Or I will need a full reinstall?

I will probably send it for a proper cleanup, before trying anything else.

BG405 · 30 July 2026 17:33

The OS should be repairable. If it turns out to be a hardware issue, that could be a different matter. I’d try running Live Manjaro session to see if that is stable, especially if it doesn’t turn out to be clogged fans/vents or degraded thermal paste on the CPU.

You could have a Terminal window open with e.g.:

watch -n10 sensors

… to keep an eye on things whilst you run tests.

Wollie · 30 July 2026 20:33

What partition is this, root or ESP - or something else?

Have you switched off Fast Startup in Windoze?

noobToLinux · 30 July 2026 21:07

How can I know the partition? I use the one that came with the installation by default, Efi for EFI,and the rest for everything else. Base on the path I would say it is root, but I don’t know,

Yes

dmt · 30 July 2026 22:27

noobToLinux:

[    **] A start job is running for File System Check on /dev/disk/by-uuid/some-id
[FAILED] Failed to start File System Check on "same_path as before"
See systemctl status systemd-fsck-root.service for details
[DEPEND] Dependency failed for /sysroot.
[DEPEND] Dependecy failed for Initrd Root File System

It does seem to be root.

You can check by booting up a live USB and using lsblk -fo +size, compare the UUIDs to figure out which partition the error mentions.

Whilst you’re there you can try to chroot, and run the command that the error message suggests along with inxi as @BG405 requested.

manjaro-chroot -a
inxi -zv8c
systemctl status systemd-fsck-root.service

Please post the output from those commands.

noobToLinux · 1 August 2026 12:30

It is the root partition EXT4 and the home is also there, no different partition for home.

inxi -zv8c

tty: ttyname error: No such device
System:
  Kernel: 6.18.18-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_KDE_2604 quiet systemd.show_status=1 splash driver=free
    nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
  Desktop: KDE Plasma v: ERR-101 tk: Qt v: N/A wm: kwin_wayland dm: N/A Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B560M DS3H V2 serial: N/A
    uuid: 035e02d8-04d3-055c-eb06-da0700080009 Firmware: UEFI vendor: American Megatrends LLC. v: F11
    date: 12/19/2023
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.48 GiB used: 1.91 GiB (12.3%)
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None max-module-size: 16 GiB note: est.
  Device-1: Controller0-ChannelA-DIMM0 type: no module installed
  Device-2: Controller0-ChannelA type: DDR4 detail: synchronous size: 8 GiB speed: 2133 MT/s
    volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK8GX4M1E3200C16 serial: N/A
  Device-3: Controller0-ChannelB-DIMM0 type: no module installed
  Device-4: Controller0-ChannelB type: DDR4 detail: synchronous size: 8 GiB speed: 2133 MT/s
    volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64 total: 64 manufacturer: Corsair
    part-no: CMK8GX4M1E3200C16 serial: N/A
PCI Slots:
  Slot: 0 type: PCIe status: in use info: J6B2 length: long volts: 3.3 bus-ID: 00:01.0 children:
    1: 01:00.0 class-ID: 0300 type: display 2: 01:00.1 class-ID: 0403 type: audio
  Slot: 1 type: PCIe status: in use info: J6B1 length: short volts: 3.3 bus-ID: 00:1c.3
  Slot: 2 type: PCIe status: in use info: J6D1 length: short volts: 3.3 bus-ID: 00:1c.4
  Slot: 3 type: PCIe status: in use info: J7B1 length: short volts: 3.3 bus-ID: 00:1c.5
  Slot: 4 type: PCIe status: in use info: J8B4 length: short volts: 3.3 bus-ID: 00:1c.6 children:
    1: 04:00.0 class-ID: 0403 type: audio
CPU:
  Info: model: Intel Core i7-10700F socket: U3E1 bits: 64 type: MT MCP arch: Comet Lake
    gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6 model-id: 0xA5 (165)
    stepping: 5 microcode: 0xF8
  Topology: cpus: 1x dies: 1 clusters: 8 cores: 8 threads: 16 tpc: 2 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB desc: 8x256 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 800 min/max: 800/4800 base/boost: 2772/4800 scaling: driver: intel_pstate
    governor: powersave volts: 0.8 V ext-clock: 100 MHz cores: 1: 800 2: 800 3: 800 4: 800 5: 800
    6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
    bogomips: 92796
  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 ibrs_enhanced ida intel_pt invpcid lahf_lm
    lm mca mce md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid
    pclmulqdq pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdrand rdseed rdtscp rep_good
    sdbg sep smap smep 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 mitigation: Microcode
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection mitigation: Aligned branch/return thunks
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: old_microcode status: Vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: Enhanced 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: Enhanced / Automatic IBRS; IBPB: conditional; PBRSB-eIBRS: SW
    sequence; BHI: SW loop, KVM: SW loop
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti GDDR6X] vendor: ASUSTeK driver: nouveau v: kernel
    non-free: 550-6xx.xx+ status: current (as of 2026-07) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2 bus-ID: 01:00.0
    chip-ID: 10de:24c9 class-ID: 0300
  Display: server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13 compositor: kwin_wayland driver:
    X: loaded: nvidia gpu: nouveau display-ID: :1
  Monitor-1: DP-2 model: ASUS XG32VC serial: <filter> built: 2021 res: 2560x1440 dpi: 93
    gamma: 1.2 chroma: red: x: 0.675 y: 0.310 green: x: 0.278 y: 0.659 blue: x: 0.153 y: 0.071 white:
    x: 0.314 y: 0.329 size: 697x392mm (27.44x15.43") diag: 800mm (31.5") ratio: 16:9
    modes: 2560x1440, 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x960, 1152x864, 1280x720,
    1440x576, 1024x768, 1440x480, 800x600, 720x576, 720x480, 640x480, 720x400
  API: EGL v: 1.5 platforms: device: 0 drv: zink device: 1 drv: swrast gbm: drv: zink
    surfaceless: drv: zink inactive: wayland,x11
  API: OpenGL v: 4.6 vendor: mesa v: 26.1.5-arch1.1 note: incomplete (EGL sourced) renderer: zink
    Vulkan 1.4(NVIDIA GeForce RTX 3060 Ti (NVK GA104) (MESA_NVK)), llvmpipe (LLVM 22.1.8 256 bits)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: nvidia-settings,nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
    chip-ID: 8086:f0c8 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1
    chip-ID: 10de:228b class-ID: 0403
  Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series BlasterX AE-5
    Plus] driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0
    chip-ID: 1102:0012 class-ID: 0403
  API: ALSA v: k6.18.18-1-MANJARO status: kernel-api with: aoss type: oss-emulator
    tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.8 status: n/a (root, process) 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: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 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
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.32 TiB used: 290.48 GiB (12.2%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD Blue SN570 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 234100WD temp: 38.9 C
  SMART: yes health: PASSED on: 1y 18d 5h cycles: 1,647 read-units: 46,471,779 [23.7 TB]
    written-units: 26,234,157 [13.4 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZRX-00L4HB0 family: Green
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: HDD
    rpm: 5400 serial: <filter> fw-rev: 1A01 temp: 27 C
  SMART: yes state: enabled health: PASSED on: 3y 69d 7h cycles: 4122
  ID-3: /dev/sdb maj-min: 8:16 vendor: KUIJIA model: Dahua T70 PSSD size: 953.87 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
    sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 2201 drive-rev: W0222A0 temp: 31 C
  SMART: yes state: enabled health: PASSED on: 128d 6h cycles: 529 read: 637.5 MiB
    written: 157.7 MiB
  ID-4: /dev/sdc maj-min: 8:32 vendor: SanDisk model: USB 3.2Gen1 size: 28.67 GiB block-size:
    physical: 512 B logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 mode: 2.0 tech: N/A
    serial: <filter> fw-rev: 1.00
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 936.54 GiB size: 920.77 GiB (98.32%) used: 290.48 GiB (31.5%) fs: ext4
    block-size: 4096 B dev: /dev/sdb2 maj-min: 8:18 label: N/A
    uuid: 2095aee5-6cb4-4d8e-8760-f3054e01d1c4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 328 KiB (0.1%) fs: vfat
    block-size: 512 B dev: /dev/sdb1 maj-min: 8:17 label: N/A uuid: 2A1A-9607
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/dm-0 maj-min: 253:0 mapped: ventoy size: 5.28 GiB fs: N/A label: MANJARO_KDE_2604
    uuid: 2026-03-27-22-39-34-00
  ID-2: /dev/dm-1 maj-min: 8:33 mapped: sdc1 size: 28.64 GiB fs: exfat label: N/A uuid: N/A
  ID-3: /dev/nvme0n1p1 maj-min: 259:1 size: 100 MiB fs: fat (32 bit) label: N/A uuid: 524C-0544
  ID-4: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: N/A label: N/A uuid: N/A
  ID-5: /dev/nvme0n1p3 maj-min: 259:3 size: 465.14 GiB fs: ntfs label: Sistema M.2
    uuid: 5EC84CB3C84C8AEB
  ID-6: /dev/nvme0n1p4 maj-min: 259:4 size: 522 MiB fs: ntfs label: N/A uuid: 1E44681E4467F745
  ID-7: /dev/sda1 maj-min: 8:1 size: 931.51 GiB fs: ntfs label: Almacenamiento HDD
    uuid: FEB8CE9AB8CE50B7
  ID-8: /dev/sdb3 maj-min: 8:19 size: 17.03 GiB fs: swap label: swap
    uuid: 8a45410f-0f83-43b6-bdf6-25c8242204f4
  ID-9: /dev/sdc1 maj-min: 8:33 size: 28.64 GiB fs: exfat label: Ventoy uuid: B920-B905
  ID-10: /dev/sdc2 maj-min: 8:34 size: 32 MiB fs: N/A label: VTOYEFI uuid: 1998-3510
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-7:2 info: Holtek Keyboard 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: 100mA
    chip-ID: 04d9:a096 class-ID: 0300
  Device-2: 1-8:3 info: HP OMEN Reactor type: mouse,HID driver: hid-generic,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 200mA chip-ID: 03f0:2041
    class-ID: 0300
  Hub-2: 1-9:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-9.2:6 info: SanDisk 3.2Gen1 type: mass storage driver: usb-storage interfaces: 1
    rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 224mA chip-ID: 0781:55a3
    class-ID: 0806 serial: <filter>
  Device-2: 1-11:5 info: Integrated Express RGB LED Controller 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: 100mA chip-ID: 048d:5702 class-ID: 0300
  Hub-3: 2-0:1 info: super-speed hub ports: 6 rev: 3.1 speed: 20 Gb/s (2.33 GiB/s) lanes: 2
    mode: 3.2 gen-2x2 chip-ID: 1d6b:0003 class-ID: 0900
  Device-1: 2-1:2 info: JMicron / USA PSSD-T70 type: mass storage driver: uas interfaces: 1
    rev: 3.2 speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 896mA chip-ID: 152d:0580
    class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 40.0 C mobo: 33.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1609 libs: 400 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https: //ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https: //ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    3: https: //muug.ca/mirror/manjaro/stable/$repo/$arch
    4: https: //mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    5: https: //manjaro.repo.cure.edu.uy/stable/$repo/$arch
    6: https: //ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 330
  1: cpu: 1.0% command: kwin_wayland pid: 1928 mem: 203.3 MiB (1.2%)
  2: cpu: 0.9% command: dolphin pid: 4456 mem: 140.6 MiB (0.8%)
  3: cpu: 0.8% command: plasmashell pid: 2126 mem: 369.8 MiB (2.3%)
  4: cpu: 0.5% command: init pid: 1 mem: 14.3 MiB (0.0%)
  5: cpu: 0.4% command: [kworker/u64:5-events_unbound] pid: 177 mem: 0.00 MiB (0.0%)
  Memory top: 5 of 330
  1: mem: 369.8 MiB (2.3%) command: plasmashell pid: 2126 cpu: 0.8%
  2: mem: 203.3 MiB (1.2%) command: kwin_wayland pid: 1928 cpu: 1.0%
  3: mem: 140.6 MiB (0.8%) command: dolphin pid: 4456 cpu: 0.9%
  4: mem: 132.3 MiB (0.8%) command: yakuake pid: 2261 cpu: 0.0%
  5: mem: 127.7 MiB (0.8%) command: konsole pid: 4197 cpu: 0.2%
Info:
  Processes: 330 Power: uptime: 7m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6.06 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 261
    default: graphical tool: systemctl
  Compilers: N/A Client: systemd inxi: 3.3.41

systemctl status systemd-fsck-root.service

Running in chroot, ignoring command 'status'

journalctl -xb

-- No entries --

journalctl | grep manjaro systemd-fsck

This was the last log, yesterday when this happened, but there are more like this on previous date, almost the same, different numbers.

Jul 30 16:26:27 manjaro systemd-fsck[296]: /dev/sdb2: clean, 1688189/61382656 files, 80270738/245508908 blocks

I fixed it by using the command fsck.ext4 -f \path\to\ext4\partition and replying y to all.

Everything seems normal now.

In case you have the same issue:

From Live USB, make sure that the filesystem is unmounted sudo umount /path/to/partition. If you are in chroot, it is mounted type exit to exit from chroot.
If the filesystem is not ext4, the command would change.
fsck is a script that checks the filesystem and fixes errors it may find.

Mod edit: Consecutive posts merged.