Topic: Rounding problem with GParted
I am in the process of aligning my /dev/sda partitions to 1 MiB boundaries (2048 sectors) before moving my disk contents to an SSD.
And I fall on problems = the GParted Move/Resize dialog seems to be rounding numbers and keeping me from doing the job.
Here is the latest setup of my /dev/sda disk:
root@debian:/mnt/dm3# sfdisk -l -u S /dev/sda Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x165e165e Device Boot Start End Sectors Size Id Type /dev/sda1 2048 2097151 2095104 1023M 1b Hidden W95 FAT32 /dev/sda2 * 2097152 102760447 100663296 48G 7 HPFS/NTFS/exFAT /dev/sda3 102760448 144418815 41658368 19.9G 17 Hidden HPFS/NTFS /dev/sda4 193185792 312581807 119396016 57G f W95 Ext'd (LBA) /dev/sda5 197103616 205629439 8525824 4.1G 7 HPFS/NTFS/exFAT /dev/sda6 205632063 254935484 49303422 23.5G 7 HPFS/NTFS/exFAT /dev/sda7 254935548 304094384 49158837 23.5G 7 HPFS/NTFS/exFAT /dev/sda8 304094448 312580095 8485648 4G 7 HPFS/NTFS/exFAT
As you can see, sda1, sda2, sda 3 and sda5 are all well aligned:
- start sector on a number divisible by 2048
- end sector on a (number divisible by 2048) - 1
However, sda6 is not (yet), it is 2623 sectors away on the right from the point where I want it to be.
The Move/Resize Dialog shows the following values:
Free space preceding (MiB): 1
New size (MiB): 24074
Free space following (MiB): 0
Whether I set "Align to" on MiB or None (didn't try Cylinder as this is not what I am looking for), there is no way I can bring "Free space preceding (MiB):" to 0 !!
- The little arrow for decreasing the value is not active / grayed out.
- Replacing 1 by 0 on the keyboard sets back the value to 1 as soon as I leave the box
- Moving the graphical handles at top never goes below 1.
Therefore, I have no way to bring my partition to the left by 2623 sectors to the start value of 205629440, which is divisible by 2048 and so is a MiB boundary :-(
Is there a workaround ? A bug to fix ? Or something I am doing wrong ?
Thanks for the support, Erwin9.