Partition 1 does not start on physical sector boundary.

[madhonk]

Dear Community,

we are running several Proxmox Installations without any Problems.

But our recent installation produces an sector error:

==>

Disk /dev/sda: 279.4 GiB, 300035497984 bytes, 586006832 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: 0D432888-AD36-4918-ABBC-1AC6DC521ABB

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 586006798 584956175 279G Linux LVM

Partition 1 does not start on physical sector boundary.

<==


It is a fresh Installation on a new HP ProLiant DL20 -> two SAS 15k in a RAID1
Adaptec RAID Controller

The HDDs are OK - iLO confirmed that

Does anyone know this specific problem?


Thanks in advance,
Markus

 

[wolfgang]

Hi,

please check if there is new firmware for this controller.
To verify you can install a Ubuntu 18.10 and see if it working.
Install it on LVM.

What model is this Raid card.

 

[madhonk]

Dear Wofgang

thank you for the quick response - it is a Smart Array E208i-a Controller

At the moment we try to recreate the RAID in DEBUG MODE and reinstall PROXMOX from the scratch

Thank you for the hint with Ubuntu 18.10 - hopefully it is not necessary

Best regards

 

[madhonk]

Hi,

now we updated the firmware / raid Controller
reinstalled Proxmox with manual partitions an automatically -> same error

But what is buzzing me -> the parted print output does not raise any errors =>

parted /dev/sda print
Model: HPE LOGICAL VOLUME (scsi)
Disk /dev/sda: 283GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 17.4kB 1049kB 1031kB bios_grub
2 1049kB 538MB 537MB fat32 boot, esp
3 538MB 283GB 282GB lvm


So we compared the partitions with an existing Proxmox installation

OLD Installation:
* pve-manager/5.3-8/2929af8e (running kernel: 4.15.18-10-pve)
* fdisk from util-linux 2.29.2

==>

fdisk -l /dev/sda
Disk /dev/sda: 464.7 GiB, 498999492608 bytes, 974608384 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: gpt
Disk identifier: C5A80B1C-BBD2-4D8C-ACEA-B1964EE6A71D

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 974608350 973557727 464.2G Linux LVM

<==

New Installation:
* pve-manager/5.4-3/0a6eaa62 (running kernel: 4.15.18-12-pve)
* fdisk from util-linux 2.29.2

==>
fdisk -l /dev/sda
Disk /dev/sda: 263.4 GiB, 282855890944 bytes, 552452912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 524288 bytes
Disklabel type: gpt
Disk identifier: 8BB63F83-0588-4A66-A596-BBBF8C25BA8B

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 552452878 551402255 263G Linux LVM

Partition 1 does not start on physical sector boundary.

<==

So there is no difference except the third partition size.

Maybe everything ist fine but there is a bug in fdisk or somewhere else?

 

[madhonk]

Dear Wolfgang,
Dear Community

the problem ist only partition 1 - boot partition

It seems that this is not really a problem -> https://forum.proxmox.com/threads/partition-error-on-new-install.37776/

It makes sense but we are not sure about this...

What's your opinion about this as a Proxmox Pro? Or anybody else?