hello forum!
PVE 4.4.35
GRUB is booting but shortly after I have this PANIC:
![deadProxmox.jpeg deadProxmox.jpeg](https://forum.proxmox.com/data/attachments/8/8935-fc27ea0c5dc616528fddb718555e5e6f.jpg)
![deadProxmox2.jpeg deadProxmox2.jpeg](https://forum.proxmox.com/data/attachments/8/8936-d6f608df1ebd6ba01b469ca93749c60c.jpg)
emergency USB boot also stucking in some loop:
![deadProxmox3.jpeg deadProxmox3.jpeg](https://forum.proxmox.com/data/attachments/8/8937-b9afbf9950865f452bb3004543bdb5da.jpg)
I was cloning some not running VM from webinterface on another running vm, server got frozen on about 53% of cloning, then I'v seen it as on photo 2.
Questions:
1. What is this could be and how to fix it?
2. Luckely (I hope) I just moved from webinterface all VMs Disks to a separate HDD with "move" operation to local, ZFS, so if I plug this HDD to another installation would I be able to acess those VMs disks? Are they containers themselves? Or may I catch em up with corresponding newly built VMs and use as disks for them so they will be same as those vms on lost server?
3. Any other options plz?
Generally I'm using PVE as an advanced desktop with videocard passthrough to WIn and OSX vms. Also I did not boot it till yesterday since few months...
everything was working for about a year and I was about to update and discover how to add a clustered mirror next week... was just ordering same h/w for this - well, hope its not too late
My *ss is on fire!!!
plz help )
PVE 4.4.35
GRUB is booting but shortly after I have this PANIC:
![deadProxmox.jpeg deadProxmox.jpeg](https://forum.proxmox.com/data/attachments/8/8935-fc27ea0c5dc616528fddb718555e5e6f.jpg)
![deadProxmox2.jpeg deadProxmox2.jpeg](https://forum.proxmox.com/data/attachments/8/8936-d6f608df1ebd6ba01b469ca93749c60c.jpg)
emergency USB boot also stucking in some loop:
![deadProxmox3.jpeg deadProxmox3.jpeg](https://forum.proxmox.com/data/attachments/8/8937-b9afbf9950865f452bb3004543bdb5da.jpg)
I was cloning some not running VM from webinterface on another running vm, server got frozen on about 53% of cloning, then I'v seen it as on photo 2.
Questions:
1. What is this could be and how to fix it?
2. Luckely (I hope) I just moved from webinterface all VMs Disks to a separate HDD with "move" operation to local, ZFS, so if I plug this HDD to another installation would I be able to acess those VMs disks? Are they containers themselves? Or may I catch em up with corresponding newly built VMs and use as disks for them so they will be same as those vms on lost server?
3. Any other options plz?
Generally I'm using PVE as an advanced desktop with videocard passthrough to WIn and OSX vms. Also I did not boot it till yesterday since few months...
everything was working for about a year and I was about to update and discover how to add a clustered mirror next week... was just ordering same h/w for this - well, hope its not too late
My *ss is on fire!!!
plz help )
Last edited: