Search results

  1. J

    [quorum] crit: quorum_initialize failed: 2

    Hi, No worries, these thing happens. Not really, nothing heavy running. We do have a Gitlab server running on that spesific node but that never cuased any issues. It was running on a pve5 node but was migraed to the new pve6 node. Is there perhaps other logs I can have al ook at and send them...
  2. J

    [quorum] crit: quorum_initialize failed: 2

    Hi, Here is the output, couldn't find the "/etc/pve/ceph.conf" file on any of the cluster nodes: (Below is what I did find) root@ponder:~# cat /etc/pve/ceph.conf cat: /etc/pve/ceph.conf: No such file or directory root@ponder:~# locate ceph.conf /usr/lib/tmpfiles.d/ceph.conf root@ponder:~#...
  3. J

    [quorum] crit: quorum_initialize failed: 2

    Hi, Here is the output of "journalctl -u corosync.service" : root@ponder:~# journalctl -u corosync.service -- Logs begin at Sun 2019-10-20 09:13:32 SAST, end at Mon 2019-10-21 08:33:53 SAST. -- Oct 20 18:13:55 ponder corosync[1202]: [KNET ] link: host: 1 link: 0 is down Oct 20 18:13:55...
  4. J

    [quorum] crit: quorum_initialize failed: 2

    Hi, One of the 5 nodes (recently added to the cluster) started with this error: [quorum] crit: quorum_initialize failed: 2 Here is the output of "journalctl -xe" : Oct 20 18:42:55 server pmxcfs[1193]: [quorum] crit: quorum_initialize failed: 2 Oct 20 18:42:55 server pmxcfs[1193]: [confdb]...
  5. J

    SMART error (FailedOpenDevice) detected on host

    Hi, I'm using pve5 currently and no raid configured. What I suspect it was, I copied data and installed a external hdd and that was a WD HDD. Funny that the S.M.A.R.T tools is still picking up that the drive is still present? Thanks.
  6. J

    SMART error (FailedOpenDevice) detected on host

    Hi, So this is almost the same as my previous post but the only thing is, I don't have a Western Digital HDD installed on this node but a SSD, which means S.M.A.R.T sending false positives? There wasn't even a Western Digital HDD plugged into the node at all. What can I do to resolve this...
  7. J

    SMART error (CurrentPendingSector) detected on host

    Hi, HDD replaced and issues sorted. Thanks.
  8. J

    kWorker running at 100% constantly

    Hi, Thanks, switched to pve6 ans so far so good. Much appreciated.
  9. J

    SMART error (CurrentPendingSector) detected on host

    Thanks for the update, yes it's a production nodeo_O
  10. J

    kWorker running at 100% constantly

    Hi, A lot of people experiencing the kWorker running at 100% constantly, upgraded to a couple of different kernel versions especially "Linux 4.15.8-20-pve" but still doing the same. The main cause of this issue is when lxc is restarted. We are in progress of testing PVE6 to see if the issue...
  11. J

    SMART error (CurrentPendingSector) detected on host

    Hi, We have a cluster of 5 nodes and from the 1 node and for the last 2/3 days we're been getting this error: (Running PVE5.2 on all of the nodes) ===== This message was generated by the smartd daemon running on: host name: server DNS domain: domain.tld The following warning/error was...
  12. J

    Can't shell into a node via GUI

    Hi, What have you done to fix this. Thanks.
  13. J

    Resize VM disk via Proxmox

    Hi, Thanks, it worked perfect, used this link as well. Much appreciated.
  14. J

    Resize VM disk via Proxmox

    cool, thanks I will try it and revert back if I still experience any issues.
  15. J

    Resize VM disk via Proxmox

    okay but I followed this steps in the link send but still shows the original size of the disk (maybe I did something wrong), what can I do to fix this. Must I post any outputs of my system here?
  16. J

    Resize VM disk via Proxmox

    yes, updated 16.04 (what do you mean wit hthe new dis information) and using lvm yes.
  17. J

    Resize VM disk via Proxmox

    Running ubuntu 16.04.
  18. J

    Resize VM disk via Proxmox

    Hi, I tried increasing the VM's disk via Proxmox but it still stays the same, what can I do to fix this. Thanks in advance.
  19. J

    Insufficient free space: XXX extents needed, but only 0 available

    Hi, I'm trying to run this command but geting this error: Command: lvresize --size +100% --resizefs /dev/mapper/pve-root, Error: Insufficient free space: XXX extents needed, but only 0 available Running ProxMox 5.1 and the lvm disk size is only 120GB and want to increase it to use the who dis...
  20. J

    vma_queue_write: write error - Broken pipe

    Hi, Is there no other way to increase the size of the disk without installing any software to increase it, like apt install <software>, like on proxmox webgui? Why does proxmox only create a 100gb HDD when installing, probably shouldi've changed it myself? The machine does have a TB HDD...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!