no such logical volume pve/data

fergrorke

New Member
Apr 9, 2025
2
1
3
Hello everyone

I’m very new to Proxmox, having started playing around with it today so don’t know too much.

By way of background I had a Rock Pi 4b SBC lying around doing nothing and decided I wanted to use it for network control things related to Tailscale. The Pi is running Debian 12 Bookworm so I followed these instructions on how to install Proxmox VE - https://github.com/jiangcuo/Proxmox-Port/wiki/Install-Proxmox-VE-on-Debian-bookworm – all of which was straightforward, no issues. The Proxmox GUI was available to port 8006 and I could login as root, no problem.

My next step was to try importing an aarch64 OPNsense 25.1 VM image I got from https://github.com/maurice-w/opnsense-vm-images/releases. Being a qcows2 image that appeared a little complicated but these instructions https://www.vinchin.com/vm-backup/import-qcow2-proxmox.html seemed to be what I needed.

The gotcha moment came when I tried ‘sudo qm importdisk 100 /var/lib/vz/images/100/OPNsense-25.1-ufs-efi-vm-aarch64.qcow2 local-lvm’ which resulted in the following error: 'no such logical volume pve/data'.

I subsequently discovered a couple of things.
1) I had no /etc/pve/storage.cfg file.
2) I had no /dev/pve/data directory or even /dev/pve.

So, it would appear these (and potentially other things) were not created when Proxmox was installed.

I then created a default storage.cfg file, as per https://pve.proxmox.com/wiki/Storage#_storage_configuration:

dir: local
path /var/lib/vz
content iso,vztmpl,backup

# default image store on LVM based installation
lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

# default image store on ZFS based installation
zfspool: local-zfs
pool rpool/data
sparse
content images,rootdir

This is now mirrored in the Datacenter→Storage section of the GUI. However, looking at Datacenter→Rocky→Disks→LVM, no Volume Groups are listed and if I try to create one the pop-up dialogue box tells me there are No Disks unused. At this stage I have no idea what to do next. It would be easy enough to create /dev/pve and /dev/pve/data but I’m unsure what the correct group permission assignment should be. There’s no pve group so should kvm be used? Would this even help?

All suggestions gratefully received.
 
Well, to answer my own post, upon reflection I figured out the problem was that I had Amrbian Bookworm installed on a single partition occupying the entire 2TB of my NVME, resulting in the whole space being allocated by Proxmox to local storage and therefore leaving no room for LVM.

As one can't, or at least I can't, resize a root partition when a system is online the somewhat painful solution was to do a ground-up reinstall of the whole system with the the NVME split into two partitions. (And yes, before that I did try resizing the root partition using a live boot installer but the Rock Pi didn't like that and wouldn't boot.)

With Proxmox up and running again I then had to figure out how to add LVM-Thin storage to the system. Thanks to Dunuin's excellent instructions in this thread - https://forum.proxmox.com/threads/a...vm-thin-help-needed-please.111724/post-481864 - all's now good and I can now attempt to get Opnsense arm64 up and running under Proxmox.

It's been a good, albeit steep, learning experience. :)
 
  • Like
Reactions: UdoB