- Oct 17, 2017
Does the latest pve-test kernel fix this issue?
no further development, but the latest 4.13 kernel (currently in pvetest) reverts the buggy commit in question. please provide feedback whether this allows upgrading to 4.13 on systems which previously failed booting because of the scsi kernel oops.no - there is still no upstream fix AFAICT.. we are tracking developements though, so once one is available we will include it.
please test the 4.13 kernel from pvetest like I said, and not known buggy ones.Damn, this affects me too. I upgraded from 5.0 to 5.1 with apt-get dist-upgrade, and afterwards it times out on boot waiting for "dev-pve-swap.device" to become ready, then hangs forever waiting for LVM2 activation ("A start job is running for Activation of LVM2 logical volumes").
I erased my Proxmox SSD, disconnected all my ZFS hard disks and did a clean install of 5.1 from the 3rd ISO. This booted fine. However, when I connect my ZFS disks back up, it starts hanging on boot again waiting for dev-pve-swap (disconnecting them allows it to keep working). Booting in single-user mode with init=/bin/bash works fine, and I can import the zpool from the disks without any errors. These tested kernels triggered the issue:
4.10.17-5-pve works perfectly.
I'm booting UEFI and my root disk is formatted with LVM using the default options in the installer.
Hey @fabian The PVETest kernel booted fine. I was able to upgrade both machines to 4.13.
please install using the 5.0 iso and then upgrade to the latest 4.13 kernel (available up to pve-no-subscription at the moment).I'm having sort of the same issue. I've reinstalled almost 20 times now. Re downloaded the ISO, changed out SSDs I'm installing to. Totally stumped on this one.