We use Univention Corporate Servers for AD compatible services and can confirm this tutorial is effective for binding the servers and for user/group auth.
Thanks for your post!
Confirmed modifying GRUB
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"
on the Dell T310 corrected the failure to boot with the MPTSAS card.
I would think disabling virtualization support would be a temporary solution to boot into the OS but not a viable work-a-round presuming Proxmox is being used to host VMs. It was faster to select the prior kernel in the grub load screen and pin it. Perhaps that was the intent of the post.
Encountered this issue today on upgrading a stand-alone install. This is on a Dell T310 with an MPTSAS card with 2 SSDs attached.
I've pinned the 5.13.19-6-pve kernel using the proxmox-boot-tool in the meantime. Interested to know if anyone else has had this issue or if there's a way to correct...
A rather old thread, however, still relevant for disaster preparations if running single node installations of Proxmox.
I found this nice writeup on generating a ZFS enabled liveCD (it might be the new CDs already have ZFS built-in - I haven't checked yet) but in case someone finds this post...
I would't qualify my experience as 'horrendous' just 'unpleasant'. Yes, same issue for the network interfaces failing to start with the new package (among other things.)
Completed the upgrade from 5.4 to 6.2. After rebooting, attempted to add a new VM. The raw disk image is created successfully, however, the link fails to create:
The contents for the zvol.rules is as follows:
# Persistent links for zvol
# persistent disk links: /dev/zvol/dataset_name
# also...
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.