Hi All, new to Proxmox and I love it.
Trying to convert a raw disk to qcow2 so I can get snapshots working for this particular VM, the disk is on CIFS storage (Synology NAS), and I'm using the 'move disk' method in the web GUI to perform the conversion. I moved the TPM disk, and the EFI disk no problem, they're only a few MB in size. The main hard drive is 512GB in size, and when I start the 'disk move' operation, the Task Viewer window shows:
The system log in the Web GUI is flooded with:
I'm not sure if this is just what happens during a Move Disk operation, and I just have to wait for it to complete? Or is there a way to check status while the operation is ongoing besides the Task viewer? It's been running for over 20 minutes, I thought the conversion operation might be taxing the CPU, but the CPU usage on the node summary in Web GUI is less than 1%. The hardware on the Proxmox server itself is a Minisforum MS-01 with Intel 13900H 96GB ram. Any light shed on this would be appreciated.
Trying to convert a raw disk to qcow2 so I can get snapshots working for this particular VM, the disk is on CIFS storage (Synology NAS), and I'm using the 'move disk' method in the web GUI to perform the conversion. I moved the TPM disk, and the EFI disk no problem, they're only a few MB in size. The main hard drive is 512GB in size, and when I start the 'disk move' operation, the Task Viewer window shows:
And it stays on 0.00%.create full clone of drive scsi0 (VM-Disks:100/vm-100-disk-1.raw)
Formatting '/mnt/pve/VM-ISOs/images/100/vm-100-disk-1.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=549755813888 lazy_refcounts=off refcount_bits=16
transferred 0.0 B of 512.0 GiB (0.00%)
The system log in the Web GUI is flooded with:
Aug 27 17:38:49 proxmox pvestatd[1265]: unable to activate storage 'VM-Disks' - directory '/mnt/pve/VM-Disks' does not exist or is unreachable
Aug 27 17:38:59 proxmox pvestatd[1265]: got timeout
Aug 27 17:38:59 proxmox pvestatd[1265]: unable to activate storage 'VM-Disks' - directory '/mnt/pve/VM-Disks' does not exist or is unreachable
Aug 27 17:39:09 proxmox pvestatd[1265]: got timeout
Aug 27 17:39:09 proxmox pvestatd[1265]: unable to activate storage 'VM-Disks' - directory '/mnt/pve/VM-Disks' does not exist or is unreachable
Aug 27 17:39:19 proxmox pvestatd[1265]: got timeout
Aug 27 17:39:19 proxmox pvestatd[1265]: unable to activate storage 'VM-Disks' - directory '/mnt/pve/VM-Disks' does not exist or is unreachable
Aug 27 17:39:30 proxmox pvestatd[1265]: got timeout
Aug 27 17:39:30 proxmox pvestatd[1265]: unable to activate storage 'VM-Disks' - directory '/mnt/pve/VM-Disks' does not exist or is unreachable
Aug 27 17:39:35 proxmox kernel: CIFS: VFS: \\NAS1-10g1 has not responded in 180 seconds. Reconnecting...
Aug 27 17:39:39 proxmox pvestatd[1265]: got timeout
Aug 27 17:53:13 proxmox kernel: CIFS: VFS: \\NAS1-10g1 Send error in SessSetup = -11
Aug 27 17:53:13 proxmox pvestatd[1265]: unable to activate storage 'VM-Disks' - directory '/mnt/pve/VM-Disks' does not exist or is unreachable
Aug 27 17:53:13 proxmox pvestatd[1265]: status update time (52.635 seconds)
I'm not sure if this is just what happens during a Move Disk operation, and I just have to wait for it to complete? Or is there a way to check status while the operation is ongoing besides the Task viewer? It's been running for over 20 minutes, I thought the conversion operation might be taxing the CPU, but the CPU usage on the node summary in Web GUI is less than 1%. The hardware on the Proxmox server itself is a Minisforum MS-01 with Intel 13900H 96GB ram. Any light shed on this would be appreciated.
Last edited: