fail upgrade 1.9 to 2.1: similar situation

[JimBeam]

Hi all,

Experiencing similar problems to the other poster that tried to upgrade his custom 1.9 to 2.1

Upgrading an original Debian+later proxmox install from 1.9 to 2.0
Tried upgrade script, didn't work (not surprised, it only supports plain vanilla installs). Removed some checks, didn't work.
Ran it a couple of times; attached the latter part of the output.View attachment lastpartupgradelog.zip

Manually upgraded to Debian Squeeze.

Trying to follow
http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze
#installed kernel, headers...
Now I get problems with circular dependencies: pve-manager couldn't be configured
Tried removing migrated old config files
aptitude purge pve-cluster pve-kvm pve-manager pve-qemu-kvm

Reinstall, still get this circular config problem:

aptitude install proxmox-ve-2.6.32
...
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
                                      Setting up vzctl (3.0.30-2pve5) ...
Checking vzevent kernel module .....done
Starting vzeventd:
Starting OpenVZ: ..done
Bringing up interface venet0: ..done
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
 proxmox-ve-2.6.32 depends on pve-manager; however:
  Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      Errors were encountered while processing:
 pve-manager
 proxmox-ve-2.6.32
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up pve-manager (2.1-1) ...
Restarting PVE Daemon: pvedaemon.
Restarting PVE Status Daemon: pvestatd.
dpkg: error processing pve-manager (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
 proxmox-ve-2.6.32 depends on pve-manager; however:
  Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pve-manager
 proxmox-ve-2.6.32

pveversion --verbose
pve-manager: not correctly installed (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3

Can I clean out all Proxmox configuration and reinstall the proxmox packages, and how would I do that? apt-get purge didn't seem to do the trick..
Then I could either recreate the config files for the VMs on the local disks or restore some VMs from backup.
I do understand an OS reinstall is the recommended way, but I'm willing to keep fiddling a bit.

If possible, I'd rather not reinstall the host OS as I might wipe out the VMs on the other disks in the machine (home install)

Thanks!

 

[JimBeam]

Ok, bit the bullet, installed a new Debian Squeeze, then proxmox. Added the existing LVM volume group as storage, recreated /etc/network/interfaces with my bridge settings etc. Now fiddling with machine config creation/parameters to see if I can get back my VMs, otherwise restore from backup. So far so good & thanks for a great product!