Recent content by Breymja
-
B
Blank page after updating today
Well, haven't had any success in finding out the cause of this issue. I wonder if i can somehow downgrade to whatever the prior working version was?- Breymja
- Post #8
- Forum: Proxmox VE: Installation and configuration
-
B
Blank page after updating today
Well, an update never broke the UI before, no matter if i restarted to get the new kernel or not. I did restart, new kernel is active and the issue was persisting. So i executed the reinstall commands mentioned above and restarted pveproxy, but the issue is still persisting. Anything else i...- Breymja
- Post #7
- Forum: Proxmox VE: Installation and configuration
-
B
Blank page after updating today
No, a reboot wasn't required for updates until now. I fear it might cause the VMs to break if something is wrong there. Shall i really reboot?- Breymja
- Post #5
- Forum: Proxmox VE: Installation and configuration
-
B
Blank page after updating today
Windows 10, 2004 Chrome, Latest Firefox, Latest Edge, Latest- Breymja
- Post #3
- Forum: Proxmox VE: Installation and configuration
-
B
Blank page after updating today
I did update the system today and since only get a blank page with the following content when trying to access the Web UI: <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge">...- Breymja
- Thread
- Replies: 9
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
That fixed the Kernel. And the Kernel fixed the Windows OS Type. Thank you very much! :) No idea how that file could have gone missing, though.- Breymja
- Post #22
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
That file doesn't exist. It's simply not there. I haven't touched that file. Will try your suggestion now.- Breymja
- Post #21
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
zd0 should be the Windows VM with its partitions, zd32 should be the Linux VM. zd16 and 48 probably are the windows VMs two snapshots. zd64 and 80 are the efi-disk for both vms. p1 should be efi, p2 should be boot and p3 should be /. (Not totally sure, mobile atm)- Breymja
- Post #19
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
Nope, doesn't work: //EDIT: Just to be clear - this is a default installation via the ISO with zero manual changes.- Breymja
- Post #17
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
Yes, i'm sure - i have ordered a Remote Console (LARA) to watch it. Okay, then i'm going to remove the Kernel again, then do pve-efiboot-tool refresh, let's see what happens. (Yes, UEFI with ZFS-RAID1 on NVME) //EDIT:- Breymja
- Post #16
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
Oh, btw, since i removed this Kernel and rebooted my VMs do no longer start: //EDIT Reinstalling the Kernel, then rebooting, fixed that issue. I need my VMs to be online, so i had to reinstall it.- Breymja
- Post #14
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
Hello @Stefan_R, of course, no Kernel there, though:- Breymja
- Post #13
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
Hello @Stefan_R Well, it's been a few years, but i've been teached removing a running Kernel is something you never do under no circumstances. I've did that and rebooted - it still booted into 5.0.15-1. This does not look healthy. No matter the weirdness of it booting an inexisting Kernel -...- Breymja
- Post #11
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
Hello @Stefan_R, that does not remove the Kernel currently running, hence on reboot it does again reboot to 5.0.15-1, any other ideas? Now the only Kernels left are 5.0.15, 5.4.41 and 5.4.44- Breymja
- Post #9
- Forum: Proxmox VE: Installation and configuration
-
B
[SOLVED] VM doesn't boot when "Windows" is selected for OS type
I've googled a lot, but couldnt find out how to change the Kernel. The solution that got to it most was "simply delete the unwanted Kernel", but that was for when someone didnt want to use the most recent kernel. My ProxMox is not using the most recent for some reason. I'm also not really...- Breymja
- Post #7
- Forum: Proxmox VE: Installation and configuration