Search results

Not possible to switch to legacy. CSM is greyed out, hetzner support team told me it's probably not possible.

thnaks, will try that right away

That's where I get a bit confused... I have a 512mb vfat partition, proxmox-boot-tool refresh generates all the config. When I mount the partition everything seems in place but I can't find where is the entry that tell the system to boot from systemd Then I don't know wherelse to look.

Thanks for replying. story is: - dedicated server at hetzner UEFI only - csm activation in bios greyed out - installation for proxmox zfs has to be in rescue mode from VNC console, so proxmox installer doesn't detect legacy/uefi and set legacy by default. now we can't boot using systemd boot...

Hi there, Anyone knows where to change the config file to tell proxmox to boot from systemd insead of grub ?

I have identified the issue with ZFS but couldn't manage to fix it yet. My server is UEFI only (enabling CSM is greyed out in bios) and the server tries to boot from legacy. I am trying to find a way to rewrite boot sector to swap to systemd bootloader. I read several tuto but didn't find...

Yeah, for me no choice, cant enable CSM so proxmox installed with grub. I can see there is a way to switch to systemd bootloader but it's confusing me right now

I was looking at that on the wiki. not completely sure how to achieve that. any chances to choose that option at installation ? could you elaborate a bit on what should be the setup ?

Aouch ! option is greyed out in bios...

Ok, I will try that then. Anything I should do from this proxmox wiki: Setting up a new partition for use as synced ESP To format and initialize a partition as synced ESP, e.g., after replacing a failed vdev in an rpool, or when converting an existing system that pre-dates the sync mechanism...

It uses UEFI is that my probem ? system currently booted with legacy bios

Hi everyone, I installed proxmox on zfs on a dedicated server at hetzner, but I cannot manage to boot. I can start it using rescue mode and loading it from vnc, but if I try to boot in normal mode the server get stuck on bios menu. This happens only on zfs system. Anyone has an idea ?

Ok, so the problems seems not related to networking. The server won't boot after intall as it doesn't detect the disks once in zfs. I will open a new thread for that. Thanks

Hi, Thanks for replying. I am trying to install PVE-7.4. Hetzner doesn't hvae proxmox ZFS image so you c'an't install proxmox on a ZFS pool. I installed it from rescue mode with VNC so I get the GUI and can install from that but the installer pick the wrong interface, it sould be something like...

Hi everyone, did someone managed recently to install proxmox on zfs on a hetzner server ? I used to do it several times in the past but could not manage to do it anymore. Tried with a bootable iso installed by hetzner's tech but it brakes the network and I loose connectivity. Tried from vnc in...

well, it seems that migration failed to transfer config file and everything got stuck. ct storages have been migrated but only one out of two has been deleted from source. I renamed files.conf to files.conf.bkp, rebooted both PVE, manually moved config files to PVE destination and deleted...

Ok, so I aborted migration from GUI. CT 100 storage still appears in PVE1 and in PVE2 (missing 1Gb on PVE2) CT 171 storage is gone from PVE1 and visible in PVE2 (missing 1Gb onPVE2) Now on PVE2, I get that: It looks like config hasn't been migrated. to PVE2. But everytime I go to folder...

Hi everyone, I migrated all my CT/container with bulk migration from PVE1 to PVE2. It's been running for 8 hours, and it keeps running but the log is saying that storage has been imported successfuly and I can see my vm/CT storage in both PVE. Container's storages on PVE 2 are not fully...

Thanks for the answer. problem is: I have not enough space on the server itself to make a backup of the whole container. backup and restore to/from a remote server would cost to much downtime. I am running out of space on the server. I need to shrink overprovisioned containers, migrate them to...

ok, got my answer. I was confusing between snapshots types: vzdump & pct snapshot vzdump is snapshot of the whole container so I can delete the container once backup is done