The Issue : Failed Remount Root and Kernel File Systems

[ghoster]

I stated see below message since the new update, started see when booting system and shut down, [Failed]

Followed by more issue, I thought I did something wrong I did do a reset, will didnt help, iso didnt work! many issues later I come seek help here! I have over follow of info below… sorry

The Issue : Failed Remount Root and Kernel File Systems

> sudo systemctl --failed

UNIT LOAD ACTIVE SUB DESCRIPTION
**● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems**

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

> sudo journalctl -p 3 -xb

– Journal begins at Sun 2021-11-21 12:39:46 GMT, ends at Sun 2021-11-21 12:48:33 GMT. –

Nov 21 12:39:46 Manjaro kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.SPT0._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
Nov 21 12:39:46 Manjaro kernel: ACPI Error: Aborting method \_SB.PCI0.SAT1.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Nov 21 12:39:46 Manjaro kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.SPT0._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
Nov 21 12:39:46 Manjaro kernel: ACPI Error: Aborting method \_SB.PCI0.SAT1.SPT0._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Nov 21 12:39:46 Manjaro kernel: BTRFS error (device nvme0n1p1): cannot disable free space tree
Nov 21 12:39:46 Manjaro systemd[1]: Failed to start Remount Root and Kernel File Systems.
Nov 21 12:39:46 Manjaro systemd-remount-fs[329]: /usr/bin/mount for / exited with exit status 32.
Nov 21 12:40:00 Manjaro kernel: nouveau 0000:06:00.0: bus: MMIO write of 800000e0 FAULT at 10eb14 [ PRIVRING ]
Nov 21 12:40:00 Manjaro kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Nov 21 12:40:00 Manjaro kernel: EDAC sbridge: Couldn't find mci handler
Nov 21 12:40:00 Manjaro kernel: EDAC sbridge: Failed to register device with error -19.
Nov 21 12:40:00 Manjaro kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled
Nov 21 12:40:00 Manjaro kernel: EDAC sbridge: Couldn't find mci handler

**

at /etc/fstab

**

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /              btrfs   subvol=/@,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /home          btrfs   subvol=/@home,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /var/cache     btrfs   subvol=/@cache,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /var/log       btrfs   subvol=/@log,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0

**

blkid

**

/dev/nvme0n1p1: UUID="f59c48d5-4494-4870-81c1-9485b9691dab" UUID_SUB="820147c4-b5b0-437d-87db-c3d08c3e5a95" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="556ef186-01"
/dev/sdb4: LABEL="rpool" UUID="17353626452047158595" UUID_SUB="17711165529915024653" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="32d9cc14-0e72-a342-805d-ab6dd7ee6d1a"
/dev/sdb2: UUID="53b69b6e-ba67-4b22-b913-06d46619a140" TYPE="swap" PARTUUID="d7866eba-0193-e847-bfe2-c067b7e7ff9b"
/dev/sdb3: LABEL="bpool" UUID="7997028952633508358" UUID_SUB="10587871280532787431" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="9836ddfc-ac21-be46-93cb-57a8048076bb"
/dev/sdb1: UUID="D046-A8E8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="7b5e9a29-0c27-4d5c-9acc-c38cc7593019"
/dev/sda2: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="BD03-E980" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Microsoft reserved partition" PARTUUID="d67c2d34-496e-11ec-b89e-243c200e1a4f"
/dev/sda3: LABEL="Software" BLOCK_SIZE="512" UUID="DA88AE1988ADF3E3" TYPE="ntfs" PARTLABEL="LDM data partition" PARTUUID="d67c2d38-496e-11ec-b89e-243c200e1a4f"

[papajoke]

nice title…
read 50 lines to understand if I can help you or not : not for me

[HowTo] Increase your chances of receiving help

Difficulty: ★☆☆☆☆ Strong of its many members, the Manjaro support forum can provide you help whenever you have an issue with your Manjaro installation. But in order to work efficiently, we shall also ask you to commit to a few things. Keep calm and read First some basics: whenever you need to troubleshoot, chances are the solution is already under your nose. Find error messages When an applications crashes, and sometimes when it misbehaves, it very often prints an error message somewhere. …

[Mirdarthos]

Also

How to provide good information

Welcome to Manjaro! To allow all of us helpful people on this forum TO HELP YOU, we need some basic information about your system. This probably means you described the symptoms of your problem, but now we need some more information to know where the origin of your issue is exactly. Someone else probably linked you to this tutorial, so if you’re reading this in response to a question, please click the link above this text to bring you to the full and unabridged text of the tutorial…

[ghoster]

Thanks for the Kind words! much helpful!

[Fall66]

My system (with btrfs on / and luks crypted /home) got the same error messages on boot. Hopefully, i can boot it and log in despite the error messages.

[ghoster]

Hello, whenever I start up the system stuck on this message about 10-30 seconds and also when I shut down the pc as well.

I started to have this issue since the newer update, I try reinstalling os didnt help I went into systemd, try to start the systemd-remount-fs.service… didnt work either.

I could use any help, thanks in advance

Issue:
● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems

sudo systemctl --failed

UNIT                       LOAD   ACTIVE SUB    DESCRIPTION                         
● systemd-remount-fs.service loaded failed failed Remount Root and Kernel File Systems

at /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /              btrfs   subvol=/@,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /home          btrfs   subvol=/@home,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /var/cache     btrfs   subvol=/@cache,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0
UUID=f59c48d5-4494-4870-81c1-9485b9691dab /var/log       btrfs   subvol=/@log,defaults,noatime,space_cache,autodefrag,compress=zstd 0 0

[Wollie]

Why don’t you have an ESP? Are you booting in BIOS mode?

[ghoster]

Yeah, I use BIOS mode

[linux-aarhus]

@ghoster

BTRFS error (device nvme0n1p1): cannot disable free space tree

Your issues start there.

You have an error in the filesystem - I don’t know what, where or why - I don’t trust btrfs.

[ghoster]

I thought btrfs faster, I have been using for last few weeks, there were no issue… what would you recommend? at this strange I would try anything, i been hit with system panic!.. I tried the TTY T/S didnt help either…

[linux-aarhus]

I ran scared and screaming away after a rendevouz with btrfs 5 years ago so my advice may not be the best. I haven’t felt comfortable with btrfs since.

I have played with it using test equipment - nothing serious though. I use ext4 and f2fs.

I don’t think you can get hurt by booting a live iso then from a terminal run

fsck /dev/nvme0n1p1

[ghoster]

Ill give that a go

[pgennere]

I had the same problem (ssd sata) with the message “BTRFS error (device nvme0n1p1): cannot disable free space tree” . Could you try this command line ?. : # btrfs check --clear-space-cache v2 /dev/sda2 . You must change the device path (your device nvme) AND use to a live iso manjaro (file system must be umount). In my problem, it was a new install of manjaro kde 21.2pre1 .
MANpage btrfs check --clear-space-cache : completely wipe all free space cache of given typeFor free space cache v1, the clear_cache kernel mount option only rebuilds the free space cache for block groups that aremodified while the filesystem is mounted with that option. Thus, using this option with v1 makes it possible to actually clearthe entire free space cache.For free space cache v2, the clear_cache kernel mount option destroys the entire free space cache. This option, with v2 providesan alternative method of clearing the free space cache that doesn’t require mounting the filesystem