Search results

  1. L

    Manually delete old nodes from cluster?

    Can anyone double confirm that "pvecm expected 1" works for this?
  2. L

    Manually delete old nodes from cluster?

    I did see those notes. Only problem is that if i do poweroff before removal i'm not in quorum anymore so I am stuck not being able to remove the node. Would be great if that command works. Scared to try it without confirmation
  3. L

    Manually delete old nodes from cluster?

    I haven't, are there instructions on how to do so?
  4. L

    Manually delete old nodes from cluster?

    So, issue is now that I can't delete the nodes because the cluster is not in quorum without 3 nodes up. I have the following output with pvecm status: root@pve:~# pvecm status Quorum information ------------------ Date: Sat Aug 27 12:30:08 2016 Quorum provider: corosync_votequorum...
  5. L

    Manually delete old nodes from cluster?

    haha, that might be what i've done before...i'll take a look. Thanks. Other input is welcome ;)
  6. L

    Manually delete old nodes from cluster?

    Yes, but the nodes that I am attempting to remove are not in quorum anymore. They aren't able to communicate with the cluster anymore...
  7. L

    New Proxmox machine HDD not fully usable

    Ah, i was able to figure it out. I reformatted to ext3, do you know why Proxmox by default doesn't use the entire disk for local storage?
  8. L

    Manually delete old nodes from cluster?

    I remember doing this in the past, but can't quite find where I found how to do this. I know there was some conf file that i could go to to delete old nodes from and upon reboot they wouldn't show up in the GUI anymore. Essentially the node is not in quorum anymore with my cluster and I would...
  9. L

    New Proxmox machine HDD not fully usable

    Here is the size that I'm seeing within the Proxmox GUI. Before i had the dell node added to the cluster i was able to see an LVM-Thin storage on it which seemed to have the remaining size on it. But now that is not visible.
  10. L

    New Proxmox machine HDD not fully usable

    Hi All, I use local storage for some intensive VMs, since I don't have a robust enough storage system yet. I currently just installed proxmox on a new-to-me Dell R620. I am using 146GB drives in a RAID1 and the installer detected them as such. But now that i've joined this machine to my...
  11. L

    [SOLVED] Clonezilla Remote --> Local issues

    Looks as though the issue is resolved with a "-fsck-src-part-y" when saving the image. I was able to save the image to my nfs share and then am restoring from that currently.
  12. L

    [SOLVED] Clonezilla Remote --> Local issues

    Not sure how to do that, do you know if there are any guides on doing that?
  13. L

    Extremely High IOstat Figures, help diagnose?

    Looks as though it might have just been a bad VM, maybe got corrupt somehow. I migrated over a snapshot version of the VM to the host in question and it is working without a hitch. Sorry for the false alarm and thanks for the help.
  14. L

    Extremely High IOstat Figures, help diagnose?

    Is it possible to migrate/move the disk to a virtio disk type?
  15. L

    Extremely High IOstat Figures, help diagnose?

    I have 8 CPUs dedicated to this. Disk type is local IDE0 and qcow2. I'm attempting from a different mac mini and am getting much better results, so might be that the HDD is on its way out of something. I will do a bit more testing and let you know what i find. Even running it from my Shared...
  16. L

    Extremely High IOstat Figures, help diagnose?

    Hi All, I have recently put my plex server as a VM and am curious if i can get some help to figure out some issues i'm experiencing. When playing any file through the plex VM i'm getting extremely high IOstat figures: As you can see this is not going to work well, but it is the same system...
  17. L

    [SOLVED] Clonezilla Remote --> Local issues

    Well, i just blew out the clonezilla VM and was able to get it to go further this time, but i did get an issue with it actually pushing content over. Doing Disk --> Disk I get this error for both sda2 and sda3: This is on the destination VM. Should i be selecting partitions to copy over...