[SOLVED] Partition 1 and 2 does not start on physical sector boundary.

[fedex03]

Hi there,

i had to replace the sdd of my proxmox server from 128 GB to 500 GB.

First, I cloned the ssd using Clonezilla and then changed the partitions sizes following the guide: https://i12bretro.github.io/tutorials/0644.html

Everything seems to work correctly but the output of ‘fdisk -l’ reports the following errors:

• Partition 1 does not start on physical sector boundary.
• Partition 2 does not start on physical sector boundary.

Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: CT500MX500SSD1
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: gpt
Disk identifier: 8AC7E82E-CAA2-4006-9BCE-7E027FF70A63

Device       Start       End   Sectors   Size Type
/dev/sda1       34      2047      2014  1007K BIOS boot
/dev/sda2     2048   2099199   2097152     1G EFI System
/dev/sda3  2099200 976773119 974673920 464.8G Linux LVM

Partition 1 does not start on physical sector boundary.


Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 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


Disk /dev/mapper/pve-root: 134.19 GiB, 144086925312 bytes, 281419776 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


Disk /dev/mapper/pve-vm--102--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x57146691

Device                                 Boot   Start      End  Sectors  Size Id Type
/dev/mapper/pve-vm--102--disk--0-part1 *       2048   999423   997376  487M 83 Linux
/dev/mapper/pve-vm--102--disk--0-part2      1001470 67106815 66105346 31.5G  5 Extended
/dev/mapper/pve-vm--102--disk--0-part5      1001472 67106815 66105344 31.5G 8e Linux LVM

Partition 2 does not start on physical sector boundary.


Disk /dev/mapper/pve-vm--103--disk--0: 90 GiB, 96636764160 bytes, 188743680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0xd436488a

Device                                 Boot     Start       End   Sectors  Size Id Type
/dev/mapper/pve-vm--103--disk--0-part1 *         2048    104447    102400   50M  7 HPFS/NTFS/exFAT
/dev/mapper/pve-vm--103--disk--0-part2         104448 187595991 187491544 89.4G  7 HPFS/NTFS/exFAT
/dev/mapper/pve-vm--103--disk--0-part3      187596800 188739583   1142784  558M 27 Hidden NTFS WinRE


Disk /dev/mapper/pve-vm--105--disk--0: 12 GiB, 12884901888 bytes, 25165824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--100--disk--0: 64 GiB, 68719476736 bytes, 134217728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x633f1dbd

Device                                 Boot     Start       End   Sectors  Size Id Type
/dev/mapper/pve-vm--100--disk--0-part1 *         2048 132216831 132214784   63G 83 Linux
/dev/mapper/pve-vm--100--disk--0-part2      132218878 134215679   1996802  975M  5 Extended
/dev/mapper/pve-vm--100--disk--0-part5      132218880 134215679   1996800  975M 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.


Disk /dev/mapper/pve-vm--103--state--suspend--2024--08--02: 8.49 GiB, 9114222592 bytes, 17801216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

Can this misalignment create problems?
Is there anything I can do?

I tried searching online but couldn't find anything useful

Thank you in advance for your time!

 

[leesteken]

Can this misalignment create problems?

It can cause twice the write actions, which slows stuff down and increases the wear on SSDs.

Is there anything I can do?

Maybe move the partitions with something like GParted Live, or redo your operation with Clonezilla and align the partitions properly, or ask the writer of the guide?

I tried searching online but couldn't find anything useful

Misaligned partitions are not at all Proxmox specific. Any (Linux) partitioning guide will probably apply.

 

[fedex03]

It can cause twice the write actions, which slows stuff down and increases the wear on SSDs.

Maybe move the partitions with something like GParted Live, or redo your operation with Clonezilla and align the partitions properly, or ask the writer of the guide?

Misaligned partitions are not at all Proxmox specific. Any (Linux) partitioning guide will probably apply.

Thank you for the reply.

May it will be bettore to install Proxmox from fresh.

I don't have a good understanding about partition managing.

 

[fedex03]

It can cause twice the write actions, which slows stuff down and increases the wear on SSDs.

Maybe move the partitions with something like GParted Live, or redo your operation with Clonezilla and align the partitions properly, or ask the writer of the guide?

Misaligned partitions are not at all Proxmox specific. Any (Linux) partitioning guide will probably apply.

Hi there,

I made a fresh install of Proxmox, but the error remains.

Could be an SSD defect?

Thank you for the help.

 

[leesteken]

I had a closer look. Partition 2 is the "extended partition" that is required when using MBR instead of GPT. The actual partitions that contain files are aligned. No need to change this or worry about it.

 

[fedex03]

I had a closer look. Partition 2 is the "extended partition" that is required when using MBR instead of GPT. The actual partitions that contain files are aligned. No need to change this or worry about it.

Thank you very much for the time dedicated to the check.

Now I can rest easy