[SOLVED] Partition 1 does not start on physical sector boundary after upgrade from 6.0 to 6.1

sif7en

New Member
Nov 18, 2019
4
1
3
43
Hello,

We have ecountered a problem with upgrading Proxmox node frpm 6.0 to 6.1

Our disk setup consist of HW raid 2x SSD 512 and Ceph RBD

lsbl output looks like:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 446.6G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part
└─sda3 8:3 0 446.1G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 96G 0 lvm /
├─pve-data_tmeta 253:2 0 3.3G 0 lvm
│ └─pve-data 253:4 0 319.6G 0 lvm
└─pve-data_tdata 253:3 0 319.6G 0 lvm
└─pve-data 253:4 0 319.6G 0 lvm
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 100M 0 part /var/lib/ceph/osd/ceph-1
└─sdb2 8:18 0 1.8T 0 part
sdc 8:32 0 1.8T 0 disk
├─sdc1 8:33 0 100M 0 part /var/lib/ceph/osd/ceph-3
└─sdc2 8:34 0 1.8T 0 part
sdd 8:48 0 1.8T 0 disk
├─sdd1 8:49 0 100M 0 part /var/lib/ceph/osd/ceph-5
└─sdd2 8:50 0 1.8T 0 part
sde 8:64 0 1.8T 0 disk
├─sde1 8:65 0 100M 0 part /var/lib/ceph/osd/ceph-7
└─sde2 8:66 0 1.8T 0 part

However after upgrade the fidsk function command outputs:

Disk /dev/sda: 446.6 GiB, 479559942144 bytes, 936640512 sectors
Disk model: SMC3108
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: 2E152527-E5F3-46FC-A58D-FB615BAFB490
Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 1050623 1048576 512M EFI System
/dev/sda3 1050624 936640478 935589855 446.1G Linux LVM
Partition 1 does not start on physical sector boundary.

It looks like /dev/sda3 (LVM) is alligned, while options 1 and 2 are not.

Partition /dev/sda is the one that resides on HW SDD RAID1 controler. This error was not present before and I'd like to find out why did it occure all of the sudden and what could be the impact on performance ?
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
4,291
535
118
Partition 1 does not start on physical sector boundary.
this should have been present since quite a while (before 5.2 afair) for efi booted systems (and since at least 6.0 for all systems)
partition 1 is the bios-boot partition, consists of less than 1M and is only used for storing the grub stage1 for bios boot.
this usually is not read or written during regular operations - the only exception being running grub-install on the drive (which you'd need to do manually) - so the impact should be non-existent/negligible

I hope this helps!
 

sif7en

New Member
Nov 18, 2019
4
1
3
43
Thanks for the fast response, this helps explaining the issue. So if it is safe and it does not cause any problems I'll leave as it is.
 
  • Like
Reactions: Stoiko Ivanov

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
4,291
535
118
Thanks for the fast response, this helps explaining the issue. So if it is safe and it does not cause any problems I'll leave as it is.
Should be safe and not cause problems - else I would expect that some of the installations done in the past year would have shown the problems.

Please mark the thread as 'SOLVED' - it could help other users with the same question.

Thanks!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!