Is that possible to install Proxmox VE on my Librem Mini V2 and use it as a normal Proxmox server?
I boot from the USB device. Until then everything is fine.
But then I get a mistake that he could not load the installation script.
Is there a solution for this?
Greetings
I have no idea but what, if anything, is currently installed on the Mini? And, if there is nothing important on there, can you install Debian? and then install Proxmox VE on top of Debian?
If you want to make progress with the original issue, you may have to capture a photo of the screen i.e. in order to exhibit the error message.
I would probably be checking with Proxmox what their expectations are around BIOS / UEFI and, conversely, which firmware you are running on your Mini (Coreboot BIOS v. Pureboot).
Thanks for the reply.
I tried several USB sticks and operating systems, including with and without Ventoy. And also with a Debian. But no ISO worked. Then there is a warning.
Unfortunately I don’t know my way around well.
I have a Librem Mini V2 with Pureboot Bundel with a Libremkey + Vault.
QubesOS is preinstalled on the pre -constructed NVME.
I deliver a screenshot, during the day.
Is it definitely due to the encryption with the libremkey?
On the other hand, if I put the libremkey in, should he actually give the OK to install a new fresification system?
I haven’t reset anything yet and didn’t put anything back on factory settings.
The device has been switched on for the first time and I once and once I let myself be guided on QuesOS with the key. Then I tried to install another OS.
I hope the photos are available long enough at this provider.
He says he would start any kernel, but even after hours he doesn’t start anything.
(I fixed the photos for you.)
OK, so there isn’t really much of an error message. It just hangs and never boots the proxmox installer. Is that correct?
Maybe @jonathon.hall can suggest some troubleshooting?
Yes that is correct.
PureBoot is unable to apply the firmware blob jail, although I am uncertain as to whether or not that is affecting Proxmox initialization.
So, I did a few more tests. With another USB stick. After reading here I read a few similar problems that were about USB3.0. So I took a USB3 stick. This time he showed me a different message. See screenshot.
Unfortunately I don’t know slowly. There are no more similar cases where there were solutions.
I very much hope that someone else who knows himself better.
What would also be interested in is what the 3 Admin and 3 users have used at the top? What does that refer to? Since I have not set up users or admins.
Is the USB flash drive formatted with an exfat file system??
For smaller capacity flash drives, they tend to come pre-formatted as FAT. For larger capacity flash drives, where FAT may not be a great option, they tend to come pre-formatted as exFAT. Linux support for exFAT may not be as mature. FAT or exFAT may be entirely unexpected.
So the capacity of the flash drive could make a difference, and the file system choice could make a difference.
Can you mount and browse this flash drive when just booted normally?
I had a quick look at the Proxmox VE install instructions and they do not spell out (that I could see) how you are supposed to copy the .iso to the USB flash drive in order to create a bootable USB. (Downloading the .iso is the easy part.)
What did you do in order to create the bootable USB from the .iso file?
I did it as in the instructions of Proxmox.
with: dd bs=1M conv=fdatasync if=./proxmox-ve_*.iso of=/dev/XYZ
Of course with the latest ISO. And that also works wonderfully. Have already tried it with Etcher, works too. The stick boots easily on other devices.
I have it with ntfs and with ext4. I also tried it with a dos and a gpt partition table.
edit: Is it perhaps because of the high security of Pureboot that he prohibits the pre -installed NVME overwritten by the boot? Do I have to verify the ISO first?
I’m still very new with Pureboot.
What was the value of XYZ?
Of course my USB stick /dev/sdb1.
Is it expecting /dev/sdb instead?
I can try again with sdb. sdb1 is the partition that I created beforehand when I overwritten the USB stick. Do you think it changes what if he can overwrite the stick himself?
Can you link to the actual instructions on the Proxmox VE web site that you are following?
The instructions are ambiguous.
I assume that there is nothing of value on the flash drive - so that it can be overwritten in its entirety.
I would guess that they want you to use sdb rather than sdb1. (Hence there is no need to partition or format the flash drive before use. It will just get completely overwritten.)
Now just tried it with sdb. It is interesting that he shows me more options in the boot menu with Etcher. With Etcher I still have Memory_test and other boot options. If I do it as in the instructions, he only shows me a PVE entry. But booting doesn’t work with both.
edit:
Maybe the problem is that I would like to use the pre -installed encrypted NVME on which Purism QubesOS was pre -installed? But I want to use this hard drive and not a new one. But I will also have to try that too.
edit2:
A small note on the edge. I have not yet connected the device to the Internet. And I use a safe offline laptop to spread the USB stick.
I suspect that in order to have a chance that this works you will want to change boot firmware from Pureboot to Coreboot/BIOS. But that procedure should only be undertaken with care!
