Failed to open |EFI\proxmox\grubx64.efi Error please help!

[gfngfn256]

Do the following:

nano /etc/apt/sources.list.d/pve-install-repo.list

# enter the following:

deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

ctrl+x to exit & press enter to save

__________

nano /etc/apt/sources.list.d/ceph.list

# add the following:

deb http://download.proxmox.com/debian/ceph-quincy bookworm no-subscription

ctrl+x to exit & press enter to save

After that repeat the above update with:

apt-get update

apt-get dist-upgrade

 

[BonelessMilk]

Do the following:

nano /etc/apt/sources.list.d/pve-install-repo.list

# enter the following:

deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

ctrl+x to exit & press enter to save

__________

nano /etc/apt/sources.list.d/ceph.list

# add the following:

deb http://download.proxmox.com/debian/ceph-quincy bookworm no-subscription

ctrl+x to exit & press enter to save

After that repeat the above update with:

apt-get update

apt-get dist-upgrade

I am now getting

root@pve:™# apt-get update


Hit:1 http://security.deblan.org bookworm-security InRelease


Hit:2 http://ftp.us.debian.org/deblan bookworm InRelease


Hit: http://ftp.us.debian.org/debian bookworm-updates InRelease


Err:4 https://enterprise.proxmox.com/debian/pve bookworm InRelease


401


Unauthorized [IP: 170.130.165.90 449]


Ign: https://dounload.proxmox.com/debian/ceph-quincy bookworm InRelease


Ign:6 https://dounload.proxmox.com/debian/pve bookworm InRelease


Ign:5 https://dounload.proxnox.com/debian/ceph-quincy bookworm InRelease


Ign:6 https://dounload.proxmox.com/deblan/pve bookworm InRelease


180:5 https://dounload.praxmox.com/debian/ceph-quincy bookworm InRelease


Ign:6 https://dounload.proxmox.com/debian/pve bookworm InRelease


Err:5 https://dounload.proxmox.com/debian/ceph-quincy bookworm InRelease


Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected.


Err:6 https://dounload.proxmox.com/deblan/pve bookworm InRelease


Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected.


Reading package 1ists... Done


E: Failed to fetch https://enterpr/se.proxmox.com/debian/pve/dists/bookworm/InRelease


E: The repository 'https://enterprise.proxmox.com/deblan/pve bookworm InRelease'


491


Unauthorized [IP: 170.130.165.90 443)


N: Updating from such a repository can't be done securely,


is not signed.


and is therefore disabled by default.


N: See apt-secure(B) manpage for repository creation and user configuration details.

 

[gfngfn256]

It looks like you have not updated those repos, or maybe they are not saving correctly.
Please show output again for the above post.

 

[BonelessMilk]

It looks like you have not updated those repos, or maybe they are not saving correctly.
Please show output again for the above post.

root@pve:*# cat /etc/apt/sources.list.d/pve-install-repo.list deb https://dounload.proxmox.com/debian/pve bookworm pve-no-subscription root@pve: *# cat /etc/apt/sources.list.d/ceph.list deb https://dounload.proxmox.com/debian/ceph-quincy bookworm no subscription rootpve: *# cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian bookworm main contrib deb http://ftp.us.debian.org/debian bookworm-updates main contrib


# security updates


deb http://security.debian.org bookworm-security main contrib

 

[gfngfn256]

You have spelled dounload instead of download. Carefully check all the changes I instructed above & change accordingly. Better would be to copy the text & paste it in nano (removing the incorrect lines).

 

[gfngfn256]

Also you have changed them to https when I told you http.

Linux in general is very unforgiving for even small typos.

 

[BonelessMilk]

Also you have changed them to https when I told you http.

Linux in general is very unforgiving for even small typos.

Sorry for the typos but that was from the screenshot reading the words wrong, so from now on I’m am going to send screenshots please let me know if you’re able to view them. Download was spelled correctly but I did accidentally put an s at the end of https, so I fixed that error and retried and am getting

 

[gfngfn256]

You could try doing now apt install --reinstall grub-efi-amd64 & see what happens.

But I'm going to give you a different piece of advice:

