Open yajo opened 1 month ago
Your assessment is correct, this is caused by using sgdisk (or more broadly, gptfdisk) instead of parted. However, I don't know what the reasoning was for moving from parted to sgdisk. Maybe @Mic92 or @Lassulus know more about that?
There is another related feature request to allow for more flexibility in partition sizes (#600), but I realize that this is more about restoring a feature that already existed.
parted is horrible for scripting and arguments are sometimes ignored on mandatory depending on other arguments passed. sgdisk provides a saner interface for using inside a script.
Thank you! Then I think it's clear that we won't be going back to parted. However, it should be possible to re-implement this feature after #789
I'm in the process to migrate an old system disk declaration to the new format, just like explained in https://github.com/nix-community/disko/blob/master/docs/table-to-gpt.md.
I find out a feature that the
table
type had, but thegpt
type doesn't have: declaring a partition as 50% size. This is the legacy format I'm using now:As you can see, there are 2 partitions with 50% size.
Now, when trying to do the same with the
gpt
type, this configuration fails:The error:
The ability to specify some partition to start at 50% was very useful to me, and the main problem seems to be that the
gpt
tool usessgdisk
(which expects absolute values) instead ofparted
.Is it possible to move again to
parted
forgpt
type, so we can specify more dynamic values? Or fix this somehow?@moduon MT-7504