Just need a nudge in the right direction as I am quite stuck at the moment. It looks like it cant mount the complete volume group and only loads root. When I login I can see the files and dir structure but nothing seems to be running.
Then some of the messages of recovering journal and caching etc. Defaulting to byte suze.įirmware Bug: the Bios has corrupted hw-PMU resources etc.
#Clover configurator boot volume full
The odd thing is that I can login to Proxmox and see that the root partition is 30Gb and not the full 120Gb I assigned, also the networking does not work. The boot takes very long and looks as if it hangs with the booting from c:\ message and a weird 6 bellow it, but if I after a while press F3 and enter a couple of times it generates an error (I had to film it as it goes by really quick) and then it boots proxmox. Installed Proxmox on a SSD in a USB 3.0 external case and prepared the SD card with the clover boot as per you instructions. So I started looking for a fix and found this. Than it suddenly I though, well offcourse, you are passing the PCIE SATA controler as a whole to the VM and the OS drive is in the ODD port which is on the same controller, that wont work.įor the rest Proxmox works fine as long as I do not pass the sata controller to the VM. NOTE: If the Timeout integer is set to 0, hold any key when powering on to invoke the bootloader GUI. Once I start the VM Proxmox hangs and I have to cold boot the server. Clover must have be able to find a default entry for it to automatically boot into an OS see DefaultVolume below. Now I want to setup my HP Microserver GEN8 (with 16Gb and a Xeon cpu) as a backup server so I can test upgrades etc.īut cant get the passthrough to work, even with the grubb fixes for IMOU and Relaxed RMRR etc. This works great, I share the storage as NFS to the host and store data and VM's etc.
#Clover configurator boot volume plus
I have a HPE Microserver GEN10 Plus running Proxmox 6.4 flawlessly from a USB ssd and with the PCI SATA controller and drives passed through to a XPENLOGY vm. After the UUID is filled in correctly, the corresponding volume will. In my search for a solution to my problem I stumbled upon this article. The disk UUID is the UUID mentioned above, and it must match the column of the path behind. Installing Clover Launch Clover Configurator, click on Mount EFI, select the drive with the EFI partition you want to mount and click Mount EFI. Look for which partition on your nvme drive is the EFI partition (you can boot into proxmox using the clover usb and pressing F3, or you can boot using the proxmox installer and choose the debug install, at the first prompt type exit, then another prompt will load with full Linux tools available.) (make sure the volume key in ist is all CAPS/Capitalized) The volume key is easy, first boot into proxmox. Load Clover's GUI and enter the Options menu (by pressing O) Browse all options and try to understand what is set and why Fix what you understand and leave the rest like it is Load the OS.