Search results

Can confirm. Not sure if I have my scripts to automate the process around anymore. Please let me know if I should dig for them.

Hi @Soulgriever The easiest would be a shortcut to the web-gui of Proxmox and do your restarts from there, but alternately look into plink (a putty tool) that if you create a keypair should be able to pass the qm stop X and qm start X commands for you...

Hi Tom, I am aware of the proper version upgrade procedure, however I am questioning if I should have been warned about apparent dependencies when installing solely the newer patched pve-qemu-kvm package. Please re-read my post.

Hi all, We ran an apt-get update; apt-get install pve-qemu-kvm across a few client servers, but did not reboot. A client server had just started after a planned power outage and No vms would start due to error: detected old qemu-kvm binary (unknown) A dist-upgrade brought it back, but...

Hi Shutt1e. I've written a script, but am awaiting further input before I release it to you all, All the commands are the same as outlined here http://forum.proxmox.com/archive/index.php/t-20912.html hope that helps you in the meantime! Cheers, Quentin Pidduck.

Hi Nickgr, Without seeing this post i've been through the same, and come to the same method of replacing disks. I've mostly written a script to make this easy for all I just need a bit of input about how best to address disks (using /by-id/ata... or /by-id/scsi...)...

Initial tests are still working well, but i need a bit of input. Our servers recognise hdd's as sda,sdb,sdc etc. I know old IDE based systems use hdX What other drive identifiers should I include? Also our servers report multiple instances of a Sata disk in /dev/disk/by-id because of scsi...

Working on something now. Looking very promising.

I'll have to do some testing then. Would Proxmox benefit from a script that assists users in introducing a new disk into a broken ZFS Raid-1 installation then running everything required to bring it to a bootable state?

Unsure sorry, Proxmox is my platform of choice. SWAP partitions and rolling log files are across the board for debian linux though, so i'd not be surprised if a linux based VMware instance had the same issue.

Without specifics I would encourage the use of umount <local path> then mounting again thought th egui with your new parameters.

Thanks for the quick reply, Any thoughts on the EFI-System-Partition on both original disks and how best to recreate that on a replacement disk?

I don't reccomend usb install unless you are running your SWAP partiton and logs directory off more reliable storage. The constant writes to these directores can kill your USB very quickly (Within a couple of days.) Thanks.

Grub is the default for that set-up yes, but I disagree your approach is the best way to handle this. 1) If I install Proxmox in the ZFS raid 1 and spend most the server's life booting from and upgrading software on /dev/sda (or bios preferred boot device) would this not mean I have to...

Hi team, We've (prior to 3.4) had out Proxmox OS's on a separate SSD and the Data managed by a Hardware raid controller. The concept of a ZFS raid one install is appealing as if helps us out of a tricky spot if we have a failure with the single SSD. Initial testing has shown that selecting ZFS...

Usually my files don't have a space between the c and the 0 when referencing the registry path... Is this intentional in your example for any reason?

Situation We belive due to an older SEABIOS version in Proxmox our Windows VM's 7 + 2008 servers have the ability to 'Safely remove' critical hardware like the disk and network cards. This is down to the Seabios having hot-swappable PCI enabled. Could be related to " BZ#671544 On a...