Search results

Thanks for summarizing back to the thread - glad to hear that this was possible / to make your config more solid. I agree that mdadm linux raid via 'custom install' feels complex compared to any version of the 'appliance install of proxmox' - especially if you are not familiar with doing linux...

Possible solution? (a) Buy a new hard drive outright to replace the failing drive (b) remove and replace; let rebuild complete (c) return bad part under warranty, and eventually get a replacement back in the mail (d) now you have a cold-spare drive on hand for quick and easy use the next time a...

Hi, it is good question. I haven't done ZFS with proxmox other than basic test appliance based (simple mirror disk set) install ~last year on a throwaway test box. Quick google, I find discussion-howtos such as, https://github.com/zfsonlinux/zfs/wiki/Debian-Jessie-Root-on-ZFS which appear to...

Hi, umm, footnote. "Building Proxmox on top of Jessie is time consuming" - maybe the first time, it takes longer than a pure appliance install, but it is still <1 hour of effort. If you follow the hints, carefully, as per wiki: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie -...

Hi, just to mention, just because the system does not have nice 'hot swap easy remove sleds' does not inherently mean the system can't support hot-plugging disks, ie, - rip open case while it is powered up - un-cable the bad drive - remove it physically, assuming screws are not inaccessible...

Hi, FYI, Proxmox on Linux SW Raid MDadmin works just fine, if you do install in proper sequence, ie, - first install your bare metal host with Debian Jesse installer, minimal boot ISO to do the install is just fine. - be very attentive to hints provided...

Hi, just a few thoughts, - it is hard to make a compelling argument / key points if we don't know what your core requirements are for your deployment config. (ie, can't address key points if we don't know what they are ?) - end of the day, if you are doing a 'very simple virtualization' setup...

Hi, I don't think Proxmox will allow you to designate, "Write backups to STORAGE_1 until it is full, then go to STORAGE2, then storage3, etc". So your options, maybe? -- build a single raid volume composed of (disk 2,3,4) to give you a single pool of storage space. Or LVM if you prefer. or ZFS...

Hi, I think there is something in communication here between your posts and my posts, which suggests that we are not understanding each other. - if your setup looks like this? - two physical systems - one system is running proxmox, had local storage for VMS to run from - one system is running...

Hi, not sure I'm understanding, but ? - 2 physical interfaces on proxmox, eth0 and eth1 - setup 2 bridges, vmbr0<>eth0 and vmbr1<>eth1 - cable eth0 to subnet1 and eth1 to subnet2 - bridge your VM interfaces to the subnet(s) you wish them to have access to. Assign IPs suitably to the interfaces...

Hi, I'm unclear, if you have still a problem; or if you resolved this ? For what it is worth, I've done similar-ish thing in past, more or less thus, -- assume we have at least 2 x physical interface on the proxmox host -- configure 2 x vmbr; one bound to each physical interface -- assume we...

Hi, is it sufficient to install snmpd on your proxmox/ceph nodes; then setup cacti (on a VM ?) and poll for this data and graph it ? Tim

Hi, my advice would be, - don't change the internal storage on proxmox you use for VMs that are active - instead just add a new storage pool, NFS based, which is used only for holding your backups - if you have not done so already, review these docs, first briefly...

Hi, just to confirm; you were not originally using VirtIO-scsi inside your guest, now you are, and performance improved "significantly" but you wonder if can make better still ? My guess is that - you probably are not going to get too much better than where you have it now. (85+MB/s writes...

Hi, just to chime in. - This is doable, unplug the raid disks first is a good suggestion to avoid 'oops' during the clean install - to be extra safe, I would suggest you first run the day-or-two before hand, a no-downtime VM-dump-backup-everything-to-external-NFS-storage. Just in case things go...

Hi, just to join the chorus, - backup, clean install, restore - is definitely the safe path. - Just for giggles, I once did a test-box upgrade from 2>3>4 and .. I don't recommend it. - since you are using new clean HDDs for the new proxmox install, it is even easier, you can sort-of skip the...

My usual baseline comment here would be, 'why on earth complicate a simple / fairly small server config with ZFS" ? You lack sufficient RAM, CPU, DISK {no SSD for ZFS_Cache_ZIL etc} to really use ZFS in the way that (I think?) it will be of the greatest benefit. I would do a stock install...

For what it is worth, moving the client to something slightly newer than CentOS5 should be ~more or less straightforward and ~painless. My vague recollection is that moving services over from a CentOS 5.X box to a 6.X box is not really a big deal. At least not as much change as when compared to...

Hi, for what it is worth. I did a small proxmox on Cisco HW deploy a few years ago, everything was fine, except for the minor detail that the on-board LSI raid was the lowest-end-'nearly-but-not-quite-fakeraid' I have ever seen. The performance of IO was more or less horrible out of the box. I...

Hi, small fun question. Are you open to idea of spinning up another VM, possibly Linux of some kind / which is otherwise similar to the windows host (ie, resource allocation, same VM underlying storage etc) ? Reason I ask - is that in my experience, Win10 as an OS is sometimes "inconsistent as...