Newly Created Disk not appearing in VM

oliversimpson_

New Member
Feb 23, 2024
11
0
1
Hi Everyone.

I have just installed 2x 3TB HDDs into the physical machine where proxmox is running, and I have added them as Lvmthin drives.
I have added them into my main virtual machine (Domain Controller running Windows Server 2022), however, despite restarting the VM (through proxmox), the drive does not appear in file explorer. I have no drive problems and have installed the relavent VirtiO driver for storage.
The drives are both set to 2500Gb in the hardware options, and show up grey rather than orange leading me to believe that proxmox is satisfied that the drives have been allocated to the VM successfully.

Any help would be greatly appreciated.
Thanks in advance.
 
Showing your VM config "qm config [id]" would be helpful.
Also, output of "cat /etc/pve/storage.cfg", "lsblk", "lvs".

This will help understand whether your PVE looks ok, if it does then issue is possibly in Windows which requires a more involved troubleshooting.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
root@oliversimpson:~# qm config 100
balloon: 512
bios: ovmf
boot: order=ide0;net0
cores: 2
cpu: host
efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-100-disk-1,size=128G
ide1: local:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812K
machine: pc-q35-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1707548887
name: Sim-VM01
net0: virtio=BC:24:11:A1:07:4E,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=7883d88e-3421-4287-bbda-23598f3bf1a0
sockets: 1
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
unused0: main1:vm-100-disk-0
unused1: main2:vm-100-disk-0
unused2: main1:vm-100-disk-1
unused3: main1:vm-100-disk-3
vga: qxl3
vmgenid: 6520b65a-1495-4147-9379-a55e1b6b5566

--

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

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

lvmthin: main1
thinpool main1
vgname main1
content images,rootdir
nodes oliversimpson

lvmthin: main2
thinpool main2
vgname main2
content rootdir
nodes oliversimpson

--

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 2.7T 0 disk
├─main1-main1_tmeta 252:19 0 15.9G 0 lvm
│ └─main1-main1-tpool 252:21 0 2.7T 0 lvm
│ ├─main1-main1 252:25 0 2.7T 1 lvm
│ ├─main1-vm--100--disk--0 252:26 0 2.4T 0 lvm
│ ├─main1-vm--100--disk--1 252:29 0 32G 0 lvm
│ ├─main1-vm--100--disk--2 252:30 0 2.4T 0 lvm
│ └─main1-vm--100--disk--3 252:31 0 400G 0 lvm
└─main1-main1_tdata 252:20 0 2.7T 0 lvm
└─main1-main1-tpool 252:21 0 2.7T 0 lvm
├─main1-main1 252:25 0 2.7T 1 lvm
├─main1-vm--100--disk--0 252:26 0 2.4T 0 lvm
├─main1-vm--100--disk--1 252:29 0 32G 0 lvm
├─main1-vm--100--disk--2 252:30 0 2.4T 0 lvm
└─main1-vm--100--disk--3 252:31 0 400G 0 lvm
sdb 8:16 0 2.7T 0 disk
├─main2-main2_tmeta 252:22 0 15.9G 0 lvm
│ └─main2-main2-tpool 252:24 0 2.7T 0 lvm
│ ├─main2-main2 252:27 0 2.7T 1 lvm
│ └─main2-vm--100--disk--0 252:28 0 2.4T 0 lvm
└─main2-main2_tdata 252:23 0 2.7T 0 lvm
└─main2-main2-tpool 252:24 0 2.7T 0 lvm
├─main2-main2 252:27 0 2.7T 1 lvm
└─main2-vm--100--disk--0 252:28 0 2.4T 0 lvm
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 1G 0 part /boot/efi
└─nvme0n1p3 259:3 0 237.5G 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 69.4G 0 lvm /
├─pve-data_tmeta 252:2 0 1.4G 0 lvm
│ └─pve-data-tpool 252:4 0 141.2G 0 lvm
│ ├─pve-data 252:5 0 141.2G 1 lvm
│ ├─pve-vm--100--disk--0 252:6 0 4M 0 lvm
│ ├─pve-vm--100--disk--1 252:7 0 128G 0 lvm
│ ├─pve-vm--100--disk--2 252:8 0 4M 0 lvm
│ ├─pve-vm--200--disk--0 252:9 0 4M 0 lvm
│ ├─pve-vm--200--disk--1 252:10 0 64G 0 lvm
│ ├─pve-vm--200--disk--2 252:11 0 4M 0 lvm
│ ├─pve-vm--101--disk--0 252:12 0 4M 0 lvm
│ ├─pve-vm--101--disk--1 252:13 0 32G 0 lvm
│ ├─pve-vm--101--disk--2 252:14 0 4M 0 lvm
│ ├─pve-vm--102--disk--0 252:15 0 4M 0 lvm
│ ├─pve-vm--102--disk--1 252:16 0 32G 0 lvm
│ ├─pve-vm--102--disk--2 252:17 0 4M 0 lvm
│ └─pve-vm--150--disk--0 252:18 0 32G 0 lvm
└─pve-data_tdata 252:3 0 141.2G 0 lvm
└─pve-data-tpool 252:4 0 141.2G 0 lvm
├─pve-data 252:5 0 141.2G 1 lvm
├─pve-vm--100--disk--0 252:6 0 4M 0 lvm
├─pve-vm--100--disk--1 252:7 0 128G 0 lvm
├─pve-vm--100--disk--2 252:8 0 4M 0 lvm
├─pve-vm--200--disk--0 252:9 0 4M 0 lvm
├─pve-vm--200--disk--1 252:10 0 64G 0 lvm
├─pve-vm--200--disk--2 252:11 0 4M 0 lvm
├─pve-vm--101--disk--0 252:12 0 4M 0 lvm
├─pve-vm--101--disk--1 252:13 0 32G 0 lvm
├─pve-vm--101--disk--2 252:14 0 4M 0 lvm
├─pve-vm--102--disk--0 252:15 0 4M 0 lvm
├─pve-vm--102--disk--1 252:16 0 32G 0 lvm
├─pve-vm--102--disk--2 252:17 0 4M 0 lvm
└─pve-vm--150--disk--0 252:18 0 32G 0 lvm

