We are also experiencing this issue now from months, since we upgraded to Proxmox 7. Unfortunately, many users are reporting this exact same bug (curiously, most of them had the CPU locked exactly for 22 or 23 seconds), but for now there is no clear solution nor workaround...
Can anyone at Proxmox's support staff confirm whether there are any major issues in running Proxmox V6.1 on kernel 4.15.18, while I wait for WD to port their driver to version 5.x of the kernel? For now everything seems to work smoothly but before upgrading a whole cluster I'd like to be...
Thanks but unfortunately while I was successfully able to compile the 5.1.28 branch of snuf's iomemory-vsl fork, it wont' recognize my SX350-3200 ioDrive2, I think that version of the driver is for ioDrive gen. 1 only. Right now I've reverted back to kernel 4.15.18-24-pve where I can get the...
Hi @Vladimir Bulgaru I'm also desperately looking for a backport of the ioDrive2 drivers to Proxmox 6.1. Since I don't use LVM on them would you mind to let me test your solution? Thanks and Merry Christmas!! :)
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.