On 26/08/2024 at 08:34, Holger Wansing wrote:
Am 26. August 2024 00:33:48 MESZ schrieb Pascal Hambourg
<pas...@plouf.fr.eu.org>:
Maybe the firmware packages in /firmware and /pool are not
deduplicated in your image ?
Need to check:
I used an instruction for remastering of the image from
https://wiki.debian.org/DebianInstaller/Preseed/EditIso
and would be surprised about such effects...
But in fact that seems to be the issue.
The firmware deduplication thingy is rather new, and therefore not
respected in that guide already.
IIRC, /firmware used to contain symlinks to actual firmware debs located
in /pool. But at some point some people complained that they could not
copy the image contents to a FAT filesystem which does not support
symlinks, so they were replaced with ISO9660 "hard links".
If you provide the minimum disk size required to reach /boot maximum
size, I can adjust the priority accordingly.
I think 25G should be fine.
(Can ESP get the same values BTW?)
Yes. The actual threshold is not very accurate due to the current
algorithm granularity (priorities are normalized on a base 100 and
rounded to integers). I updated the MR with two new commits:
- increase / minimum size and tweak ESP and /boot priorites
- add small_disk recipe for 3GB-10GB disks
New minimum disk sizes (with EFI and LVM):
- atomic 10GB
- home 10.5G
- multi 12.5GB
- server 10GB
