[SOLVED] Problem when upgrading to proxmox-ve 5.0-19

[Nam Trần]

Dear gurus,

Yesterday I decided to upgrade pve to the newest version (through pve-no-subscription repository). A problem (WARNING) was popped up as described as followings:

Spoiler: upgrade

root@pve17:~# apt-get update && apt-get upgrade
Ign:1 http://debian.xtdv.net/debian stretch InRelease
Hit:2 http://debian.xtdv.net/debian stretch Release
Get:4 http://download.proxmox.com/debian/pve stretch InRelease [3,058 B]
Get:5 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 P ackages [87.1 kB]
Get:6 http://security.debian.org stretch/updates InRelease [62.9 kB]
Get:7 http://security.debian.org stretch/updates/main amd64 Packages [128 kB]
Get:8 http://security.debian.org stretch/updates/main Translation-en [52.7 kB]
Get:9 http://security.debian.org stretch/updates/contrib amd64 Packages [556 B]
Get:10 http://security.debian.org stretch/updates/contrib Translation-en [256 B]
Fetched 335 kB in 29s (11.5 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
proxmox-ve pve-qemu-kvm
The following packages will be upgraded:
libpve-access-control libpve-storage-perl linux-libc-dev lxcfs pve-manager
qemu-server
6 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 3,531 kB of archives.
After this operation, 8,192 B of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
root@pve17:~# apt-get dist-upgrade --yes
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
libsnappy1v5 pve-kernel-4.10.17-2-pve
The following packages will be upgraded:
libpve-access-control libpve-storage-perl linux-libc-dev lxcfs proxmox-ve
pve-manager pve-qemu-kvm qemu-server
8 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 57.9 MB of archives.
After this operation, 156 kB of additional disk space will be used.
Get:1 http://debian.xtdv.net/debian stretch/main amd64 libsnappy1v5 amd64 1.1.3-3 [51.0 kB]
Get:2 http://security.debian.org stretch/updates/main amd64 linux-libc-dev amd64 4.9.30-2+deb9u3 [1,252 kB]
Get:3 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 libpve-access-control amd64 5.0-6 [33.0 kB]
Get:4 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 lxcfs amd64 2.0.7-pve4 [38.9 kB]
Get:5 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 pve-kernel-4.10.17-2-pve amd64 4.10.17-19 [48.0 MB]
Get:6 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 pve-qemu-kvm amd64 2.9.0-3 [6,322 kB]
Get:7 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 libpve-storage-perl all 5.0-13 [74.7 kB]
Get:8 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 qemu-server amd64 5.0-15 [152 kB]
Get:9 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 pve-manager amd64 5.0-30 [1,981 kB]
Get:10 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 proxmox-ve all 5.0-19 [5,092 B]
Fetched 57.9 MB in 2min 9s (448 kB/s)
apt-listchanges: Reading changelogs...
Preconfiguring packages ...
(Reading database ... 93049 files and directories currently installed.)
Preparing to unpack .../0-libpve-access-control_5.0-6_amd64.deb ...
Unpacking libpve-access-control (5.0-6) over (5.0-5) ...
Preparing to unpack .../1-linux-libc-dev_4.9.30-2+deb9u3_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.9.30-2+deb9u3) over (4.9.30-2+deb9u2) ...
Preparing to unpack .../2-lxcfs_2.0.7-pve4_amd64.deb ...
Unpacking lxcfs (2.0.7-pve4) over (2.0.7-pve2) ...
Selecting previously unselected package pve-kernel-4.10.17-2-pve.
Preparing to unpack .../3-pve-kernel-4.10.17-2-pve_4.10.17-19_amd64.deb ...
Unpacking pve-kernel-4.10.17-2-pve (4.10.17-19) ...
Selecting previously unselected package libsnappy1v5:amd64.
Preparing to unpack .../4-libsnappy1v5_1.1.3-3_amd64.deb ...
Unpacking libsnappy1v5:amd64 (1.1.3-3) ...
Preparing to unpack .../5-pve-qemu-kvm_2.9.0-3_amd64.deb ...
Unpacking pve-qemu-kvm (2.9.0-3) over (2.9.0-2) ...
Preparing to unpack .../6-libpve-storage-perl_5.0-13_all.deb ...
Unpacking libpve-storage-perl (5.0-13) over (5.0-12) ...
Preparing to unpack .../7-qemu-server_5.0-15_amd64.deb ...
Unpacking qemu-server (5.0-15) over (5.0-14) ...
Preparing to unpack .../8-pve-manager_5.0-30_amd64.deb ...
Unpacking pve-manager (5.0-30) over (5.0-29) ...
Preparing to unpack .../9-proxmox-ve_5.0-19_all.deb ...
Unpacking proxmox-ve (5.0-19) over (5.0-18) ...
Setting up libpve-storage-perl (5.0-13) ...
Setting up linux-libc-dev:amd64 (4.9.30-2+deb9u3) ...
Setting up libpve-access-control (5.0-6) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Setting up libsnappy1v5:amd64 (1.1.3-3) ...
Processing triggers for systemd (232-25+deb9u1) ...
Setting up lxcfs (2.0.7-pve4) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up pve-kernel-4.10.17-2-pve (4.10.17-19) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.17-2-pve /boot/vmlinuz-4.10.17-2-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.10.17-2-pve /boot/vmlinuz-4.10.17-2-pve
update-initramfs: Generating /boot/initrd.img-4.10.17-2-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.10.17-2-pve /boot/vmlinuz-4.10.17-2-pve
Generating grub configuration file ...
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
Found linux image: /boot/vmlinuz-4.10.17-2-pve
Found initrd image: /boot/initrd.img-4.10.17-2-pve
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
Found linux image: /boot/vmlinuz-4.10.17-1-pve
Found initrd image: /boot/initrd.img-4.10.17-1-pve
Found linux image: /boot/vmlinuz-4.10.15-1-pve
Found initrd image: /boot/initrd.img-4.10.15-1-pve
Found linux image: /boot/vmlinuz-4.4.67-1-pve
Found initrd image: /boot/initrd.img-4.4.67-1-pve
Found linux image: /boot/vmlinuz-4.4.62-1-pve
Found initrd image: /boot/initrd.img-4.4.62-1-pve
Found linux image: /boot/vmlinuz-4.4.59-1-pve
Found initrd image: /boot/initrd.img-4.4.59-1-pve
Found linux image: /boot/vmlinuz-4.4.49-1-pve
Found initrd image: /boot/initrd.img-4.4.49-1-pve
Found linux image: /boot/vmlinuz-4.4.44-1-pve
Found initrd image: /boot/initrd.img-4.4.44-1-pve
Found linux image: /boot/vmlinuz-4.4.35-1-pve
Found initrd image: /boot/initrd.img-4.4.35-1-pve
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Adding boot menu entry for EFI firmware configuration
done
Setting up pve-qemu-kvm (2.9.0-3) ...
Setting up qemu-server (5.0-15) ...
Setting up pve-manager (5.0-30) ...
Setting up proxmox-ve (5.0-19) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
root@pve17:~# man pvscan
root@pve17:~# pvscan --cache
WARNING: Not using lvmetad because config setting use_lvmetad=0.
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).

Here are the results of pveversion -v:

proxmox-ve: 5.0-19 (running kernel: 4.10.15-1-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.4.62-1-pve: 4.4.62-88
pve-kernel-4.10.17-2-pve: 4.10.17-19
pve-kernel-4.4.49-1-pve: 4.4.49-86
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.44-1-pve: 4.4.44-84
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.59-1-pve: 4.4.59-87
pve-kernel-4.10.17-1-pve: 4.10.17-18
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-13
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-3
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

systemctl status:

Spoiler: systemctl status

● pve17
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Wed 2017-07-12 11:47:03 +07; 4 weeks 0 days ago
CGroup: /
├─user.slice
│ └─user-0.slice
│ ├─session-750.scope
│ │ ├─22061 sshd: root@pts/0
│ │ ├─22075 -bash
│ │ ├─31358 systemctl status
│ │ └─31359 pager
│ └─user@0.service
│ └─init.scope
│ ├─22063 /lib/systemd/systemd --user
│ └─22064 (sd-pam)
├─init.scope
│ └─1 /lib/systemd/systemd --system --deserialize 19
├─qemu.slice
│ ├─701.scope
│ │ └─1323 /usr/bin/kvm -id 701 -chardev socket,id=qmp,path=/var/run/qemu-server/701.qmp,server,nowait -mo
│ ├─704.scope
│ │ └─1482 /usr/bin/kvm -id 704 -chardev socket,id=qmp,path=/var/run/qemu-server/704.qmp,server,nowait -mo
│ ├─702.scope
│ │ └─1371 /usr/bin/kvm -id 702 -chardev socket,id=qmp,path=/var/run/qemu-server/702.qmp,server,nowait -mo
│ └─703.scope
│ └─1434 /usr/bin/kvm -id 703 -chardev socket,id=qmp,path=/var/run/qemu-server/703.qmp,server,nowait -mo
└─system.slice
├─lvm2-lvmetad.service
│ └─2642 /sbin/lvmetad -f
├─spiceproxy.service
│ ├─ 3233 spiceproxy
│ └─30499 spiceproxy worker
├─systemd-timesyncd.service
│ └─18592 /lib/systemd/systemd-timesyncd
├─ksmtuned.service
│ ├─ 933 /bin/bash /usr/sbin/ksmtuned
│ └─31301 sleep 60
├─lxcfs.service
│ └─905 /usr/bin/lxcfs /var/lib/lxcfs/
├─iscsid.service
│ ├─21355 /sbin/iscsid
│ └─21356 /sbin/iscsid
├─pvefw-logger.service
│ └─9961 /usr/sbin/pvefw-logger
├─corosync.service
│ └─1218 /usr/sbin/corosync -f
├─dbus.service
│ └─902 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
├─pve-firewall.service
│ └─1219 pve-firewall
├─pve-ha-lrm.service
│ └─1306 pve-ha-lrm
├─ssh.service
│ └─21541 /usr/sbin/sshd -D
├─watchdog-mux.service
│ └─911 /usr/sbin/watchdog-mux
├─system-getty.slice
│ └─getty@tty1.service
│ └─1045 /sbin/agetty --noclear tty1 linux
root@pve17:~# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● console-setup.service loaded failed failed Set console font and keymap

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@pve17:~# journalctl -xn
-- Logs begin at Wed 2017-07-12 11:47:03 +07, end at Wed 2017-08-09 16:01:00 +07. --
Aug 09 15:57:00 pve17 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has begun starting up.
Aug 09 15:57:00 pve17 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Aug 09 15:58:00 pve17 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has begun starting up.
Aug 09 15:58:00 pve17 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Aug 09 15:59:00 pve17 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has begun starting up.
Aug 09 15:59:00 pve17 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Aug 09 16:00:00 pve17 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has begun starting up.
Aug 09 16:00:00 pve17 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
Aug 09 16:01:00 pve17 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
lines 1-61

Spoiler: console-setup.service

root@pve17:~# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● console-setup.service loaded failed failed Set console font and keymap

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
root@pve17:~# systemctl status console-setup.service
● console-setup.service - Set console font and keymap
Loaded: loaded (/lib/systemd/system/console-setup.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-08-10 15:02:36 +07; 16min ago
Process: 13091 ExecStart=/lib/console-setup/console-setup.sh (code=exited, status=1/FAILURE)
Main PID: 13091 (code=exited, status=1/FAILURE)

Aug 10 15:02:36 pve17 systemd[1]: Starting Set console font and keymap...
Aug 10 15:02:36 pve17 console-setup.sh[13091]: /usr/bin/ckbcomp: Can not find file "symbols/en-us" in any known directory
Aug 10 15:02:36 pve17 systemd[1]: console-setup.service: Main process exited, code=exited, status=1/FAILURE
Aug 10 15:02:36 pve17 systemd[1]: Failed to start Set console font and keymap.
Aug 10 15:02:36 pve17 systemd[1]: console-setup.service: Unit entered failed state.
Aug 10 15:02:36 pve17 systemd[1]: console-setup.service: Failed with result 'exit-code'.
root@pve17:~# journalctl -xe
--
-- The start-up result is done.
Aug 10 15:18:15 pve17 systemd[14625]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 10 15:18:15 pve17 systemd[14625]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 10 15:18:15 pve17 systemd[14625]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Aug 10 15:18:15 pve17 systemd[14625]: Startup finished in 11ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 11388 microseconds.
Aug 10 15:18:15 pve17 systemd[1]: Started User Manager for UID 0.
-- Subject: Unit user@0.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit user@0.service has finished starting up.
--
-- The start-up result is done.
Aug 10 15:19:00 pve17 systemd[1]: Starting Proxmox VE replication runner...
-- Subject: Unit pvesr.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has begun starting up.
Aug 10 15:19:00 pve17 systemd[1]: Started Proxmox VE replication runner.
-- Subject: Unit pvesr.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pvesr.service has finished starting up.
--
-- The start-up result is done.
lines 5757-5818/5818 (END)

I have not reboot the system as it is running normally. Is there any problem after a reboot? How could I fix this error?

Thank you.

 

[Alwin]

First thing, please use apt-get dist-upgrade and NOT upgrade, as this will lead often to problems. The warning can be ignored, as we don't use the lvmetad daemon, it is disabled in the config. After the dist-upgrade you will reboot your system to activate the new kernel and then the physical volumes are scanned anyway.

 

[Rhinox]

First thing, please use apt-get dist-upgrade and NOT upgrade, as this will lead often to problems

Could you please explain this? On Debian I always do "upgrade" first, and then "dist-upgrade". Never had any problem with it...

 

[SPGC]

I still do not understand

 

[dcsapak]

Could you please explain this? On Debian I always do "upgrade" first, and then "dist-upgrade". Never had any problem with it...

unlike debian, we sometimes introduce new dependencies for packages, which an 'apt-get upgrade' does not install
but an 'apt-get dist-upgrade' does that

 

[Nam Trần]

First thing, please use apt-get dist-upgrade and NOT upgrade, as this will lead often to problems. The warning can be ignored, as we don't use the lvmetad daemon, it is disabled in the config. After the dist-upgrade you will reboot your system to activate the new kernel and then the physical volumes are scanned anyway.

I have noticed that:

1. Debian-based packages: apt-get upgrade
2. PVE-based packages: apt-get dist-upgrade

Then I decided to cancel apt-get upgrade and replace it by apt-get dist-upgrade. Everything is fine except the WARNINGs. I've found out that console-setup.serivce has failed. Is it an important service? Will it be fine after a reboot?

Do you mean that I should always use apt-get dist-upgrade? Thank you very much!

 

[Alwin]

For Proxmox server you should always use apt-get dist-upgrade or the apt full-upgrade. It is no problem that the service is not working. There is a new package on the way.

 

[fabian]

the console-setup.service will not be automatically fixed on upgrades (but the new iso coming soon has the fix). if you want to fix it, you can run "dpkg-reconfigure keyboard-configuration", and re-configure the keyboard layout.

the root cause is having 'en-us' instead of 'us' in /etc/default/keyboard , so you can also manually fix it in there

 

[Nam Trần]

the console-setup.service will not be automatically fixed on upgrades (but the new iso coming soon has the fix). if you want to fix it, you can run "dpkg-reconfigure keyboard-configuration", and re-configure the keyboard layout.

the root cause is having 'en-us' instead of 'us' in /etc/default/keyboard , so you can also manually fix it in there

I have modified the /etc/default/keyboard by replacing the "en-us" with "us" and restart the console-setup.service. It works. Thank you very much. You are so genius!