Search results

I tried that, but the problem persisted. I' marking the thread as solved , weirdest hardware malfunction i ever saw. Thanks!

This can be marked as "solved" , since whatever suggestions may appear i won't be able to implement them. I searched other threads with from users that wanted to do something similar, they were referred to an outside KB article on how to resize LVM storage, i tried the tutorial and it messed up...

Hi , this can be marked as solved, i turns out it's a problem in the CPU, from one moment to another this feature stopped working. I tested this CPU on another machine (i am migrating to another chassis), the problem appeared there two. I tested another CPU on this node and the problem went away.

So this is my storage: I am not using "local" or "local-lvm" for anything, they were created by the proxmox install when i choose EXT4. Local is 100G, the only thing i used it for was to store an ISO file, the space is very underutilized and i dont have any option to remove or destroy it...

Hi there, I have two Lenovo M900 Tiny running as a cluster. Each of them has 1 NVME M2 512GB SSD where i installed Proxmox, formated and partitioned automaticaly by the installler. 1 SATA M2 512GB SSD Running a ZFS POOL (with the same name on both hosts) - Called ZFS_SSD 1 SATA 4TB HDD also...

Help?

I gathered more debugs that were requested in older threads of users having this issue, in those threads the problem went away and the root cause was not found. LSMOD | GREP KVM + UNAME -R for both nodes: root@node1:~# lsmod | grep kvm kvm_intel 286720 0 kvm...

Hi there, i reinstalled both servers, rebuilt the cluster, re-integrated the QIDevice (a RasperryPI 1) and i was hopping the problem would go away with a fresh install. It didn't. Both machines are identical , both have the same configuration on the BIOS and both are running the latest BIOS...

Node2: root@node2:~# cat /etc/corosync/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: node1 nodeid: 1 quorum_votes: 1 ring0_addr: 192.168.1.22 } node { name: node2 nodeid: 2 quorum_votes: 1 ring0_addr: 192.168.1.23 } }...

Node1: root@node1:~# cat /etc/corosync/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: node1 nodeid: 1 quorum_votes: 1 ring0_addr: 192.168.1.22 } node { name: node2 nodeid: 2 quorum_votes: 1 ring0_addr: 192.168.1.23 } }...

Node2: proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve) pve-manager: 7.1-5 (running version: 7.1-5/6fe299a0) pve-kernel-5.13: 7.1-4 pve-kernel-helper: 7.1-4 pve-kernel-5.11: 7.0-10 pve-kernel-5.4: 6.4-6 pve-kernel-5.13.19-1-pve: 5.13.19-2 pve-kernel-5.11.22-7-pve: 5.11.22-12...

Hi , i see, the Rasperry Pi is out of service for a while now, and i think i had already rebooted both nodes after the PI being out. But it's the most verbose error the node1 gives on boot, and when it finishes booting the node2 reboots sponaneously. Node 1 proxmox-ve: 7.1-1 (running kernel...

Sorry about it being in PDF , the attach function wouldn't let me attach RTF documents. About the corosync issues on the LOGs i use a Rasperry Pi as QiDevice and it malfunctioned, i already reinstalled everything but the instructions i used before no longer work, i get a permission error when...

They were running the same kernel: root@node1:~# uname -r 5.11.22-7-pve root@node2:~# uname -r...

Hi there, I have two Hosts Lenovo M900 Tiny with an Intel I7 6700T with VT-D enabled on the BIOS. Both running Virtual Environment 7.0-14+1 One of the hosts, after a reboot started showing "internal error" on the VM's, and on the Syslog showed "KVM internal error. Suberror: 1 / emulation...

I tried to follow recommendations on https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node: 6.5. Recovery If you have major problems with your Proxmox VE host, e.g. hardware issues, it could be helpful to just copy the pmxcfs database file /var/lib/pve-cluster/config.db...

Host 2 , alone in it's cluster missing Host 1: Host1 , all storage configured, not running VM's, running as stand alone: Host 1 , having the VM's HDD's all ready and accessible: Host2, having all the information to get Host1 back running: root@node2:/etc/pve/nodes/node1# ls -l...

Hi, i found outside the forum: zpool import -f -d /dev/sdX PoolName root@node1:/# zpool import -f -d /dev/sdb1 ZFS_SSD root@node1:/# zpool import -f -d /dev/sda1 ZFS_HDD I now have the pools added and i can see the VM's disk's on them. Now, at this point, i could start to recreate the VM's...

Hi there, I had a working cluster with two hosts and HA using a Rasperry PI as a QI Device. Host 1 boot drive failed (i use a USB as a boot drive, something i learned here on the forum is risky and i am waiting for hardware to change it). I have now Host 2 and the QI Device running, and i...

Had the same problem, this worked , in my case it was SMB/CIFS, not NFS. The copy on STEP 5 took 7 hours in my case.