Hi,
thank you for the help, I really appreciate it. I'm sorry for the very
late reply, I had an issue with my mail server and only sorted it out
today.
I had to jump through a couple of problems, but I've mostly got
something stable now.
The first is that all of the partitions needed for my bo
So, I use systemd-repart in an embedded system of mine. This system runs
systemd 254.9 and is custom made using buildroot.
I am attempting to do the following:
* Create a second root-arm partition with SecondaryRootfs label of 128
MB, and fill it with the content of the PrimaryRootfs partition.
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
e 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
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-roo
Hi,
I don't use a tmpfs, because the data that is stored there is still useful to
have, and preferably should not be lost. If it happens, alright, but in the
best
possible case it should be present.
On Thu Feb 13, 2020 at 8:22 AM, Ulrich Windl wrote:
> >>> "Xogium"
Hi,
I am wondering about how to best implement a mechanism to recreate a specific
filesystem in case of the slightest data corruption done to it. From what I
read
in systemd-makefs manpage, the tool will not trigger if it can detect that a
filesystem is already present. However I'm thinking tha