--

LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
main1 main1 twi-aotz-- <2.70t 0.00 0.17
vm-100-disk-0 main1 Vwi-a-tz-- 2.44t main1 0.00
vm-100-disk-1 main1 Vwi-a-tz-- 32.00g main1 0.00
vm-100-disk-2 main1 Vwi-aotz-- 2.44t main1 0.00
vm-100-disk-3 main1 Vwi-a-tz-- 400.00g main1 0.00
main2 main2 twi-aotz-- <2.70t 0.00 0.17
vm-100-disk-0 main2 Vwi-a-tz-- 2.44t main2 0.00
data pve twi-aotz-- <141.23g 63.31 3.21
root pve -wi-ao---- <69.37g
swap pve -wi-ao---- 8.00g
vm-100-disk-0 pve Vwi-aotz-- 4.00m data 14.06
vm-100-disk-1 pve Vwi-aotz-- 128.00g data 19.85
vm-100-disk-2 pve Vwi-aotz-- 4.00m data 1.56
vm-101-disk-0 pve Vwi-a-tz-- 4.00m data 14.06
vm-101-disk-1 pve Vwi-a-tz-- 32.00g data 35.17
vm-101-disk-2 pve Vwi-a-tz-- 4.00m data 1.56
vm-102-disk-0 pve Vwi-a-tz-- 4.00m data 14.06
vm-102-disk-1 pve Vwi-a-tz-- 32.00g data 35.55
vm-102-disk-2 pve Vwi-a-tz-- 4.00m data 1.56
vm-150-disk-0 pve Vwi-a-tz-- 32.00g data 50.10
vm-200-disk-0 pve Vwi-a-tz-- 4.00m data 14.06
vm-200-disk-1 pve Vwi-a-tz-- 64.00g data 39.58
vm-200-disk-2 pve Vwi-a-tz-- 4.00m data 1.56
 
unused0: main1:vm-100-disk-0
unused1: main2:vm-100-disk-0
unused2: main1:vm-100-disk-1
unused3: main1:vm-100-disk-3
the "unused" is quite literal and does say that disks are unused by VM. You need to edit each disk and assign it to an interface.
I suspect you wont be able to assign them all to IDE and may need to use SCSI, I dont recall. In my opinion, you are better off using SCSI instead of IDE for everything.
You can find more details in our study:
https://kb.blockbridge.com/technote/proxmox-optimizing-windows-server/part-1.html
https://kb.blockbridge.com/technote/proxmox-optimizing-windows-server/part-2.html



Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
How do I edit each disk to assign it?
Open PVE GUI and login. Navigate to VM property by opening the VM in the left tree, then selecting hardware in the right panel.
Highlight the unused disk by a mouse click, the "Edit" menu on the top should become available. When you select the "Edit" button a wizard will appear where you can choose Controller, Lun and other appropriate information.

