Dear Nils,
Thank you for the fast answer.
Am 06.05.24 um 02:00 schrieb Nils Kattenbeck:
This was not properly implemented until the current version:
https://github.com/systemd/systemd/pull/30030
Indeed, it seems to work with Ubuntu 24.04 (noble numbat) with *systemd*
255.4-1ubuntu8.
```
$ systemd --version
systemd 255 (255.4-1ubuntu8)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS
+OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD
+LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2
+BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT
default-hierarchy=unified
$ sudo journalctl -u systemd-repart
May 07 10:31:27 localhost systemd-repart[424]: Failed to find TPM2
pcrlock policy file 'pcrlock.json': No such file or directory
May 07 10:31:27 localhost systemd-repart[424]: Device '/' has no
dm-crypt/dm-verity device, no need to look for underlying block device.
May 07 10:31:27 localhost systemd-repart[424]: Device /dev/vda opened
and locked.
May 07 10:31:27 localhost systemd-repart[424]: Sector size of device is
512 bytes. Using grain size of 4096.
May 07 10:31:27 localhost systemd-repart[424]: TYPE
LABEL UUID PARTNO FILE
NODE OFFSET OLD SIZE RAW SIZE SIZE OLD
PADDING RAW PADDING PADDING ACTIVITY
May 07 10:31:27 localhost systemd-repart[424]: esp
esp 53907356-a252-4940-8ed1-c20276a7e04d 0
00-esp.conf /dev/vda1 1048576 536870912 536870912 512.0M
0 0 0B unchanged
May 07 10:31:27 localhost systemd-repart[424]:
21686148-6449-6e6f-744e-656564454649 linux
60b723a6-ff6c-49f0-91af-1d47e379d03c 1 05-bios.conf /dev/vda2
537919488 1048576 1048576 1.0M 0 0
0B unchanged
May 07 10:31:27 localhost systemd-repart[424]: root-x86-64
root-x86-64 05068373-5d08-4133-ac7d-719e5498d27d 2
10-root.conf /dev/vda3 538968064 1117876224 108492058624 1.0G → 101.0G
107374182400 0 100.0G → 0B resize
May 07 10:31:27 localhost systemd-repart[424]:
Σ = 101.5G
Σ = 0B
May 07 10:31:27 localhost systemd-repart[424]:
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░
May 07 10:31:27 localhost systemd-repart[424]: ├─ 10-root.conf
May 07 10:31:27 localhost systemd-repart[424]: ├─ 05-bios.conf
May 07 10:31:27 localhost systemd-repart[424]: └─ 00-esp.conf
May 07 10:31:27 localhost systemd-repart[424]: Applying changes to /dev/vda.
May 07 10:31:27 localhost systemd-repart[424]: Growing existing partition 2.
May 07 10:31:27 localhost systemd-repart[424]: Writing new partition table.
May 07 10:31:28 localhost systemd-repart[424]: Telling kernel to reread
partition table.
May 07 10:31:28 localhost systemd-repart[424]: All done.
May 07 10:31:28 localhost systemd[1]: systemd-repart.service: Child 424
belongs to systemd-repart.service.
May 07 10:31:28 localhost systemd[1]: systemd-repart.service: Main
process exited, code=exited, status=0/SUCCESS (success)
May 07 10:31:28 localhost systemd[1]: systemd-repart.service: Changed
start -> exited
May 07 10:31:28 localhost systemd[1]: systemd-repart.service: Job 60
systemd-repart.service/start finished, result=done
May 07 10:31:28 localhost systemd[1]: Finished systemd-repart.service -
Repartition Root Disk.
May 07 10:31:28 localhost systemd[1]: systemd-repart.service: Control
group is empty.
```
On Ubuntu 22.04 editing the partition table with `fdisk /dev/vda` or
using `growpart /dev/vda 3` (package *cloud-guest-utils*) works around it.
Kind regards,
Paul
