Phison E12 NVMe missing in 5.4.34-1-pve

[hk@]

the fun thing here is: the webGUI reports the start "ok", yet in syslog we get something like this:
pvestatd[1924]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5

proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.34-1-pve: 5.4.34-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve8
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

the testsystem worked fine, but this one is now a bit strange...

 

[hk@]

well, just realised the NVMe storage associated with these VEs is gone in this box after the update...
now this is really unexpected.

 

[hk@]

well, after going back to the 5.3.18-3-pve we got our nvme back and lspci shows it again:
Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01)

while on another box running 5.4.34-1-pve we got the samsung NVMe without problems:
Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)

 

[Stoiko Ivanov]

please check the journal when booting with 5.4.34-1-pve - (`journalctl -b -1 ` should give you the journal for the boot before the current one) - maybe this gives a hint.

additionally you could try booting one of the other 5.4 kernels - that could help in narrowing down when the issue was introduced.

I hope this helps!

 

[hk@]

sorry, but: journalctl -b -1
reports: Specifying boot ID or boot offset has no effect, no persistent journal was found.

 

[Stoiko Ivanov]

reports: Specifying boot ID or boot offset has no effect, no persistent journal was found.

I would suggest to enable persistent journalling for the future - see https://www.freedesktop.org/software/systemd/man/journald.conf.html (in short: `mkdir /var/log/journal; systemctl restart systemd-journald`)

maybe the syslog (files matching /var/log/syslog*) contain some information (they should contain the same as the journal )

 

[hk@]

well after updating today - tried this again.
although the "pveversion -v" shows no difference to the releases above.

now we get the controller loaded...

currently not exactly trusting this.