Good luck


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
Disk-2 in your screenshot is a special TMP device, why are you trying to edit it? I suspect its working or your VM wont boot.

You need to update the "unused" disks, which should be listed towards the bottom of the hardware page.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
lvmthin: main1
thinpool main1
vgname main1
content images,rootdir
nodes oliversimpson

lvmthin: main2
thinpool main2
vgname main2
content rootdir
nodes oliversimpson
as you can see above you "main1" is configured to support "images" and "rootdir". In Proxmox speak "images" are virtual disks presented to VM, "rootdir" are filesystems for Containers.
The error you are seeing is telling you that VM wont start because "main2" is misconfigured. I am guessing you iterated with its configuration after you created the disks, because otherwise you would not have been able to create the disks in the first place.

Have a good night and enjoy Proxmox.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Was missing permissions for "Disk Image" on the datacentre config.
Thanks very much for your help.
It's the middle of the day here, but thank you I will enjoy it.
Have a good night.
 
I've gone into the server, and it is still not there.

Here are the commands from before (repeated now):
balloon: 512
bios: ovmf
boot: order=ide0;net0
cores: 2
cpu: host
efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-100-disk-1,size=128G
ide1: local:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812K
machine: pc-q35-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1707548887
name: Sim-VM01
net0: virtio=BC:24:11:A1:07:4E,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
sata0: main1:vm-100-disk-0,size=2500G
sata1: main2:vm-100-disk-0,size=2500G
sata2: main1:vm-100-disk-1,size=32G
sata3: main1:vm-100-disk-3,size=400G
sata4: main1:vm-100-disk-2,size=2500G
scsihw: virtio-scsi-single
smbios1: uuid=7883d88e-3421-4287-bbda-23598f3bf1a0
sockets: 1
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
vga: qxl3
vmgenid: 6520b65a-1495-4147-9379-a55e1b6b5566
root@oliversimpson:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content vztmpl,iso,backup

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

lvmthin: main1
thinpool main1
vgname main1
content rootdir,images
nodes oliversimpson

lvmthin: main2
thinpool main2
vgname main2
content images,rootdir
nodes oliversimpson

