sgdisk behaves confusingly when specifying partitions.${name}.start = "0M"
#702
Labels
bug
Something isn't working
contributions welcome
There's nothing left to discuss, feel free to submit a PR for this!
good first issue
Good for newcomers
partitions.${name}.start = "0M"
causessgdisk
to begin at the start of next free space on disk, which crashesdisko
with confusing errors.This is despite the manpage setting a distinction between plain 'N' as sector numbers and 'N[K/M/G]' as logical size/byte positions, and stating that '0' is the 'next free space' position, not 0 with a letter.
In any case it would be nice to have a check for
start = '0*'
(and possibly any intersections which fail too) indisko
as thesgdisk
is an implementation detail. Start should be 1M (or whatever is physically possible minimum considering GPT and such) or not specified for the first partition, with only size being specified.Encountered errors for reference:
Could not create partition 1 from 1258295296 to 1258297343
(sgdisk
)Failed to open key file.
(cryptsetup luksFormat
; not in thedisko
log, but when grabbed from the generateddiskoScript
and tried manually; not sure if this was caused by the same issue but maybe)start = "0M"
and then proceeded failing again with the samedisko.nix
The text was updated successfully, but these errors were encountered: