Proxmox VE 5.1 released!
- Thread starter martin
- Start date
no - there is still no upstream fix AFAICT.. we are tracking developements though, so once one is available we will include it.
You can track it too:
Ubuntu Kernel: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519
Linux Kernel-Stable: https://www.spinics.net/lists/stable/msg201905.html
Linux Kernel-SCSI: https://www.spinics.net/lists/linux-scsi/msg115491.html
Ubuntu Kernel: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519
Linux Kernel-Stable: https://www.spinics.net/lists/stable/msg201905.html
Linux Kernel-SCSI: https://www.spinics.net/lists/linux-scsi/msg115491.html
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.
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:
pve-kernel-4.13.8-3-pve
pve-kernel-4.13.8-2-pve
pve-kernel-4.13.4-1-pve
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.
EDIT: Hmm, you know what, this could be explained by LVM2 scanning for disks during boot and getting hung up on one whose SATA controller driver was broken in the newer kernel release. I reinstalled with a ZFS root volume and removed LVM as much as possible, and now it just hangs on ZFS operations instead.
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:
pve-kernel-4.13.8-3-pve
pve-kernel-4.13.8-2-pve
pve-kernel-4.13.4-1-pve
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.
EDIT: Hmm, you know what, this could be explained by LVM2 scanning for disks during boot and getting hung up on one whose SATA controller driver was broken in the newer kernel release. I reinstalled with a ZFS root volume and removed LVM as much as possible, and now it just hangs on ZFS operations instead.
Last edited:
please test the 4.13 kernel from pvetest like I said, and not known buggy ones.
only a kernel update to disable the buggy Intel SPI flasher module which causes hardware issues on some Lenovo laptops (the iso contains its release notes btw
)
Hey @fabian The PVETest kernel booted fine. I was able to upgrade both machines to 4.13.
Thanks!
Running: Linux prxphx6 4.13.13-4-pve #1 SMP PVE 4.13.13-35 (Mon, 8 Jan 2018 10:26:58 +0100) x86_64 GNU/Linux
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.
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.
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).
Where can you download the 5.0 ISO? The only thing i see here is the 5.1, and that's the one that's not working.
