[systemd-devel] systemd-repart with volatile root

[Xogium]

Is anyone able to help with this issue ? Is this even supported/supposed to 
work, or expected to fail ? I was hoping to use repart because the system I have 
to add a partition to is litterally 5000 km away, but so far this completely 
fails.
Any help would be appreciated

On Tue Jul 28, 2020 at 7:38 PM CEST, Xogium wrote:
> I am still totally unable to make use of repart when the root is
> volatile... Is
> this intended, or not ? I know volatile-root service changes where the
> sysroot.mount ends up, for overlayfs, but this prevent repart from
> working
> because it can't find the underlying root block device anymore but only
> the
> overlay.
>
> It seems so, at least. This is my only theory for as to why it would
> print
> 'failed to discover root block device'.
> Any help / ideas are welcome
>
> On Fri Jul 17, 2020 at 4:38 PM CEST, Xogium wrote:
> > Hi,
> > as the subject says, I am trying to use repart to add a partition on a
> > block
> > device, from inside the initramfs. I also make use of overlayfs via
> > systemd-volatile-root to make it possible to write temporarily on the
> > root device. However it appears that systemd-repart and
> > systemd-volatile-root are both ran in parallel: http://ix.io/2rRi
> > This results in repart failing to find the root block device.
> > Would there be any way to have repart ran before systemd-volatile-root,
> > such
> > that it has time to finish modifying the real block device ? Adding
> > systemd-volatile-root on the Before= line in systemd-repart.service via
> > an
> > override is not enough since both units are of type simple. It is
> > started before
> > the volatile root unit, but they both ultimately end up running in
> > parallel once
> > again.
> > _______________________________________________
> > systemd-devel mailing list
> > systemd-devel at lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/systemd-devel