Universal BlueUB
Universal Blue•4mo ago
Droopy Druchii

System D issues

I was getting a bunch of errors related to system d... I consulted a few AIs and they suggested me this fix. im not sure if its ideal, if it isnt, please tell me>

---

Problem: Root Overlay Mount Conflict


Symptoms


  • systemd-remount-fs.service failed on boot with errors like:
  fsconfig: overlay: No changes allowed in reconfigure

  • This prevented proper remount of 
    /
     and caused warnings in logs.
### Root Cause

  • OSTree mounts 
    /
     as an overlay filesystem (read-only base + writable upper layer).
  • Your 
    /etc/fstab
     had this line:
UUID=fd80e458-fc81-4835-a4b0-c52e748550c6 / btrfs subvol=root,...,ro 0 0


  • Conflict: fstab requested a read-only mount (ro), but OSTree wanted read-write (rw).
  • Result: systemd could not remount 
    /
    , leading to errors.
---

Fix Applied


  1. Comment out the root line in 
    /etc/fstab
#UUID=fd80e458-fc81-4835-a4b0-c52e748550c6 / btrfs subvol=root,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2,ro 0 0


  • Prevents systemd from trying to remount `/` with conflicting options.
  • **Set correct OSTree kernel arguments**
sudo ostree admin kargs --replace=rootflags=subvol=root
sudo rpm-ostree kargs --append=rootflags=subvol=root,noatime,lazytime,commit=120,discard=async,compress-force=zstd:1,space_cache=v2


  • Ensures the root overlay mounts **read-write** with proper BTRFS options.
  • **Reboot and verify**
mount | grep ' / '


  • Confirms that 
    /
     is mounted via composefs overlay correctly.
---

Outcome


  • systemd-remount-fs.service no longer fails.
  • Root filesystem is stable and properly mounted as overlay with read-write upper layer.
  • Compatible with future OSTree updates.
---
Was this page helpful?