Search results

  1. T

    Kernel Oops with kworker getting tainted.

    Since upgrading from 6.0 to 6.1 I have had two different host machine generate the following similar error. It always had kworker as the issue PID. First system became unresponsive and unrecoverable over time. Tried to reboot the host safely but had to power reset the physical host. This one is...
  2. T

    Question on noVNC behavior

    I have a few systems that noVNC seems to behave differently between them. If I open a noVNC to a non-running VM of course I get a "Failed to connect to server" but if I use the noVNC commands from the GUI to start it, it will sit and wait for a connection and present me with the logo and...
  3. T

    Upgrade to kernel 4.15.18-12-pve goes BOOM!

    Just did an upgrade to 4.15.18-12-pve which looked like ZFS changes only and now my system boots into a read-only state just after 'cgmanager' starts and that's it. Just a '(none):~#' prompt. I am running ZFS on the server. Scientific Progress Goes Boink. -Waz

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!