What's the consequence of partitions not matching boundaries on a clone

[Whit Blauvelt]

Going from a HD to an SSD, fdisk now shows for the SSD:

Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00022f72

Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 63 19535039 19534977 9.3G 83 Linux
/dev/sdc2 19535040 21494969 1959930 957M 82 Linux swap / Solaris
/dev/sdc3 21495031 625141759 603646729 287.9G f W95 Ext'd (LBA)
/dev/sdc5 21495033 320721659 299226627 142.7G 8e Linux LVM
/dev/sdc6 320721723 353122898 32401176 15.5G 83 Linux
/dev/sdc7 353124352 625141759 272017408 129.7G 83 Linux

Partition 1 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 5 does not start on physical sector boundary.
Partition 6 does not start on physical sector boundary.

Is this of concern?

[Steven Shiau]

Basically it's OK. However, if you want to improve that, you might be able to use some disk utility program to fix that. Some hard drive vendor provides such tools, so you can find that to give it a try.

Steven