Recent content by Dolomike

  1. D

    Moving from RAID to Ceph in 3 node cluster - will this work?

    We'd like to get away from hardware RAID and move into distributed storage. I've been reading a number of posts regarding 3-node clusters with Ceph, how it's not ideal but I see that many people have implemented it without any issues and we'll add a 4th node sometime in the future, but I'd like...
  2. D

    Wipe and fresh install of 5.1 - Filesystem and drive config

    Unfortunately I don't have a 3rd node that's setup for storage so moving to Ceph won't happen right now. I'll have to revisit this when the shared storage will be implemented. For now it's running hardware RAID with various LVM pools.
  3. D

    Wipe and fresh install of 5.1 - Filesystem and drive config

    I've been a big Linux user for a long time and Proxmox for the past couple of years but I just haven't been keeping up on the various filesystems so I'm in need of some suggestions on how I should proceed with a fresh install. I've just received a bunch of new drives so not sure what the best...
  4. D

    [SOLVED] Creating a CT error: "Could not reserve ID XXXX, already taken"

    The only thing I can think of is that there is a file that Proxmox can't write to or that you actually have that id already taken. Check your vm config files and make sure that ID doesn't exist and that the correct permissions are set on the required config files.
  5. D

    upgrade proxmox 4.1 to 4.4 on Hp Proliants

    I have a DL380 G6 and G7 running 4.4. I did have a lockup the other day but that may have been from something else. Note, that I'm only running a two node cluster, no HA.
  6. D

    [SOLVED] Creating a CT error: "Could not reserve ID XXXX, already taken"

    The /etc/pve/corosync.conf file was un-writable so the cluster was "invalid" and for whatever reason this prevents new CT's from being created. I stopped the corosync service and switched to local only mode: service corosync stop pmxcfs -l I was then able to delete /etc/pve/corosync.conf...
  7. D

    [SOLVED] Creating a CT error: "Could not reserve ID XXXX, already taken"

    Hi, Yeah, I tried that yesterday as well but still the same result. It works fine on the "slave" node but not on the "master" node that I started the cluster process on. I'll see if I can get the cluster operational and report back.
  8. D

    [SOLVED] Creating a CT error: "Could not reserve ID XXXX, already taken"

    I recently attempted to join another Proxmox host into a cluster but ran into errors and wasn't able to complete the process so I left it for now but now when I attempt to create a container, I get the following error: TASK ERROR: Could not reserve ID XXXXX, already taken I've attempted a a...
  9. D

    Proxmox 3.4, OVS and Open VZ - 2 nics, 2 subnets

    Hello, I tried a while ago to get this working with Proxmox 3.3 but could never get things working right. I've just installed 3.4 and was hoping someone had a good example of using OVS and OpenVZ with two nics. I have two nics, each with their own subnet and gateway, would like to be able to...
  10. D

    Moving from two Openvz servers to one Proxmox - Setting up Networks

    I'm new to advanced networking so please bear with me. I believe you are saying I should do the following (based on what I've read on other posts): /etc/networking/interfaces #network interface settings auto lo iface lo inet loopback #Bridge for testing vlan network - vlan123 created on...
  11. D

    Moving from two Openvz servers to one Proxmox - Setting up Networks

    I've been managing two CentOS based OpenVZ servers for the past few years and I would like to consolidate the two physical servers into a single physical Proxmox managed server. The setup is currently this: -------- 192.168.120 subnet----- OpenVZ Server 1 Firewall ---<...