Unable to find VM Disk: Not a Directory

splnut

Active Member
Jan 21, 2020
1
0
41
40
My proxmox server died and I moved the 2 nvme drives to a new computer. Proxmox boots up just fine, but is unable to access any of the VM's or containers on my 2nd drive. Even when attempting to create a new container/vm on the 2nd drive, I get an error message:

kvm: -drive if=pflash,unit=1,id=drive-efidisk0,format=raw,file=/dev/nvme2/vm-100-disk-0,size=540672: Could not open '/dev/nvme2/vm-100-disk-0': Not a directory
TASK ERROR: start failed: QEMU exited with code 1

Code:
root@beelink:~# lsblk -l
NAME                   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
pve-swap               252:0    0     8G  0 lvm  [SWAP]
pve-root               252:1    0    96G  0 lvm  /
pve-data_tmeta         252:2    0   3.6G  0 lvm 
pve-data_tdata         252:3    0 348.8G  0 lvm 
nvme2-nvme2_tmeta      252:4    0   9.3G  0 lvm 
nvme2-nvme2_tdata      252:5    0 912.8G  0 lvm 
pve-data-tpool         252:6    0 348.8G  0 lvm 
pve-data               252:7    0 348.8G  1 lvm 
pve-vm--100--disk--0   252:8    0     4M  0 lvm 
pve-vm--108--disk--0   252:9    0     4M  0 lvm 
pve-vm--108--disk--1   252:10   0     4M  0 lvm 
pve-vm--102--disk--0   252:11   0     2G  0 lvm 
pve-vm--109--disk--0   252:12   0    32G  0 lvm 
pve-vm--109--disk--1   252:13   0     4M  0 lvm 
nvme2-nvme2-tpool      252:14   0 912.8G  0 lvm 
nvme2-nvme2            252:15   0 912.8G  1 lvm 
nvme2-vm--101--disk--0 252:16   0     4G  0 lvm 
nvme2-vm--102--disk--0 252:17   0     2G  0 lvm 
nvme2-vm--103--disk--0 252:18   0     8G  0 lvm 
nvme2-vm--100--disk--0 252:19   0    64G  0 lvm 
nvme2-vm--115--disk--1 252:20   0    10G  0 lvm 
nvme2-vm--112--disk--0 252:21   0    40G  0 lvm 
nvme2-vm--120--disk--0 252:22   0     4G  0 lvm 
nvme2-vm--116--disk--0 252:23   0    75G  0 lvm 
nvme2-vm--104--disk--0 252:24   0     3G  0 lvm 
nvme2-vm--105--disk--0 252:25   0     4G  0 lvm 
nvme2-vm--106--disk--0 252:26   0     4G  0 lvm 
nvme2-vm--107--disk--0 252:27   0    32G  0 lvm 
nvme2-vm--107--disk--1 252:28   0     4M  0 lvm 
nvme0n1                259:2    0 476.9G  0 disk
nvme0n1p1              259:3    0  1007K  0 part
nvme0n1p2              259:4    0     1G  0 part /boot/efi
nvme0n1p3              259:5    0 475.9G  0 part
nvme2n1                259:6    0 931.5G  0 disk

Code:
root@beelink:~# pvesm path nvme2:vm-100-disk-0
/dev/nvme2/vm-100-disk-0

Code:
dir: local
        path /var/lib/vz
        content backup,iso,vztmpl
        prune-backups keep-last=1
        shared 0

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

lvmthin: nvme2
        thinpool nvme2
        vgname nvme2
        content rootdir,images

Code:
Nov 19 05:48:39 beelink kernel: nvme nvme0: pci function 0000:02:00.0
Nov 19 05:48:39 beelink kernel: nvme nvme1: pci function 0000:0d:00.0
Nov 19 05:48:39 beelink kernel: nvme nvme2: pci function 0000:10:00.0
Nov 19 05:48:39 beelink kernel: nvme nvme1: missing or invalid SUBNQN field.
Nov 19 05:48:39 beelink kernel: nvme nvme1: Shutdown timeout set to 10 seconds
Nov 19 05:48:39 beelink kernel: nvme nvme1: 8/0/0 default/read/poll queues
Nov 19 05:48:39 beelink kernel: nvme nvme1: Ignoring bogus Namespace Identifiers
Nov 19 05:48:39 beelink kernel:  nvme1n1: p1
Nov 19 05:48:39 beelink kernel: nvme nvme0: 8/0/0 default/read/poll queues
Nov 19 05:48:39 beelink kernel:  nvme0n1: p1 p2 p3
Nov 19 05:48:39 beelink kernel: nvme nvme2: allocated 64 MiB host memory buffer.
Nov 19 05:48:39 beelink kernel: nvme nvme2: 8/0/0 default/read/poll queues