[SOLVED] Proxmox not start after upgrade from v4.4 to v5.1

Hi,
what kind of filesystem do you use?

I had one machine, with zfs, where I must use rootdelay=5 as grub kernel option to boot successfull.

BTW. The usb install stick can be used for rescue-boot.

Udo

Hi Udo,

The server start but I can't connect him via WEB, the VM's and CT's not start either.

If I execute the "qm" command:

---------------------------------------------------------
# qm config 120 | grep ^vga ; echo $?
-bash: qm: command not found
1
#
---------------------------------------------------------

Not work.

If I execute the "pct" command not work either:

---------------------------------------------------------
# pct start 100
-bash: pct: command not found
#
---------------------------------------------------------

I unknow what happen...


Regards,

Ramses
 
Hi everyone,

I have solved the problem installing the PROXMOX package:

apt install proxmox-ve postfix open-iscsi

I think that postfix and open-iscsi packages were installed previously and was not necessary install it again.


Regards,

Ramses
 
Hi everyone,

I have solved the problem installing the PROXMOX package:

apt install proxmox-ve postfix open-iscsi

I think that postfix and open-iscsi packages were installed previously and was not necessary install it again.


Regards,

Ramses
Hi,
i was have the same problem but with this command:
apt install proxmox-ve postfix open-iscsi

I can fix and now i can access in miip:8006

but have the error with network failure.

So following this: https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0

i used:
apt-get -fy install

but don't work any VM. @ramses @fireon @udo

Any can help me?


root@server:~# pveversion -v
proxmox-ve: 5.1-38 (running kernel: 4.4.98-5-pve)
pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.4.19-1-pve: 4.4.19-66
pve-kernel-4.4.49-1-pve: 4.4.49-86
pve-kernel-4.4.15-1-pve: 4.4.15-60
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.13.13-5-pve: 4.13.13-38
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-20
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-6
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.4-pve2~bpo9
 
Last edited:
@JesusM my problem wass that when I upgraded the server, I only had in the source.list file this content:

-----------------------------------------------------
# debian updates
deb http://ftp.es.debian.org/debian stretch main contrib

# security updates
deb http://security.debian.org stretch/updates main contrib
-----------------------------------------------------

I did not remembered to review it and It was missing the following lines:

-----------------------------------------------------
# Proxmox no subscription
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription
-----------------------------------------------------

By this my server only upgraded the Linux system and did not work PROXMOX 5.1.

Later, I installed PROXMOX 5.1 with command:

apt install proxmox-ve postfix open-iscsi

After that all worked well again. The VM's and LXC CT's started without problems.

Before of upgrading It has to check the contain of source.list and must be:

-----------------------------------------------------
# debian updates
deb http://ftp.es.debian.org/debian stretch main contrib

# security updates
deb http://security.debian.org stretch/updates main contrib

# Proxmox no subscription
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription
-----------------------------------------------------


Regards,

Ramses