partioning unit confusion

[pellepelster]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

I attempted to trigger a server install, using the default partitioning scheme retrieved via

$ scw dedibox server get-partitioning server-id=<server_id> os-id=482
Partitions.0.Type          primary
Partitions.0.FileSystem    efi
Partitions.0.MountPoint    /boot/efi
Partitions.0.RaidLevel     no_raid
Partitions.0.Capacity      600 B
Partitions.0.Connectors.0  A
Partitions.1.Type          primary
Partitions.1.FileSystem    swap
Partitions.1.RaidLevel     no_raid
Partitions.1.Capacity      512 B
Partitions.1.Connectors.0  A
Partitions.1.Connectors.1  B
Partitions.2.Type          primary
Partitions.2.FileSystem    ext4
Partitions.2.MountPoint    /boot
Partitions.2.RaidLevel     raid1
Partitions.2.Capacity      600 B
Partitions.2.Connectors.0  A
Partitions.2.Connectors.1  B
Partitions.3.Type          primary
Partitions.3.FileSystem    ext4
Partitions.3.MountPoint    /
Partitions.3.RaidLevel     raid1
Partitions.3.Capacity      20 kB
Partitions.3.Connectors.0  A
Partitions.3.Connectors.1  B
Partitions.4.Type          primary
Partitions.4.FileSystem    ext4
Partitions.4.MountPoint    /data
Partitions.4.RaidLevel     raid1
Partitions.4.Capacity      955 kB
Partitions.4.Connectors.0  A
Partitions.4.Connectors.1  B

The capacity units kB and B seem off, e.g. 512 B seems to actually be 512 Mb when using the web frontend, same for 20 kB which seems to be 20000 Mb in the web frontend.

scw dedibox server install

claims to only accept G and Gb as capacity units, but when I provide roughly matching units like this

scw dedibox server install \
    //...
    partitions.0.file-system=efi \
    partitions.0.mount-point=/boot/efi \
    partitions.0.raid-level=no_raid \
    partitions.0.capacity="1 G" \
    partitions.0.connectors.0=A \
    partitions.1.file-system=swap \
    partitions.1.raid-level=no_raid \
    partitions.1.capacity="1 G" \
    partitions.1.connectors.0=A \
    partitions.1.connectors.1=B \
    partitions.2.file-system=ext4 \
    partitions.2.mount-point=/boot \
    partitions.2.raid-level=raid1 \
    partitions.2.capacity="1 G" \
    partitions.2.connectors.0=A \
    partitions.2.connectors.1=B \
    partitions.3.file-system=ext4 \
    partitions.3.mount-point=/ \
    partitions.3.raid-level=raid1 \
    partitions.3.capacity="20 G" \
    partitions.3.connectors.0=A \
    partitions.3.connectors.1=B \
    partitions.4.file-system=ext4 \
    partitions.4.mount-point=/data \
    partitions.4.raid-level=raid1 \
    partitions.4.capacity="955 G" \
    partitions.4.connectors.0=A \
    partitions.4.connectors.1=B \
    //...

I get even more confusing units as an error during validation

//...
Total partitions sizes 24000000000 Mo exceeds the disk size (976756 Mo) on connector A

Expected Behavior

Have the same possibility to specify capacity with Mb accuracy like in the web frontend.

Actual Behavior

No clear error messages and/or documentation how to correctly specify partition capacities

More info

$ scw version
Version          2.56.3
BuildDate        2026-06-09T10:18:17Z
GoVersion        go1.26.4
GitBranch        HEAD
GitCommit        94a66f7a
GoArch           amd64
GoOS             linux
UserAgentPrefix  scaleway-cli