Your Proxmox instance appears quite compromised & seemingly has never been updated. (Proxmox does not upgrade by itself).
Assuming you only had/have 2 VMs on that server, & you should have a full & restorable backup of them (somewhere else - not on that drive), I would do the following.

1. Check that disk drive for errors thoroughly. (Boot up from a different OS to do this).
2. Format/wipe completely that drive (assuming it is still good) - or get another enterprise grade disk.
3. Freshly install Proxmox.
4. Restore those VMs from backup.

In general you need to familiarize yourself with the PVE OS - to be able to avoid these pitfalls in the future.

please let me know if you’re able to view them

I could just about see it. But why can't you copy & paste the text from an SSH session? I'm not prepared to squint over those images, nor suffer your seemingly inaccurate OCR in your post outputs. You should check it carefully before posting.

 

[BonelessMilk]

You could try doing now apt install --reinstall grub-efi-amd64 & see what happens.

But I'm going to give you a different piece of advice:

Your Proxmox instance appears quite compromised & seemingly has never been updated. (Proxmox does not upgrade by itself).
Assuming you only had/have 2 VMs on that server, & you should have a full & restorable backup of them (somewhere else - not on that drive), I would do the following.

1. Check that disk drive for errors thoroughly. (Boot up from a different OS to do this).
2. Format/wipe completely that drive (assuming it is still good) - or get another enterprise grade disk.
3. Freshly install Proxmox.
4. Restore those VMs from backup.

In general you need to familiarize yourself with the PVE OS - to be able to avoid these pitfalls in the future.


I could just about see it. But why can't you copy & paste the text from an SSH session? I'm not prepared to squint over those images, nor suffer your seemingly inaccurate OCR in your post outputs. You should check it carefully before posting

1. I just tried to reinstall grub but started getting the error that the paths that were trying to be reinstalled were in read only so I’m going to agree with you that my installation of proxmox is quite corrupted and will reinstall

2. After booting up proxmox from a usb in recovery mode I was able to access the gui from a web browser but now when I try to I’m getting the error “connection refused” same with trying to SSH into the machine any ideas so I could get my files?

 

[gfngfn256]

any ideas so I could get my files?

Not sure what files you mean. As I said above you should have fully restorable backups on a different medium (not that boot disk).
Do you have any backups anywhere?

 

[BonelessMilk]

Not sure what files you mean. As I said above you should have fully restorable backups on a different medium (not that boot disk).
Do you have any backups anywhere?

Sadly not I was in the process of backing them up but was looking around for the best way to do it. I wasn’t really in a rush because this server is still relatively new being less than 6 months old so I thought I had more time. I would like to get a copy of the VMs I had on there if you know a way, if not it’s not too big of a deal since I didn’t have too much important on there anyway.

 

[gfngfn256]

Well you learnt the hard way - you must always have backups; 6 months?!

Anyway, basically the VMs consist of a config file & it's virtual disk/s. You may be able to recover these by attaching an external drive, mounting it, & copying over the relevant files.

If you enter qm config <VMID> you should be able to see the VM's exact config. From there you can work out which disks they have & probably copy these over to an external drive. You could also copy over the VM's config file, which should be located at /etc/pve/nodes/MINS-PRXMX/qemu-server/ .

Something that will be relevant, will be the file/storage structure, you have at present. You can probably check that with lsblk .

 

[BonelessMilk]

You could try doing now apt install --reinstall grub-efi-amd64 & see what

So I rebooted the system and was able to get CODE:apt install —reinstall grub-efi-amd64 to work and from there I attempted CODE: apt-get update only to get the same error I was getting before, but then I tried apt-get dist-upgrade and got it to install properly! So now after rebooting I am at the GNU GRUB version 2.06-13+pmx2 screen. Any ideas where to go from here?

 

[gfngfn256]

2.06-13+pmx2

That should probably be 2.06-13+pmx5, but I guess we are again suffering from typos. I'm as fed up as you are.

I've already pointed out above what you need to do. As far as retrieving "files" I've also given you pointers above, mind you these may already be corrupted like the rest of your system. You also say yourself that they are not very important - so why should we waste our time.

Just start again.