Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 3
    It actually seems documentation is a bit sloppy in this area, since it only specifies e.g. kB as an allowed unit for kilobyte (here it documents that number suffixes use the same units as the unit commnad). However, the code actually seems to look only at the first two characters, but is also lowercase, which is why kB, k and K (and even kFOO) all work. Commented Oct 20, 2021 at 6:57
  • Re "One exception is that when using power-of-two-units": So a workaround to force alignment could be to convert (and use) the real megabytes into Gparted's megabytes (?). (Multiply by approx. 1.05.) Commented Mar 26, 2023 at 19:40
  • I can positively confirm that this trick works. In my case, the underlying size of the disk was only divisible by 8 kB (other prime factors were 3, 3, 3, 7, 547 and 1181). Using the two limits "-2089MiB" and "-2489MiB" to Gparted (offset from end of the disk) resulted in unaligned partition starts (951380.7109375 MiB and 951780.7109375 MiB). Whereas using the converted "-2190MB" and "-2610MB" resulted in alignment to 1 MiB boundaries (951381 MiB and 951781), approx. a 0.29 MiB shift in starting position. Commented Mar 26, 2023 at 22:20
  • Correction: Parted (command line), not GParted (GUI). Commented Mar 28, 2023 at 16:55
  • This was tested with Parted 3.2 and Parted 3.3. Commented Mar 28, 2023 at 19:15