Search results

The kernel does not detect the hard drive. Solution: bug grub2-probe -d /root/centos/root cfdisk /dev/sda #change type to "Linux LVM" bug not detect the hard drive. copy debian bullseye kernel # prepare files root@et089601:# cd /lib/modules/ root@et089601:/lib/modules# tar -cvf...

The OVA contains a CentOS 7 with kernel 3.10. The import of the OVA works correctly. qm importovf 612 ACR4_2_6.ovf local-lvm --format qcow2 WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set activation/thin_pool_autoextend_threshold below 100 to...

Hello, I think I found out why: Before adding this node to the cluster, I added a node that had a different configuration. After that, it wouldn't let me add more nodes. I think it was because of this partition that the node pve-ajt-05 had and they didn't have the others (lvmthin: local-1T)...

After several tests I no longer get the error. Now I need to start the normal grub menu. open systemrescuecd usb : e2fsck -ff /dev/pve/root resize2fs /dev/pve/root 95G # size 96G - 1G lvreduce -L -1G /dev/pve/root modprobe efivarfs mount /dev/mapper/pve-root /mnt mount -t proc proc /mnt/proc...

After several tests I no longer get the error. Now I need to start the normal grub menu. open systemrescuecd usb : e2fsck -ff /dev/pve/root resize2fs /dev/pve/root 95G # size 96G - 1G lvreduce -L -1G /dev/pve/root modprobe efivarfs mount /dev/mapper/pve-root /mnt mount -t proc proc...

Help me. I did not turn on the proxmox server. I have only been able to access by chroot from the systemrecuecd. * Error Grub: error disk 'lvmid/XyYOqp-wfj3-zsZC-s1d4-...' . Entering rescue mode... * Error install grub: grub-probe --device /dev/pve/root grub-probe: error: no s'ha trobat el...

Help me. I did not turn on the proxmox server. I have only been able to access by chroot from the systemrecuecd. * Error Grub: error disk 'lvmid/XyYOqp-wfj3-zsZC-s1d4-...' . Entering rescue mode... * Error install grub: grub-probe --device /dev/pve/root grub-probe: error: no s'ha trobat el...

root@pve-ajt-11:~# pvecm delnode pve-ajt-03 error with cfs lock 'file-corosync_conf': got lock request timeout

de gen. 22 18:01:27 pve-ajt-11 pmxcfs[1321]: [status] crit: cpg_send_message failed: 6 de gen. 22 18:01:28 pve-ajt-11 corosync[1573]: [TOTEM ] Token has not been received in 4565 ms de gen. 22 18:01:28 pve-ajt-11 pmxcfs[1321]: [status] notice: cpg_send_message retry 10 de gen. 22 18:01:29...

de gen. 22 17:59:17 pve-ajt-11 pmxcfs[1321]: [status] crit: cpg_send_message failed: 6 de gen. 22 17:59:17 pve-ajt-11 pmxcfs[1321]: [status] notice: cpg_send_message retried 100 times de gen. 22 17:59:17 pve-ajt-11 pmxcfs[1321]: [status] notice: cpg_send_message retry 100 de gen. 22 17:59:16...

* root@pve-ajt-04:~# systemctl status pvesr.service pvesr.service - Proxmox VE replication runner Loaded: loaded (/lib/systemd/system/pvesr.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-12-12 09:24:01 CET; 15s ago Process: 12204...

I have 4 nodes in proxmox 6.1. Trying to add one more does not work. root@pve-ajt-04:~# pvecm add 172.20.10.61 Please enter superuser (root) password for '172.20.10.61': ****** Establishing API connection with host '172.20.10.61' The authenticity of host '172.20.10.61' can't be established...

Fixed outdated kernel to version 4.10.17-5 root@pve-xxx-yy:~# aptitude install pve-kernel-4.10.17-5-pve root@pve-xxx-yy:~# vi /boot/grub/grub.cfg root@pve-xxx-yy:~# reboot ... root@pve-xxx-yy:~# uname -a Linux pve-xxx-yy 4.10.17-5-pve #1 SMP PVE 4.10.17-25 (Mon, 6 Nov 2017 12:37:43 +0100) x86_64...

Fixed back kernel to version 4.10.17-5 root@pve-xxx-yy:~# aptitude install pve-kernel-4.10.17-5-pve root@pve-xxx-yy:~# vi /boot/grub/grub.cfg root@pve-xxx-yy:~# reboot ... root@pve-xxx-yy:~# uname -a Linux pve-xxx-yy 4.10.17-5-pve #1 SMP PVE 4.10.17-25 (Mon, 6 Nov 2017 12:37:43...

Hello, Did a clean/fresh install of teh PVE 5.2 iso. Started restoring the kvms and containers. VMs restored fine. Container "appeared" to restore fine. However when I go to start the container: command 'systemctl start pve-container@100' failed: exit code 1 Log: root@pve:/# lxc-start -n 110...