Advice on New Storage Type

stoney777

New Member
Oct 26, 2024
1
0
1
I am just starting to get accustomed to Proxmox. I come from a strong VMware background so I may confuse certain things so apologies in advance!

I have a single host running Proxmox. Proxmox itself is installed on a smaller SSD for which I chose ext4 as the storage type.

I added a second 2TB NVMe and unfortunately got a bit excited and just chose most options for the storage type eg. Images, backups, ISO's etc.

I believe that because of this, one of my VM's on that drive is unable to take snapshots.

My requirement from Proxmox is just to be able to run VM's which are thin provisioned and to also be able to take snapshots. For backups and ISO's etc, I have access to a NAS which can handle all that.

How best do I proceed with that already installed 2TB? Do i just wipe and start over or can it be converted?

The VM that is not able to take snapshots for some reason has the RAW disk format. This is the home assistant VM and the process involves donwloading the qcow disk and attaching it to the VM via command line. Here is the command I used:

Code:
qm importdisk 102 haos_ova-13.2.qcow2 lexar2tb

Here is my storage config:

Code:
cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content iso,backup,vztmpl

lvmthin: local-lvm
        thinpool data
        vgname pve
        content images,rootdir

dir: lexar2tb
        path /mnt/pve/lexar2tb
        content backup,rootdir,vztmpl,iso,snippets,images
        is_mountpoint 1
        nodes proxmox001

cifs: synologyds1821
        path /mnt/pve/synologyds1821
        server 192.168.0.113
        share Backups
        content backup
        prune-backups keep-all=1
        subdir /Proxmox
        username svc_proxmox_backup

Code:
pvesm status
Name                  Type     Status           Total            Used       Available        %
lexar2tb               dir     active      1921724676        40718868      1783313748    2.12%
local                  dir     active        71017632        10547488        56816924   14.85%
local-lvm          lvmthin     active       148086784         1362398       146724385    0.92%
synologyds1821        cifs     active     22490509088     18783865044      3706644044   83.52%

The VM that is not able to take snapshots:

Code:
root@proxmox001:~# qm config 102
agent: 1
bios: ovmf
boot: order=scsi0
cores: 2
cpu: x86-64-v2-AES
efidisk0: lexar2tb:102/vm-102-disk-0.qcow2,efitype=4m,size=528K
ide2: none,media=cdrom
memory: 4096
meta: creation-qemu=8.1.5,ctime=1729866155
name: homeassistant
net0: virtio=bc:24:11:91:48:11,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: lexar2tb:102/vm-102-disk-1.raw,discard=on,iothread=1,size=32G
scsihw: virtio-scsi-single
smbios1: uuid=0ffbce1a-3a74-49d4-b0dc-52e02a20a06b
sockets: 1
usb0: host=1-2
vmgenid: e0bd03b2-04ce-44e8-9329-27f473dd87e3

The VM that is able to take snapshots:

Code:
root@proxmox001:~# qm config 101
agent: 1
boot: order=scsi0;ide2;net0
cores: 1
cpu: x86-64-v2-AES
ide2: none,media=cdrom
machine: pc-i440fx-8.1
memory: 7629
meta: creation-qemu=8.1.5,ctime=1729784150
name: blueiris-w10
net0: virtio=BC:24:11:D5:31:2B,bridge=vmbr0,firewall=1,tag=4
numa: 0
onboot: 1
ostype: win10
parent: test
scsi0: lexar2tb:101/vm-101-disk-0.qcow2,cache=writeback,iothread=1,size=80G
scsihw: virtio-scsi-single
smbios1: uuid=cad5c965-5df0-40c1-b056-a3bafccb4cab
sockets: 1
vcpus: 1
vmgenid: a348ecb3-c82a-4b80-8987-b5d73a31adf7

advice welcome!
 
Last edited:

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!