Upgrade from version 7.4-3 to 8.2-4 issues.

davidoeol0

New Member
Nov 27, 2023
4
0
1
Hello everyone,

During the migration of one of my Proxmox nodes from version 7.4-3 to version 8.2-4, when booting with the kernel 6.8.12-1 that comes with this latest version, the following error appears:

libceph: mon1 (1) 192.168.169.20:6789 socket closed ((con state V1_BANNER))
libceph: mon5 (1) 192.168.169.10:6789 socket closed ((con state V1_BANNER))
libceph: mon6 (1) 192.168.169.15:6789 socket closed ((con state V1_BANNER))[/CODE]
ceph: No mds server is up or the cluster is laggy
[FAILED] Failed to mount mnt-pve-cephfs.mount - /mnt/pve/cephfs[/CODE]
[FAILED] Failed to mount mnt-pve-cephfs.mount - /mnt/pve/cephfs.See 'systemctl status mnt-pve-cephfs.mount' for details.
Mounting mnt-pve-cephfs.mount - /mnt/pve/cephfs...


I have already tried several solutions found in other Proxmox forums, such as adding:

[mon]
mon_mds_skip_sanity = true

to the /etc/pve/ceph.conf file, or checking if all the Ceph packages are installed.

I'm including the output of the pveversion -v command from one of the nodes running version 8.2-4 and kernel 6.8.12-1.

root@proxmox01:~# pveversion
pve-manager/8.2.4/faa83925c9641325 (running kernel: 6.8.12-1-pve)
root@gmvprox01:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-15
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph: 17.2.7-pve3
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

Thank you very much in advance for your help :)
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!