Proxmox 4 Installation Issue on LSI Raid Systems Rumi, March 4, 2016 I was installing Proxmox 4.X on my new server systems having SAS disk with LSI MPT2 Raid controller. The installation went just perfect, however, after post installation boot- I was getting errors as below similar screenshot- After googling a lot, found the solution. Here goes it- On the initial boot screen- select “*Advanced…..” Hit “e” on the next screen You’ll find something similar as below- title Debian GNU/Linux, kernel 2.6.26-1-686 root (hd0,0) kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/sda1 ro quiet initrd /boot/initrd.img-2.6.26-1-686 add rootdelay=90 after quiet Hit “Ctrl+X” or F10. The boot will initiate and you;ll have the login prompt appears on screen. Success!!! Now, let’s make it permanent for the next boot. now open /etc/default/grub and add the following command- GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=90" Save it Now issue the command- update-grub Now time to reboot Problem resolved!!! Related Proxmox ProxmoxProxmox4
Fix Proxmox (PVE) “can’t lock file ‘/var/lock/qemu-server/lock-xxx.conf’ – got timeout” (Proxmox can’t shutdown/stop virtual machine) (Proxmox kill/force stop virtual machine) August 14, 2020 The Issue When trying to “Stop” or “Shutdown” virtual machine from Proxmox (PVE) web gui, the “Cluster log” shows end task UPID:pve:xxxxxxxx:xxxxxxxx:xxxxxxx:qmstop:xxx:root@pam: can’t lock file ‘/var/lock/qemu-server/lock-xxx.conf’ -got timeout end task UPID:pve:xxxxxxxx:xxxxxxxx:xxxxxxx:qmreboot:xxx:root@pam: VM quit/powerdown failed The Fix We can manually delete the lock from following path /run/lock/qemu-server # The file will… Read More
Force Stop Proxmox LXC November 21, 2020 First try to unlock the pct (assuming your troubled container is 101): pct unlock 101 if it works just stop and start again the vm. if it does’nt work (my case) try to stop with this lxc-stop –name 101 if it’s does’nt work (my case) you can force stop with… Read More