Re: Prerequisites for systemd.volatile=yes

[Shreenidhi Shedi <shreenidhi.shedi@xxxxxxxxxxxx>]

Hi All,

Any inputs on this?

--

Shedi

On Mon, Apr 15, 2024 at 7:15 PM Shreenidhi Shedi <shreenidhi.shedi@xxxxxxxxxxxx> wrote:

Hi All,

I'm trying to use volatile root feature for the first time.

This is my /etc/fstab:

```

#system mnt-pt type options dump fsck
PARTUUID=ad7ab716-2c0a-4dbe-9a28-06dc8bd0383b / ext4 defaults,barrier,noatime,data="" 1 1

```

And systemd grub configs are:

systemd_cmdline=net.ifnames=0 plymouth.enable=0 systemd.unified_cgroup_hierarchy=yes systemd.volatile=yes

Finally, kernel command is:

BOOT_IMAGE=/vmlinuz-6.1.83-1.ph5 root=PARTUUID=ad7ab716-2c0a-4dbe-9a28-06dc8bd0383b init=/lib/systemd/systemd ro loglevel=3 quiet net.ifnames=0 plymouth.enable=0 systemd.unified_cgroup_hierarchy=yes systemd.volatile=yes

And I regenerated initrd using `mkinitrd`

But when I rebooted my vm, it is going to emergency shell and shows /run/initramfs/rdsosreport.txt and I'm not able to get into emergency shell either, it just keeps looping in press Ctrl-D or enter root password prompt and entering root password or pressing Ctrl-D just prompts the same thing again.

Can someone assist me on what are the prerequisites for enabling volatile root?

- Kernel configs to be enabled

- File system types supported

- Kernel command line args needed

If someone can provide a step by step procedure on how to see this feature in action, it would really help.

--

Shedi