Search results

I have a cluster with 3 nodes. Each node has 2 drives. first 2TB HDD and a second 500GB SSD. Proxmox installed on 2TB and LXC containers on SSD. Rebooted one node today since then containers don't start. root@R020:/var/lib/lxc/157# zfs list NAME USED AVAIL...

All the 6 failed containers give the same error Job for pve-container@107.service failed because the control process exited with error code. See "systemctl status pve-container@107.service" and "journalctl -xe" for details. TASK ERROR: command 'systemctl start pve-container@107' failed: exit...

@Alwin Any possible fix for this issue?

I have upgraded a production server from 5.1 to 5.2 on yesterday. I had 7 active containers. after the upgrade and reboot kernel changed from 4.15.3-1 to 4.15.17-1 Since then I couldn't start 6 of my 7 containers. Survived one was on first drive local-zfs. 6 failed containers were on the second...

I have upgraded a production server from 5.1 to 5.2 on yesterday. I had 7 active containers. after the upgrade and reboot kernel changed from 4.15.3-1 to 4.15.17-1 Since then I couldn't start 6 of my 7 containers. Survived one was on first drive local-zfs. 6 failed containers were on the second...

Bluescreen was an occasional guest on windows 2003 with old virtio. But windows 2012 or 2016 with Virtio 0.1.141 is a charm. Didn't see any Blue screen error on Windows 2012 and 2016 with vrtio 0.1.141 By the way, I didn't use proxmox 4.x , jumped from 3.4 to 5.1