how to downgrade from 3.4 to 3.3

I

ioiioi

Member
Jun 19, 2014
17
0
21
hello, I have encounter a series problem.

originally, I just want to install ulogd packages, which lead to this result:

Code: 
 The following packages were automatically installed and are no longer required:
  ipset libipset2 libmnl0 libnetfilter-log1 novnc-pve
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  pve-kernel-2.6.32-45-pve
Suggested packages:
  ulogd-mysql ulogd-pgsql ulogd-pcap ulogd-sqlite3
The following packages will be REMOVED:
  proxmox-ve-2.6.32 pve-firewall pve-manager qemu-server
The following NEW packages will be installed:
  pve-kernel-2.6.32-45-pve ulogd
0 upgraded, 2 newly installed, 4 to remove and 121 not upgraded.
Need to get 37.2 MB/37.3 MB of archives.
After this operation, 95.2 kB disk space will be freed.


I am no brains to confirm and process, then the whole world crash. after I reboot, if I choose the pve-kernel-2.6.32-45-pve, boot failed. the whole screen is full of udevd timeout killing /sbin/modprobe.
if I choose the pve-kernel-2.6.32-34-pve, the proxmox could boot propertly, but miss pve-manager, qemu-server.
If I apt-get install qemu-server pve-manager, there is another problem.

so my question is : how to downgrade the proxmox 3.4 to proxmox 3.3

my pveversion command is missing too, so I can't tell you gay, which version I am currently on now.
 
well, there is little pve* command I could use
pvecm status

Version: 6.2.0
Config Version: 6
Cluster Name: idc
Cluster Id: 719
Cluster Member: Yes
Cluster Generation: 26540
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: proxmox1
Node ID: 2
Multicast addresses: 239.192.2.209
Node addresses: 192.168.77.29

addition:
this host is one of the two-node cluster, another one is working properly, and I have migrated the important vm to the other node.

the other node's pveversion:

proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-139
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
I know, I have apt-get purge ulogd immediately. but problem is still there, the new kernel seems imcompitable with my hp dl385 g8

when choose pve-kernel-2.6.32-45-pve, the system will hang on
udevd timeout killing /sbin/modprobe

any idea how to fix it?
 
I fixed it.

the reason was I added additional kernel boot options before when I installed 3.3. the default kernel is not compatible with hp dl385 g8, so I add "pci=noacpi noapic amd_iommu=on panic=20", after upgrade to 3.4, these options cause boot hang, after delete these options, 3.4 could boot successfully.
 
You must log in or register to reply here.
Top Bottom
Back