[SOLVED] Help setting up the initial disk partitioning

emma.makes

Member
Feb 20, 2021
5
2
8
I'm setting up my first Proxmox environment on my local server using one NVMe drive and one 2,5" SSD.

I was planning on allocating 16GB of the NVMe drive for Proxmox VE, the rest of the NVMe as a data storage and the SSD for the VMs.

During the setup, I chose ext4 16GB disksize on the NVMe for Proxmox VE. I found no further configuration options. I redid the setup a number of times in search of said configuration.

The disk are partitioned as follows:

Code:
fdisk -l
Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disk model: nvme drive          
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: 8A230009-F3F4-4C75-AD23-AC0F83A92FC6

Device           Start      End  Sectors  Size Type
/dev/nvme0n1p1      34     2047     2014 1007K BIOS boot
/dev/nvme0n1p2    2048  1050623  1048576  512M EFI System
/dev/nvme0n1p3 1050624 33554432 32503809 15.5G Linux LVM


Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Disk model: ssd drive
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: dos
Disk identifier: 0x1e0f64e7


Disk /dev/mapper/pve-swap: 2 GiB, 2147483648 bytes, 4194304 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 /dev/mapper/pve-root: 3.8 GiB, 4026531840 bytes, 7864320 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


The SSD shows up in the disk as SSD, no usage.
If I try to add /dev/sda as a directory under disk in my node I receive the following error:

Code:
command '/sbin/sgdisk -n1 -t1:8300 /dev/sda' failed: exit code 2

How can I configure the unused space on the NVMe drive for ISO storage and the SSD for the VMs?

I'm aware that a single disk setup is not recommended due to the missing disk failure tolerance.

I appreciate your suggestions and help!
Thank you all for the help.
 
Why are you not just using the PVE Iso installer? That way you do not need to partition anything at all. The Installer can partition the NVMe drive for you using LVM and you can set how much of the drive you want to use as system storage for proxmox, storage for VMs and so on if you set the values for advanced LVM options.

Look here ("Advanced LVM Configuration Options").
 
I'm sorry if I wasn't being clear. I did use the PVE iso installer. During the installation I only found the option to chose the target drive, not the configuration of a data partition. I'll redo the installation and see how the installer formats the drive.

Edit: Apparently the default installation sets up the NVMe drive just as I wanted it to, but didn't notice beforehand. All that's left is to get by the SSD directory creation error command '/sbin/sgdisk -n1 -t1:8300 /dev/sda' failed: exit code 2
 
Last edited:
I fixed the above managed error. gdisk reported the following error, when I ran /sbin/sgdisk -n1 -t1:8300 /dev/sda in the shell

Code:
Caution: invalid main GPT header, but valid backup; regenerating main header

I used gdisk interactively to write an new/empty GPT, after which the directory could be created.
 
  • Like
Reactions: bobmc

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!