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...
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...
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
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.