upgrade

  1. F

    4.4 > 5.2 upgrade > grub error: unknown filesystem

    I upgraded one of my 4.x Proxmox servers to 5.2 today following the directions[1] below and have grub error after rebooting. After the reboot this came up: https ://imgur.com/a/kKXlHUj and then after fsck'ing Grub is lost: https ://imgur.com/a/cmAwRNc Is this salvageable? [1]...
  2. J

    Journals missing or in the wrong place?

    Good morning all, On each of my Ceph nodes I have 2 SSD's for journals. /dev/sdj & /dev/sdk While upgrading from Hammer -> Jewel I noticed something that I think is odd, but I'm not sure. It appears that some of my OSD's either may not have journals, or the journal is not set to one of the...
  3. W

    Upgrading root disk on PVE host in a cluster?

    Hi All Homelab environment. System 1: Supermicro X10SDV, 8C/16T, 64GB. 256GB NVMe (as system and some for lvm-thin) 1TB SATA SSD (as ZFS pool, shared via NFS) 4x SATA disks as ZFS Pool shared via NFS System 2: Intel NUC, 2C/4T, 16GB 512GB SATA SSD Configured as a proxmox cluster. Bunch of...
  4. L

    [SOLVED] Web interface broke after update

    Hello, after i perfomed an 'apt upgrade' today with 116 updates that broke the webinterface. When i want to reach webinterface the site keep to be blank. Updated packages: Start-Date: 2018-05-10 19:07:20 Commandline: apt upgrade Install: libldb1:amd64 (2:1.1.27-1+b1, automatic)...
  5. S

    Upgrade from 3.4 to current version

    Hi, We have 13 hosts with proxmox 3.4 (1 cluster). We want update to current version 5. I guess that we should: 1. make install proxmox 4 and restore vm's and containers, convert containers to new format. 2. upgrade in-place to 5 - (is it safe?). What is preferred upgrade path? Maybe is...
  6. D

    [SOLVED] upgrade issues

    Setting up proxmox-ve (5.1-42) ... Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating /boot/initrd.img-4.13.16-2-pve cryptsetup: WARNING: failed to detect canonical device of /dev/sda1 cryptsetup: WARNING: could not determine root device from /etc/fstab Any idea...
  7. D

    Odd warning message when upgrading

    When running apt dist-upgrade, I sometimes get the following warning message: run-parts: executing /etc/kernel/postinst.d/dkms 4.13.16-2-pve /boot/vmlinuz-4.1 3.16-2-pve dkms: WARNING: Linux headers are missing, which may explain the above failures. please install the...
  8. I

    Upgrading Proxmox from 3.4 to 4.x

    Hi there, I am running Proxmox 3.4-16 and looking to upgrade. I am attempting to follow this guide - https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC but, at the start where I need to check network settings, I have followed the instructions for both VENET AND VETH in obtaining network...
  9. E

    Vorgehensweise: Umstellung von Wheezy Openvz auf Proxmox 5.x

    Hallo zusammen, vorhanden: Debian Wheezy Openvz Rootserver 4 VMs online direkt mit eigener IP erreichbar 1 VM über VPN und interner IP erreichbar (VMs sind schon auf Proxmox VM konvertiert (Testserver) Um ein Update des Systems auf Stretch mit Proxmox durchzuführen, fallen mir ein paar Wege...
  10. T

    Live migration to another cluster (even from 3 to 5)

    All old proxmox users know how frustrating it can be to migrate your enviroment from 3 to 4 or even to 5. Ad there is many many other reasons why you some times want migrate your vm's from cluster to another. There is dirty hack for that. - copy from your local machine authorized keys your...
  11. G

    Different upgrade state on two PVE systems?

    I have two PVE systems which are not connected, both have a valid subscription and the same apt sources settings, but I get different results on running package update while both claiming that no updates are available: proxmox-ve: 5.1-40 (running kernel: 4.13.13-4-pve) pve-manager: 5.1-46...
  12. gurubert

    Migration from PVE 3 to 5 with GFS2 on shared storage

    Hi, I need to migrate a two node cluster from PVE 3.2 to 5.1. The cluster uses a shared storage device connected via SAS to the nodes running GFS2 on top of the shared block devices. GFS2 uses lock_dlm as locking manager, managed by the cluster manager of PVE. Is it possible to install PVE 5.1...
  13. MagicFab

    Thank you! Flawless hardware upgrade in progress.

    This morning I had a scheduled PVE hardware upgrade planned. The plan was to move PVE OS disk + local data disk from an aging system (A) to a temporary system (B), in preparation for new faster disks + RAID being installed on (A). I just plugged the (A) disks in (B), booted and... it works...
  14. D

    Unable to upgrade node in cluster

    root@node02-sxb-pve01:~# apt-get update Err:1 https://packages.cisofy.com/community/lynis/deb stretch InRelease Failed to connect to packages.cisofy.com port 443: No route to host Err:2 https://enterprise.proxmox.com/debian/pve stretch InRelease Failed to connect to enterprise.proxmox.com...
  15. G

    PVE won't boot after upgrade 4.2 to 4.4

    Hi! just did a dist-upgrade to upgrade my PVE node from 4.2 to 4.4. upgrade process was good, but after the system reboot it won't start on default mode. the output of journalctl -xe is attached. I need some help to identify the error, thanks in advance.
  16. T

    Proxmox 5.1 upgrade problem - lvm-thin disappears

    When I upgraded from 4.4 to 5.1, I ran into a problem where the lvm-thin storage refused to start when the system was booting. I've forgotten the exact error code, but it was something along the lines of lvm2-activation.service error code 5. This of course caused quite a panic, even though I...
  17. B

    CEPH problem after upgrade to 5.1 / slow requests + stuck request

    Hi, I've got problem with my CEPH cluster. Cluster specification: 4x node 4x mon 4x mgr 37x osd I was starting from CEPH hammer so I followed tutorials: https://pve.proxmox.com/wiki/Ceph_Hammer_to_Jewel - without any problems https://pve.proxmox.com/wiki/Ceph_Jewel_to_Luminous - without any...
  18. C

    Upgrading to enterprise repo

    Hello, I wanted to know if we currently have the no-subscription repo and wanted to upgrade to the enterprise repo would that be possible by just changing the source list and apt-get update && apt-get dist-upgrade or we would need to reinstall since some packages are newer on the no-sub repo ...
  19. I

    monitors crash after upgrade Proxmox 4.4 to Proxmox 5.1

    Hello, After successful upgrade Proxmox 4.4 to Proxmox 5.1 we decided to go with BlueStore instead of FileStore. As soon as I deleted one FileStore OSD and created BlueStore instead, ceph became unresponsive. It appeared that 2 of 3 monitors crashed, and failed to start. Here is the snippet of...
  20. Volker Lieder

    Merge Proxmox 4.4 to 5.1

    Hi, we have a running setup with: 4 Server Debian 8.x with Proxmox 4.4, CEPH "hammer" with 30 osds Last weekend and for further growing, we installed 4 server with debian stretch and proxmox 5.1. If we login to the proxmox panel the new servers are marked as "offline". I didnt see any hints...