Can't delete unnecessary vm disk.

P

pant-dm

New Member
Apr 16, 2015
27
0
1
Hello!

I tried to clone a virtual machine in machine with number 138. Cloning was too long and I canceled cloning. However, in shared LVM storage stuck disk drive of the virtual machine vm-138-disk-1.raw and I can not delete it. The remove button is inactive. How can I remove this unnecessary disk.

With respect and hope for help, pant-dm.

Cantdelete.png

P.S.: proxmox 3.4. LVM storage connected to 5 nodes by multipath FC.
 
Last edited:
Hi pant-dm
Is the disk you can't delete the source of the starget of the clone ?
What is the output of pvesm list <myStorageName>

Manu
 
Thank you, for reply:)!

The output is:
Code: 
root@vnode3:~# pvesm list mainlvm
  /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sde: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sde: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 4096: Input/output error
mainlvm:vm-100-disk-1   raw 34359738368 100
mainlvm:vm-101-disk-1   raw 268435456000 101
mainlvm:vm-102-disk-1   raw 34359738368 102
mainlvm:vm-105-disk-1   raw 21474836480 105
mainlvm:vm-105-disk-3   raw 322122547200 105
mainlvm:vm-106-disk-1   raw 21474836480 106
mainlvm:vm-106-disk-2   raw 214748364800 106
mainlvm:vm-108-disk-1   raw 21474836480 108
mainlvm:vm-108-disk-3   raw 536870912000 108
mainlvm:vm-110-disk-1   raw 85899345920 110
mainlvm:vm-110-disk-2   raw 214748364800 110
mainlvm:vm-114-disk-1   raw 34359738368 114
mainlvm:vm-115-disk-1   raw 128849018880 115
mainlvm:vm-136-disk-1   raw 268435456000 136
mainlvm:vm-136-disk-2   raw 34359738368 136
mainlvm:vm-137-disk-1   raw 268435456000 137
mainlvm:vm-138-disk-1   raw 268435456000 138
mainlvm:vm-138-disk-2   raw 85899345920 138
root@vnode3:~#

P.S.: Input/Output error were before. Don't know does it affect the problem.
 
Last edited:
Are you able to see the cloned VM in the GUI ?
IIRC, you should in the hardware tab of the vm de attach the disk from the controller, and then delete the disk from there.
 
I interrupted cloning operation somewhere in the 70%. And the virtual machine 138 did not exist. However, the disc vm-138-disk-1.raw appeared and it was impossible to remove. I left the situation for a while and forget about it.
I recently created a virtual machine 138, and found that "unnecessary" drive. It takes a lot of space and I would really like to delete it.
 
I would try the following steps ( but please do it in a test environment before !! )
* remove the virtual machine with ID 138 ( a disk in PVE is always the child of a VM so it might confuse PVE)
* then retry to delete the disk
 
Thank you, manu, for your replies:).

