Recent content by Obi_Yoann

  1. O

    [SoYouStart] rEFInd/Grub Boot Error (Upgrading Proxmox 6 to 7)

    I would also say that they NEED to document the specifics of their installation templates, the fact they use two (or more) EFI partitions is not documented anywhere i believe. Yes they should provide newer templates, it would be much better! But here an update to grub would be halfway done is...
  2. O

    [SoYouStart] rEFInd/Grub Boot Error (Upgrading Proxmox 6 to 7)

    rEFInd is used by OVH in order to provide the rescue for your server in cas something goes wrong, it is loaded from a PXE on OVH's infrastructure, it is not installed inside the server. It also allows the installation of the OS from OVH. By changing the boot order, you actually skip this rEFInd...
  3. O

    [SoYouStart] rEFInd/Grub Boot Error (Upgrading Proxmox 6 to 7)

    This looks good to me, at this point i believe you've got the "grub" situation sorted, my guess is an issue with the network interfaces. Easiest would be for your to connect to the IPMI if you can, otherwise if you are limited to rescue mode, check in /var/log if you can to see if there is...
  4. O

    [SoYouStart] rEFInd/Grub Boot Error (Upgrading Proxmox 6 to 7)

    When you are in rescue mode, just try to do "fdisk -l" to check if you can see two EFI partitions. Here's mine, while system is running from PVE though : # fdisk -l Disk /dev/nvme0n1: 419.19 GiB, 450098159616 bytes, 879097968 sectors Disk model: INTEL SSDPE2MX450G7 Units: sectors of 1 * 512 =...
  5. O

    [SoYouStart] rEFInd/Grub Boot Error (Upgrading Proxmox 6 to 7)

    Hey guys, i had the same issue on a couple of servers we just got from soyoustart, i found the reason there is an issue and a solution. The issue is because the servers have multiple disk drives, in my case 2 nvmes. OVH created EFI partitions on both drives, with the same label, so you can't be...