(2023-11-03) x86_64 GNU/Linux

I installed Debian testing (without desktop or gnome).
then I installed overlayroot and rebooted
in grub I modified the line with 'e', I added overlayroot=tmpfs then F10

on startup, errors are displayed:
systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and
Kernel filesystems.
and when I login: the file system is read-only

I've done the same procedure with Debian 12 stable, it works fine: the
filesystem is read/write with an overlay: the disk is RO with a RW tmpfs.

Thanks

Translated from :

Paquet : overlayroot
Version : 0.18.debian13
Debian version : testing, téléchargée le 27/11/2023
uname -a : Linux Debian 6.5.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian
6.5.10-1 (2023-11-03) x86_64 GNU/Linux

J'ai installé Debian testing (sans desktop ni gnome).
puis j'ai installé overlayroot et redémarré
dans grub j'ai modifié la ligne avec 'e', j'ai ajouté overlayroot=tmpfs
puis F10

au démarrage des erreurs s'affichent :
systemd[1] : Failed to start systemd-remount-fs.service - Remount Root and
Kernel filesystems.
et lorsque je me connecte : le système de fichier est en lecture seul

J'ai effectué la même procédure avec Debian 12 stable, ça fonctionne
correctement : le système de fichiers est en lecture/écriture avec un
overlay : le disque en RO et un tmpfs en RW.

Merci

Overlayroot is still broken in trixie right before stable.


I have installed fresh on a thinkpad and in a kvm vm and went to install
overlayroot and when activating it fails

If I have it has tmpfs it just boots to a readonly /.    If I try to use
a device for the overlay everything fails and overlayroot is not engaged
at all.

from:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/2042034
overlayroot does not work with Linux 6.5
I found that one of the things that the initramfs script does is to add and
check for a kernel parameter, specifically that "ro" is present;

There is a bunch of discussion:
https://forums.debian.net/viewtopic.php?t=164015

For my use, I switched ro to rw and what I need works as expected.  I have
not looked into how or why, so this may not work for you.

Hello,

This is the usual setup - the kernel mounts read-only so the rootfs can
be fscked.  Then, it's remounted read-write later in the boot process.

Based on the comments, overlayroot's checking for ro to preserve other
software's assumptions about this sequence.

I'm not familiar with overlayroot, but our package is very out of date.
There are many bugfixes since 0.18, and very recent updates for dracut
support (which is now used in some of the cloud image builds).

I notice that you're listed in the changelog as having contributed - are
you able to test a new upstream release?

Thanks,
Ross