Boot method: network
Image version: https://d-i.debian.org/daily-images/arm64/20210325-02:16/netboot/netboot.tar.gz
Date: 2021-03-25 ~17:00 UTC
Machine: apm mustang
Partitions:
Filesystem Type 1K-blocks Used Available Use% Mounted on
udev devtmpfs 16359696 0 16359696 0% /dev
tmpfs tmpfs 3281996 524 3281472 1% /run
/dev/mapper/mst0vg-mst00--root ext4 4721184 1233016 3227664 28% /
tmpfs tmpfs 16409976 0 16409976 0% /dev/shm
tmpfs tmpfs 5120 0 5120 0% /run/lock
/dev/sda1 vfat 511720 4352 507368 1% /boot/efi
tmpfs tmpfs 3281992 0 3281992 0% /run/user/1000
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [O]
Detect media: [ ]
Load installer modules: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Detect hard drives: [O]
Partition hard drives: [E]
Install base system: [E]
Install tasks: [O]
Install boot loader: [O]
Overall install: [O]
Comments/Problems:
I was performing an installation with existing LVM volumes of several
virtual machines, and partman defaulted to selecting the ESP
partitions that were present inside the LVM volumes of the virtual
machines, but would fail to proceed during the installation. Going
back to the partitioning menu and setting each of the undesired ESP
partitions to "do not use this partition" eventually allowed the
install to proceed.
Similar issue with swap partitions, though I'm sure it would have
happily proceeded to re-initialize all the swap partitions in the
virtual machine images... not sure how to handle that sanely; other
than potentially suspend-to-disk images, it is fairly easy to recover
from having the swap signature rewritten.