Unfortunately, I can not now remove the virtual machine 138, it is almost "production".
Maybe there is some other way? After all, the machine 138 don`t use vm-138 disk-disk-1.raw.
138vmdisk.png
 
Thank you for having responded, udo.
Here the requested output of these commands:
Code: 
root@vnode3:~# root@vnode3:~# pvs
  /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sde: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 4096: Input/output error
  PV                                                  VG      Fmt  Attr PSize   PFree 
  /dev/mapper/360080e50002e4b3e00000afa519b131d       comnlvm lvm2 a--    8.00t  7.69t
  /dev/mapper/360080e50002e4b3e000010315301b07e-part1 mainlvm lvm2 a--    3.91t  1.31t
  /dev/sda3                                           pve     lvm2 a--  232.38g 16.00g
root@vnode3:~# vgs
  /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sde: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 4096: Input/output error
  VG      #PV #LV #SN Attr   VSize   VFree 
  comnlvm   1   5   0 wz--n-   8.00t  7.69t
  mainlvm   1  18   0 wz--n-   3.91t  1.31t
  pve       1   3   0 wz--n- 232.38g 16.00g
root@vnode3:~# lvs
  /dev/sdd: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdd: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sde: read failed after 0 of 4096 at 0: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sde: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sde: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611866624: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4804611923968: Input/output error
  /dev/sdh: read failed after 0 of 4096 at 4096: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 0: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796092956672: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 8796093014016: Input/output error
  /dev/sdi: read failed after 0 of 4096 at 4096: Input/output error
  LV            VG      Attr      LSize   Pool Origin Data%  Move Log Copy%  Convert
  vm-107-disk-1 comnlvm -wi-a----  16.00g                                           
  vm-107-disk-2 comnlvm -wi-a----  64.00g                                           
  vm-118-disk-1 comnlvm -wi-a----  80.00g                                           
  vm-119-disk-1 comnlvm -wi-ao---  80.00g                                           
  vm-123-disk-1 comnlvm -wi-a----  80.00g                                           
  vm-100-disk-1 mainlvm -wi-a----  32.00g                                           
  vm-101-disk-1 mainlvm -wi-a---- 250.00g                                           
  vm-102-disk-1 mainlvm -wi-a----  32.00g                                           
  vm-105-disk-1 mainlvm -wi-a----  20.00g                                           
  vm-105-disk-3 mainlvm -wi-a---- 300.00g                                           
  vm-106-disk-1 mainlvm -wi-a----  20.00g                                           
  vm-106-disk-2 mainlvm -wi-a---- 200.00g                                           
  vm-108-disk-1 mainlvm -wi-a----  20.00g                                           
  vm-108-disk-3 mainlvm -wi-a---- 500.00g                                           
  vm-110-disk-1 mainlvm -wi-a----  80.00g                                           
  vm-110-disk-2 mainlvm -wi-a---- 200.00g                                           
  vm-114-disk-1 mainlvm -wi-a----  32.00g                                           
  vm-115-disk-1 mainlvm -wi-a---- 120.00g                                           
  vm-136-disk-1 mainlvm -wi-ao--- 250.00g                                           
  vm-136-disk-2 mainlvm -wi-ao---  32.00g                                           
  vm-137-disk-1 mainlvm -wi-ao--- 250.00g                                           
  vm-138-disk-1 mainlvm -wi-a---- 250.00g                                           
  vm-138-disk-2 mainlvm -wi-ao---  80.00g                                           
  data          pve     -wi-ao--- 135.39g                                           
  root          pve     -wi-ao---  58.00g                                           
  swap          pve     -wi-ao---  23.00g                                       
root@vnode3:~# dmsetup ls --tree
mainlvm-vm--114--disk--1 (253:10)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
comnlvm-vm--119--disk--1 (253:26)
 └─360080e50002e4b3e00000afa519b131d (253:2)
    ├─ (8:128)
    ├─ (8:64)
    ├─ (8:96)
    └─ (8:32)
mainlvm-vm--108--disk--1 (253:12)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
comnlvm-vm--118--disk--1 (253:24)
 └─360080e50002e4b3e00000afa519b131d (253:2)
    ├─ (8:128)
    ├─ (8:64)
    ├─ (8:96)
    └─ (8:32)
mainlvm-vm--106--disk--2 (253:7)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--105--disk--3 (253:11)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
comnlvm-vm--123--disk--1 (253:25)
 └─360080e50002e4b3e00000afa519b131d (253:2)
    ├─ (8:128)
    ├─ (8:64)
    ├─ (8:96)
    └─ (8:32)
mainlvm-vm--106--disk--1 (253:6)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--105--disk--1 (253:5)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--110--disk--2 (253:9)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--110--disk--1 (253:8)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
pve-swap (253:20)
 └─ (8:3)
pve-root (253:0)
 └─ (8:3)
pve-data (253:21)
 └─ (8:3)
mainlvm-vm--138--disk--2 (253:27)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
comnlvm-vm--107--disk--2 (253:23)
 └─360080e50002e4b3e00000afa519b131d (253:2)
    ├─ (8:128)
    ├─ (8:64)
    ├─ (8:96)
    └─ (8:32)
mainlvm-vm--138--disk--1 (253:19)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--102--disk--1 (253:15)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
comnlvm-vm--107--disk--1 (253:22)
 └─360080e50002e4b3e00000afa519b131d (253:2)
    ├─ (8:128)
    ├─ (8:64)
    ├─ (8:96)
    └─ (8:32)
mainlvm-vm--137--disk--1 (253:18)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--101--disk--1 (253:16)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--136--disk--2 (253:28)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--108--disk--3 (253:13)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--136--disk--1 (253:17)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--115--disk--1 (253:14)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
mainlvm-vm--100--disk--1 (253:4)
 └─360080e50002e4b3e000010315301b07e-part1 (253:3)
    └─360080e50002e4b3e000010315301b07e (253:1)
       ├─ (8:112)
       ├─ (8:48)
       ├─ (8:80)
       └─ (8:16)
root@vnode3:~# cat /etc/pve/qemu-server/138.conf
agent: 1
bootdisk: virtio0
cores: 2
hotplug: disk,network,cpu,memory
memory: 4096
name: 1CBuxBD
net0: virtio=16:67:22:4B:84:0D,bridge=vmbr0,tag=220
numa: 1
ostype: l26
smbios1: uuid=3c89b283-a2d3-4413-9f29-960ceef0b8f0
sockets: 1
virtio0: mainlvm:vm-138-disk-2,size=80G
root@vnode3:~#
 
pant-dm said:
Thank you for having responded, udo.
Here the requested output of these commands:
Code: 
...
root@vnode3:~# lvs
  LV            VG      Attr      LSize   Pool Origin Data%  Move Log Copy%  Convert
...                                    
  vm-138-disk-1 mainlvm -wi-a---- 250.00g                                           
  vm-138-disk-2 mainlvm -wi-ao---  80.00g                                           
...

root@vnode3:~# cat /etc/pve/qemu-server/138.conf
agent: 1
bootdisk: virtio0
cores: 2
hotplug: disk,network,cpu,memory
memory: 4096
name: 1CBuxBD
net0: virtio=16:67:22:4B:84:0D,bridge=vmbr0,tag=220
numa: 1
ostype: l26
smbios1: uuid=3c89b283-a2d3-4413-9f29-960ceef0b8f0
sockets: 1
virtio0: mainlvm:vm-138-disk-2,size=80G
root@vnode3:~#
Click to expand...
Hi,
vm-138-disk-1 isn't open, so you can simply remove the disk via
Code: 
lvremove /dev/mainlvm/vm-138-disk-1
Normaly you have an entry in the VM-conf (unused0: ...).

Your missing device entrys are still strange. Do you have assinged (and deleted) iscsi/fc-Volumes to the node?

What is the output of
Code: 
ls -lsa /dev/mapper/
Udo
 
Thank you, udo :-)! Unnecessary disk has been successfully removed and the space was released :-)!

Here the output of command 'ls -lsa /dev/mapper/':
Code: 
root@vnode3:~# root@vnode3:~# ls -lsa /dev/mapper/
total 0
0 drwxr-xr-x  2 root root    620 Jul 16 16:45 .
0 drwxr-xr-x 18 root root   7040 Jul  9 15:57 ..
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 360080e50002e4b3e00000afa519b131d -> ../dm-2
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 360080e50002e4b3e000010315301b07e -> ../dm-1
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 360080e50002e4b3e000010315301b07e-part1 -> ../dm-3
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 comnlvm-vm--107--disk--1 -> ../dm-22
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 comnlvm-vm--107--disk--2 -> ../dm-23
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 comnlvm-vm--118--disk--1 -> ../dm-24
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 comnlvm-vm--119--disk--1 -> ../dm-26
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 comnlvm-vm--123--disk--1 -> ../dm-25
0 crw-------  1 root root 10, 61 Jul  9 10:12 control
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 mainlvm-vm--100--disk--1 -> ../dm-4
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--101--disk--1 -> ../dm-16
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--102--disk--1 -> ../dm-15
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 mainlvm-vm--105--disk--1 -> ../dm-5
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--105--disk--3 -> ../dm-11
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 mainlvm-vm--106--disk--1 -> ../dm-6
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 mainlvm-vm--106--disk--2 -> ../dm-7
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--108--disk--1 -> ../dm-12
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--108--disk--3 -> ../dm-13
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 mainlvm-vm--110--disk--1 -> ../dm-8
0 lrwxrwxrwx  1 root root      7 Jul  9 10:13 mainlvm-vm--110--disk--2 -> ../dm-9
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--114--disk--1 -> ../dm-10
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--115--disk--1 -> ../dm-14
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--136--disk--1 -> ../dm-17
0 lrwxrwxrwx  1 root root      8 Jul  9 15:57 mainlvm-vm--136--disk--2 -> ../dm-28
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 mainlvm-vm--137--disk--1 -> ../dm-18
0 lrwxrwxrwx  1 root root      8 Jul  9 10:20 mainlvm-vm--138--disk--2 -> ../dm-27
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 pve-data -> ../dm-21
0 lrwxrwxrwx  1 root root      7 Jul  9 10:12 pve-root -> ../dm-0
0 lrwxrwxrwx  1 root root      8 Jul  9 10:13 pve-swap -> ../dm-20
root@vnode3:~#
 
Hi, i´m having the same problem, but i have a Dell R720 with a PCI2nmve adaptor, i´m getting the FAILED to import ZFS SSD2TB when booting proxmox, i´ve read in this post that is a normal error or timeout when boot, then when proxmox load, the datastore works ok...

i did a qm importdisk (converting from hyper-v vhd files) but it failed, and now i have my 2TB nvme (SSD2TB) almost full, and when i try to remove the ghost disk from GUI it says that the VM exists yet.

when i do a
CSS: 
cd /
cd /SSD2TB

ls -lh is empty...

i dont know what else to do...

Right now i´m waiting for a full backup to my NAS mount (3 hours left or so)... then i will delete my SSD2TB zfs pool, and then i will create again the same datastore... and then i will restore my 3 VM´s from my NAS mount...

I´m running out of ideas...

Any help will be appreciated :)

Thanks
 
Last edited:
You must log in or register to reply here.
Top Bottom