On 3/31/20 11:54 AM, Renaud Allard wrote:
The funny part is that if I relaunch /autoinstall manually after the failure, it partitions everything as expected.
It seems that when (linux) extended partitions are present, the first execution of "fdisk -iy /dev/rsd0c" doesn't correctly write the MBR and some partitions are still present. Executing it a second time correctly reinits everything. Please note that I am testing on a VM running under VMware, but this is typically a case where you want that to work if you don't have a console. While solving this in install would be as trivial as executing fdisk twice, I feel there is a need to find the root cause of this.
smime.p7s
Description: S/MIME Cryptographic Signature
