Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form

Installing Proxmox VE: Fix Volume Group Creation Error

Posted on 10/01/201714/08/2023 IT Expert By IT Expert No Comments on Installing Proxmox VE: Fix Volume Group Creation Error
  1. Home
  2. Virtualization
  3. Installing Proxmox VE: Fix Volume Group Creation Error
virtualization

Proxmox Virtual Environment (VE) is a powerful platform for virtualization, facilitating the management of virtual machines and containers. However, during installation, you may encounter a specific issue that can hinder progress – the “Volume Group Creation Error.”

This error often arises when configuring essential components in Proxmox VE, preventing you from moving forward smoothly. Addressing this issue is crucial for a successful installation. It also ensuring the proper setup of storage volumes and smooth execution of virtual environments.

In this discussion, we’ll explore the steps to diagnose and resolve this “Volume Group Creation Error,” allowing you to install Proxmox VE without hindrance, enabling you to harness the full potential of this versatile virtualization solution.

When installing Proxmox VE 4.1, it fails right at the begining of installation with messages and prompted “unable to create volume group at /usr/bin/proxinstall line 519”. Error as follow below.

 Device boot Start End Blocks Id System
 /dev/sda1 * 32 524319 524208 83 Linux
 /dev/sda2 524320 293033631 292509312 0e Linux LVM
 /dev/sda3 0 - 0 0 Empty
 /dev/sda4 0 - 0 0 Empty
 Successfully wrote the new partition table
 [..]
 Physical volume /dev/sda2" successfully created
 A volume group called 'pve' already exists
 unable to create volume group at /usr/bin/proxinstall line 519
 umount: /target/boot: not found
 umount: /target/var: not found
 umount: /target/tmp: not found
 umount: /target/proc: not found
 umount: /target: not mounted

Solution
– I resolved this problem by simply installing Proxmox VE the RAID option to 0 and the file system to ZFS to overide the existing block (volume).
– After this i reinstalled, haven reverted back to the existing file system and reinstalled Proxmox and it worked.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Virtualization Tags:errors, proxmox, virtualization

Post navigation

Previous Post: WatchGuard Log and Report Server Installation in a VM
Next Post: How to mount a USB Drive in Linux

Related Posts

  • microsoft
    Fix EFI network timeout on VMware Workstation Virtualization
  • Enable Hyper V on Windows 11 Create a VM with PowerShell
    Run Hyper-V on Windows 11: Convert Physical PC to Hyper-V VM Virtualization
  • image 22
    How to clone a Windows Server running on VirtualBox Virtualization
  • PXE Access Denied Or Aborted
    PXE Boot Failure: “Access Denied or Aborted” with Secure Boot on [Part 4] Virtualization
  • Clone SysPrep
    Clone and Sysprep a Windows Server running on a VMware Workstation Virtualization
  • nested virtualization
    Enable the Virtual Machine Platform Windows Feature and ensure Virtualization is enabled in the BIOS Virtualization

More Related Articles

microsoft Fix EFI network timeout on VMware Workstation Virtualization
Enable Hyper V on Windows 11 Create a VM with PowerShell Run Hyper-V on Windows 11: Convert Physical PC to Hyper-V VM Virtualization
image 22 How to clone a Windows Server running on VirtualBox Virtualization
PXE Access Denied Or Aborted PXE Boot Failure: “Access Denied or Aborted” with Secure Boot on [Part 4] Virtualization
Clone SysPrep Clone and Sysprep a Windows Server running on a VMware Workstation Virtualization
nested virtualization Enable the Virtual Machine Platform Windows Feature and ensure Virtualization is enabled in the BIOS Virtualization

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • Windows 11 Taskmanager
    Create Task Manager Shortcuts: How to add access, pin the Task Manager on Windows 11 Windows
  • cryptsetup
    How to encrypt a partition with Cryptsetup Linux
  • PowerShell Exec
    Determine the execution policy configured on Windows PC Windows
  • windows server 1
    In-place upgrade for Windows Server 2012 to Windows Server 2019 Windows Server
  • dev
    Disable Developer Tools in Microsoft Edge using Registry or Group Policy in Windows Windows
  • offload apps
    How to automatically offload unused Apps on iPhone Mac
  • PowerShell Module Must Be Set To Remote Signed
    Veeam Backup and Replication: PowerShell must be Remote Signed Backup
  • Azure Virtual Desktop: Deploy host pools and session hosts in the Azure [Part 01] AWS/Azure/OpenShift

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,785 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2025 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.