Rendering one of the most common server raid adapters out there unbootable (as evidenced by the wide range of very common server types already reported to have issues) is not exactly to be dismissed as "any issues on all possible hardware" so yeah, I do question how obvious the choice was to promote this one to default.... having a kernel that never shows any issues on all possible hardware is an illusion).
+1. HP BL460c gen8 + HP SA p220i.after latest upgrade to 4.15.15-1-pve kernel on server DL180 G6, with Array HP410 - server wont start.
some console messages on screenshot
We just uploaded a new 4.15 kernel (pve-kernel-4.15.17-1-pve: 4.15.17-8) to pvetest, should fix your issue.+1. HP BL460c gen8 + HP SA p220i.
Bug in kernel.
Fixed in Kernel 4.15.0-19.20.
It's currently in pvetest repo only. If you wait awhile it should be in no-subscription repo soon. Otherwise use 4.13.16-2 for now
So, not solved...Sometimes if i say "reboot" in an LXC the whole server did not response anymore. On the clusternode on all VM's, containers and storages there is an questionmark. On journallog there is nothing showy. PCT Command did nothing, only an never ending timeout. Only an reboot did help here.
May 06 01:07:37 virtu01 pct: <root@pam> end task UPID:virtu01:00000A21:025B1AEF:5AEE3938:vzstart:104:root@pam: command 'systemctl start pve-container@104' failed: exit code 1 May 06 01:07:37 virtu01 pct: command 'systemctl start pve-container@104' failed: exit code 1 May 06 01:07:37 virtu01 systemd: email@example.com: Failed with result 'exit-code'. May 06 01:07:37 virtu01 systemd: firstname.lastname@example.org: Unit entered failed state. May 06 01:07:37 virtu01 systemd: Failed to start PVE LXC Container: 104. May 06 01:07:37 virtu01 systemd: email@example.com: Killing process 2597 (lxc-start) with signal SIGKILL. May 06 01:07:37 virtu01 systemd: firstname.lastname@example.org: Control process exited, code=exited status=1 May 06 01:07:37 virtu01 lxc-start: Additional information can be obtained by setting the --logfile and --logpriority options. May 06 01:07:37 virtu01 lxc-start: To get more details, run the container in foreground mode. May 06 01:07:37 virtu01 lxc-start: The container failed to start. May 06 01:07:37 virtu01 lxc-start: lxc-start: 104: lxccontainer.c: wait_on_daemonized_start: 824 Received container state "STOPPING" instead of "RUNNING" May 06 01:07:37 virtu01 zed: eid=257 class=history_event pool_guid=0x8BF9CFD7A2BDFFE2
You can download and install it manually if you dont want to use pvetest repo otherwise::
wget http://download.proxmox.com/debian/pve/dists/stretch/pvetest/binary-amd64/pve-kernel-4.15.17-1-pve_4.15.17-8_amd64.deb dpkg -i pve-kernel-4.15.17-1-pve_4.15.17-8_amd64.deb