Early boot shows error: /etc/abroot/abroot.json not found before /etc is mounted

[arvindautar]

Issue Description

After installing Vanilla OS 2 Orchid, I noticed several red/orange messages appearing during both boot and reboot.

One recurring message is:

could not read config file in /etc open /etc/abroot/abroot.json: no such file or directory

These messages appear early in the boot process. However, the system continues booting normally afterwards and the GNOME desktop starts successfully.

From discussion on the Vanilla OS Discord it seems this may happen because /etc has not yet been fully mounted when the check runs.

Even though the system works correctly, these messages appear in red/orange and can make it look like something is broken.

It may be helpful to either:

• delay this check until /etc is mounted, or

• suppress the warning if this situation is expected.

Steps to Reproduce

1. Install Vanilla OS 2 Orchid
2. Boot the system
3. Observe the boot messages
4. Red/orange messages about /etc/abroot/abroot.json appear

The same types of messages can also appear during reboot/shutdown when system services are stopping.

On what version of Vanilla OS this happens?

Vanilla OS 2 Orchid

Additional Information

The system boots successfully and GNOME starts normally, so this does not appear to break functionality.

Other warnings that appear during boot include for example:

• Landlock: Disabled but requested by user space
• Bluetooth: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported
• nvme nvme0: using unchecked data buffer

During reboot I also see messages such as:

Job user@1000.service/stop running

These may be normal systemd messages, but because they appear in red/orange they look like errors.

Screenshots of the boot and reboot messages are attached.