Search results

Hi there. I tried everything and am still struggling with this same issue. I have managed to set up two servers from PVE 7.4 live USB stick as a workaround and then on a running system upgrade to PVE 8.1. But one server won't even work with PVE 7.4 installer, installing fine until the end, but...

Thanks. That sure was the first thing I tried but struggled with exactly the same issues, screen going black right after having selected "Install Proxmox VE (Terminal UI)". And as I have reported above, I could get past the whole install process (by modifying...

again, very good to know! I thought the same, as it didn't happen on any of my 4 affected servers running on PVE 8.1 The only reason I need to set them up from scratch is for re-partitioning (see https://forum.proxmox.com/threads/help-grub-rescue-proxmox-8-1.137120/#post-611680), and PVE 7.4...

Great, @Apollon77 thanks a lot for your feedback. Guess I will then need to go this path as well. Good to know I am not the only one affected on this specific hardware. Still hoping for an official "fix" in PVE 8.x. Merry Christmas!

Hi all. Thanks to this thread, I have managed to get past the black screen on PVE 8.1 installer, using lspci to lookup the VGA controller BusID and then configuring it in /usr/share/X11/xorg.conf.d/10-quirks.conf. Thanks @logics for your great advice! But... I never got further. Managed to...

I am still struggling with this. When booting into the freshly set up PVE 8.1, Grub boot works fine but soon after it gets stuck in black screen. From there, I don't find a way to apply any tunings, as no terminal shows up and I cannot switch to any terminal with Ctrl-Alt-F1 (F2, F3,...). Also...

Hey @fabian Thanks for the hint. I also wanted to warn future readers that your workaround ("fix it up by adding another drive") might be the better option, as re-installing PVE from scratch on such a legacy server could fail completely due to such issues...

OK, this was already discussed/resolved here: https://forum.proxmox.com/threads/generic-solution-when-install-gets-framebuffer-mode-fails.111577/ https://dev-pages.info/troubleshooting-proxmox-installation-issues-fixing-black-screen-problem/ So my solution was (no editing of grub boot params...

Thanks a lot @fabian for your hint! That was exactly it. I remember trying to solve this a while ago, when I wanted to switch from grub to UEFI boot, but failed because of legacy partitioning: $ proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace...

I am trying to set up Proxmox VE 8.1 from scratch on a legacy system (Supermicro X9DRW-3LN4F+ board). In the past, PVE 6/7 installer worked fine on that server, but with 8.1-1 ISO (also tried with 8.0-2), the screen blacks out right after boot. Same problem with Graphical or Terminal UI...

same here, like @keropiko described. After upgrading PVE 8.1 from 6.5.11-5-pve (reboot yesterday worked fine after 6.5.11-4-pve to 6.5.11-5-pve upgrade) to 6.5.11-6-pve, Grub reported: error: no such device: 0dXXXXXXXXX. error: unknown filesystem. grub rescue> In the past, I was always able to...

The changed values should be immediately visible in the container. But you're right, nowadays it does not anymore. Remember, my post dates back to Oct 2022 and I can't tell what has changed since then. Maybe it was also changed in previous LXC or kernel versions. You are probably just fine with...

Yes, it affects ALL containers running on that same Proxmox host! I also have this running in production on hosts with 5-10 other LXC containers, for over 7 yrs and never, and have never experienced any negative side effects.

Looks like this is a duplicate of https://forum.proxmox.com/threads/proxmox-on-arm64.69080/ Please close this thread and continue the discussion there.

I have just found a distributor in Germany that could ship the HPE ProLiant RL300 Gen11 – with a beefy Ampere M128-30 that would be the dream machine! I just hope Proxmox VE will be soon ready for arm64 and officially support it. Until then, I am going to hold back any server upgrades in my...

ok, the kernel documentation https://www.kernel.org/doc/Documentation/networking/bonding.txt says: min_links Specifies the minimum number of links that must be active before asserting carrier. It is similar to the Cisco EtherChannel min-links feature. This allows setting the...

Hi there. I have my Proxmox VE (latest 7.3) pre-configured for LAGGs with LACP, currently only with a single interface assigned to bond0 slaves, so I can go live by adding the second interface once I (physically) migrate to new switches (Aruba 6300 Series). All works fine so far and «Apply...

Yes, I did so. But this ended up being rather a remote management issue, as it got really hard to further debug this. Video of my remote management solution (Raritan DKX4-101 connected to an Aten KVM switch) dropped out completely, so I was never able to see that black screen and could only type...

thanks, that worked as well. But unluckily, it seems impossible to rescue that server from remote, as it gets stuck on that prompt: Cannot import 'rpool': pool was previously in use from another system. The pool can be imported, use 'zpool import -f' to import the pool. I can only hardly...

Thanks, that worked. I was just rbindmounting /run directly: $ zpool import -f rpool $ zfs set mountpoint=/mnt rpool/ROOT/pve-1 $ mount -t proc /proc /mnt/proc $ mount --rbind /dev /mnt/dev $ mount --rbind /sys /mnt/sys $ mount --rbind /run /mnt/run $ chroot /mnt /bin/bash init then worked...