Error when trying to start a VM

[alex165]

Hi,

I am new to Proxmox and am running into an issue when i am trying to start my previously working Unraid VM. I added more cores and more memory to the VM, but when i went to start the VM again. I am getting "starting worker failed: unable to create output file '/var/log/pve/tasks/6/UPID:threadripper:00001856:0000A0E0:635F2816:qmstart:100:root@pa - Input/output error (500)
I tried to load into the shell and navigate to this log location, but the shell is not loading for me either.

In doing a bit of reading, it seems that there is an issue with the underlying storage ( a 1tb nvme) that was purchased less than a month ago.

I was thinking that 1tb nvme is too large for the install of proxmox. am i correct in this thinking? I have an HBA that is passed through to the Unraid VM and want to use Proxmox as the base OS for my lab, while keeping Unraid going at the same time.

Thanks in advance

 

[leesteken]

I was thinking that 1tb nvme is too large for the install of proxmox. am i correct in this thinking?

No that's not correct. Does the VM start when you undo your changes? Are there I/O errors in the system logs?

 

[alex165]

Thanks for the reply.

No the VM does not start when i change the settings back. When i open the task viewer for the VM, it says "TASK ERROR: no such logical volume pve/data" So i thought to go check the LVM under disks for the host and It says no volume groups found. I am not sure if that last part is helpful or not.

 

[leesteken]

No the VM does not start when i change the settings back. When i open the task viewer for the VM, it says "TASK ERROR: no such logical volume pve/data" So i thought to go check the LVM under disks for the host and It says no volume groups found. I am not sure if that last part is helpful or not.

It would appear that your virtual disks are missing, which would explain the VM not starting, and correlates with the I/O errors.

In doing a bit of reading, it seems that there is an issue with the underlying storage ( a 1tb nvme) that was purchased less than a month ago.

Sounds like you has a drive crash and your LVM is corrupt or lost some parts. I have no experience in recovering LVM volume groups and logical volumes, sorry.