Incorrect partitioning during install?

dswartz

Renowned Member
Dec 13, 2010
286
9
83
So I did a VE 2.2 install and it's working just fine. I want to move the boot disk to a smaller SSD so I can use the larger one for other purposes. I happened to be looking at the output of fdisk, and something suspicious leaped out at me:

root@proxmox:~# fdisk -l /dev/sde

Disk /dev/sde: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000da2e3

Device Boot Start End Blocks Id System
/dev/sde1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sde2 66 15567 124510208 8e Linux LVM


It looks like the two partitions overlap on cylinder 66? At first I thought I was misreading/understanding the output, but every other disk I have looked at has the first cylinder of partition N+1 one after the last cylinder of partition N. If this is really wrong, I assume it just doesn't cause issues since /dev/sde1 is /boot which uses very little space, but if that stopped being true, the volume could get corrupted, no?
 
So I did a VE 2.2 install and it's working just fine. I want to move the boot disk to a smaller SSD so I can use the larger one for other purposes. I happened to be looking at the output of fdisk, and something suspicious leaped out at me:

root@proxmox:~# fdisk -l /dev/sde

Disk /dev/sde: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000da2e3

Device Boot Start End Blocks Id System
/dev/sde1 * 1 66 523264 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sde2 66 15567 124510208 8e Linux LVM


It looks like the two partitions overlap on cylinder 66? At first I thought I was misreading/understanding the output, but every other disk I have looked at has the first cylinder of partition N+1 one after the last cylinder of partition N. If this is really wrong, I assume it just doesn't cause issues since /dev/sde1 is /boot which uses very little space, but if that stopped being true, the volume could get corrupted, no?

Hi,
switch with fdisk to sectors and you will see there is no overlapping:
Code:
Disk /dev/sda: 300.1 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders, total 586072368 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
Disk identifier: 0x000d4329

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1048575      523264   83  Linux
/dev/sda2         1048576   586072063   292511744   8e  Linux LVM
Udo
 
Last edited:
Ah, okay. That's a relief, thanks. I suppose that explains the warning about the partition not ending on a cylinder boundary...
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!