root@oliversimpson:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 2.7T 0 disk
├─main1-main1_tmeta 252:19 0 15.9G 0 lvm
│ └─main1-main1-tpool 252:21 0 2.7T 0 lvm
│ ├─main1-main1 252:25 0 2.7T 1 lvm
│ ├─main1-vm--100--disk--0 252:26 0 2.4T 0 lvm
│ ├─main1-vm--100--disk--1 252:29 0 32G 0 lvm
│ ├─main1-vm--100--disk--2 252:30 0 2.4T 0 lvm
│ └─main1-vm--100--disk--3 252:31 0 400G 0 lvm
└─main1-main1_tdata 252:20 0 2.7T 0 lvm
└─main1-main1-tpool 252:21 0 2.7T 0 lvm
├─main1-main1 252:25 0 2.7T 1 lvm
├─main1-vm--100--disk--0 252:26 0 2.4T 0 lvm
├─main1-vm--100--disk--1 252:29 0 32G 0 lvm
├─main1-vm--100--disk--2 252:30 0 2.4T 0 lvm
└─main1-vm--100--disk--3 252:31 0 400G 0 lvm
sdb 8:16 0 2.7T 0 disk
├─main2-main2_tmeta 252:22 0 15.9G 0 lvm
│ └─main2-main2-tpool 252:24 0 2.7T 0 lvm
│ ├─main2-main2 252:27 0 2.7T 1 lvm
│ └─main2-vm--100--disk--0 252:28 0 2.4T 0 lvm
└─main2-main2_tdata 252:23 0 2.7T 0 lvm
└─main2-main2-tpool 252:24 0 2.7T 0 lvm
├─main2-main2 252:27 0 2.7T 1 lvm
└─main2-vm--100--disk--0 252:28 0 2.4T 0 lvm
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 1G 0 part /boot/efi
└─nvme0n1p3 259:3 0 237.5G 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 69.4G 0 lvm /
├─pve-data_tmeta 252:2 0 1.4G 0 lvm
│ └─pve-data-tpool 252:4 0 141.2G 0 lvm
│ ├─pve-data 252:5 0 141.2G 1 lvm
│ ├─pve-vm--100--disk--0 252:6 0 4M 0 lvm
│ ├─pve-vm--100--disk--1 252:7 0 128G 0 lvm
│ ├─pve-vm--100--disk--2 252:8 0 4M 0 lvm
│ ├─pve-vm--200--disk--0 252:9 0 4M 0 lvm
│ ├─pve-vm--200--disk--1 252:10 0 64G 0 lvm
│ ├─pve-vm--200--disk--2 252:11 0 4M 0 lvm
│ ├─pve-vm--101--disk--0 252:12 0 4M 0 lvm
│ ├─pve-vm--101--disk--1 252:13 0 32G 0 lvm
│ ├─pve-vm--101--disk--2 252:14 0 4M 0 lvm
│ ├─pve-vm--102--disk--0 252:15 0 4M 0 lvm
│ ├─pve-vm--102--disk--1 252:16 0 32G 0 lvm
│ ├─pve-vm--102--disk--2 252:17 0 4M 0 lvm
│ └─pve-vm--150--disk--0 252:18 0 32G 0 lvm
└─pve-data_tdata 252:3 0 141.2G 0 lvm
└─pve-data-tpool 252:4 0 141.2G 0 lvm
├─pve-data 252:5 0 141.2G 1 lvm
├─pve-vm--100--disk--0 252:6 0 4M 0 lvm
├─pve-vm--100--disk--1 252:7 0 128G 0 lvm
├─pve-vm--100--disk--2 252:8 0 4M 0 lvm
├─pve-vm--200--disk--0 252:9 0 4M 0 lvm
├─pve-vm--200--disk--1 252:10 0 64G 0 lvm
├─pve-vm--200--disk--2 252:11 0 4M 0 lvm
├─pve-vm--101--disk--0 252:12 0 4M 0 lvm
├─pve-vm--101--disk--1 252:13 0 32G 0 lvm
├─pve-vm--101--disk--2 252:14 0 4M 0 lvm
├─pve-vm--102--disk--0 252:15 0 4M 0 lvm
├─pve-vm--102--disk--1 252:16 0 32G 0 lvm
├─pve-vm--102--disk--2 252:17 0 4M 0 lvm
└─pve-vm--150--disk--0 252:18 0 32G 0 lvm
root@oliversimpson:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
main1 main1 twi-aotz-- <2.70t 0.00 0.17
vm-100-disk-0 main1 Vwi-aotz-- 2.44t main1 0.00
vm-100-disk-1 main1 Vwi-aotz-- 32.00g main1 0.00
vm-100-disk-2 main1 Vwi-aotz-- 2.44t main1 0.00
vm-100-disk-3 main1 Vwi-aotz-- 400.00g main1 0.00
main2 main2 twi-aotz-- <2.70t 0.00 0.17
vm-100-disk-0 main2 Vwi-aotz-- 2.44t main2 0.00
data pve twi-aotz-- <141.23g 63.31 3.21
root pve -wi-ao---- <69.37g
swap pve -wi-ao---- 8.00g
vm-100-disk-0 pve Vwi-aotz-- 4.00m data 14.06
vm-100-disk-1 pve Vwi-aotz-- 128.00g data 19.85
vm-100-disk-2 pve Vwi-aotz-- 4.00m data 1.56
vm-101-disk-0 pve Vwi-a-tz-- 4.00m data 14.06
vm-101-disk-1 pve Vwi-a-tz-- 32.00g data 35.17
vm-101-disk-2 pve Vwi-a-tz-- 4.00m data 1.56
vm-102-disk-0 pve Vwi-a-tz-- 4.00m data 14.06
vm-102-disk-1 pve Vwi-a-tz-- 32.00g data 35.55
vm-102-disk-2 pve Vwi-a-tz-- 4.00m data 1.56
vm-150-disk-0 pve Vwi-a-tz-- 32.00g data 50.10
vm-200-disk-0 pve Vwi-a-tz-- 4.00m data 14.06
vm-200-disk-1 pve Vwi-a-tz-- 64.00g data 39.58
vm-200-disk-2 pve Vwi-a-tz-- 4.00m data 1.56

1708735539976.png
 

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!