please check the linked thread with a patched test kernel
It works, thanks!
please check the linked thread with a patched test kernel
to help trouble shoot upgrading issues, we built a 4.10-based kernel including ZFS 0.7.3, available on pvetest. you need to manually download and install it, as no meta-package pulls it in automatically:
http://download.proxmox.com/debian/...pve-kernel-4.10.17-5-pve_4.10.17-25_amd64.deb
Thanks Fabian,
The 4.10/0.7.3 kernel works perfectly on my two misbehaving servers. It seems 4.13 added a regression for the Supermicro SCU on at least the X9SRW-F motherboard (C602 chipset). Attached are two snapshots of 4.13 (not) booting - the first shows the kernel panic (isci_task_abort_task), the second where starting udev just fails.
View attachment 6191 View attachment 6192
thanks for the feedback. seems like that particular 4.13 issue (on a Lenovo system) is already being bisected by the ubuntu kernel team. once a potential fix is available, we will provide a test kernel.
No. The only way to get security update is to update to PVE 5.1Is it possible to stay a little bit longer on 5.0 and still receive security updates and bugfixes?
I for some reason can't upgrade to version 5.1. I don't have the subscription. I am going from version 5.0. When I read the directions I see my source.list points to the right place. If I do an apt update that seems to work fine other then the 401 error for enterprise which I would expect since I don't have the subscription. But when I do apt dist-upgrade it literally shows that nothing needs to be done. Any help would be appreciated.
Please ignore. I did solve this.I for some reason can't upgrade to version 5.1. I don't have the subscription. I am going from version 5.0. When I read the directions I see my source.list points to the right place. If I do an apt update that seems to work fine other then the 401 error for enterprise which I would expect since I don't have the subscription. But when I do apt dist-upgrade it literally shows that nothing needs to be done. Any help would be appreciated.
How did you solve it? I am having that exact same issue on 2 hosts.Please ignore. I did solve this.
That was it. I upgraded all of my whitebox hosts to Proxmox VE 5.1 with zero issues. Thanks.You should buy a subscription or use a no-subscription repository.
https://pve.proxmox.com/wiki/Package_Repositories#_proxmox_ve_no_subscription_repository
Are we gonna get to try kernel 4.14 in place of 4.13 to see if the bsod bugs are fixed there?
this is a bug, and i sent a fix for this already to the list. thanks for catching thisAm I doing something wrong?