It simply took me to a screen, that said “Reboot into firmware interface”.
However, when I re-did the installation using ext4 - I was able to boot successfully
Please use the debug mode of the installer, at the second prompt check for /sys/firmware/efi directory, if it is not present or empty you are not booted in uefi mode. I'll add a line at the summary screen to show which boot mode the installer is in, it seems that it may help some people to ensure that they have correct the mode selected.Will a UEFI installation be possible in the future?
This seems rather odd (segfaults in core binaries usually makes me think about broken RAM).
Please open a separate thread, since this seems a more involved issue, and provide the following:
* the diff of the shipped udev init-script and the one you have on your system (did you modify it)?
* what is written in the systemd-override-conf for udev ('/etc/systemd/system/systemd-udevd.service.d/override.conf')?
* the output of `dmesg`
* the journal since the last boot `journalctl -b`
Please use the debug mode of the installer, at the second prompt check for /sys/firmware/efi directory, if it is not present or empty you are not booted in uefi mode. I'll add a line at the summary screen to show which boot mode the installer is in, it seems that it may help some people to ensure that they have correct the mode selected.
If you're booted into uefi mode and choose ZFS everything should be done automatically.
After DHCP it tells me that the installations is aborted and cannot continue
Awesome, super psyched to get this newer version of ZFS upgrade. But before I try on my lone single server, anyone have success upgrading a machine with ZFS on root?
As mentioned in Post #23, I successfully updated my Proxmox machine with ZFS on root.Also need to do this on 2 machines, and would prefer to read some success stories first...
I'd love to do that, but the shortcut does not work with the LARA from Hetzner. I can neither do it via my keyboard nor via the softkeyboard. Nothing happens.Strange! Could you switch over to the second tty, normally done by sending "CTRL + ALT + F2" (use F2 to switch back to the original prompt) and check if there are any errors visible about why this happens. Note that sending this combination is best done via the virtual keyboard of the remote viewer, at least if you use Linux as Desktop - as else your local Desktop will switch to TTY2, (and the xserver is normal on TTY7).
I attached the dmesg.log, but it's really hard to get that with the slowlyness and english keyboard.
Q: Can I install Proxmox VE 6.0 beta on top of Debian Buster?
A: Yes, see https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster
Q: Can I dist-upgrade Proxmox VE 5.4 to 6.0 beta with apt?
A: Please follow the upgrade instructions exactly, as there is a major version bump of corosync (2.x to 3.x)
echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
I guess you change to root via `su`? In that case this is a change in Debian Buster:is this a sign that there is something else wrong or I just need to adjust PATH, and if so, whats the proper way to update PATH?