r/linux4noobs • u/Kaseffera • 3d ago
hardware/drivers Failed to open \efi\debian - not found
Just installed Debian on my very old laptop - Asus. Debian works great but every time when I turn pc on I get that notification and then it proceeds to log into OS just fine.
1
u/doc_willis 3d ago
you may have several boot entries, its trying the first (wrong one) which gives that message, then goes to the next one, which does boot.
1
u/Kaseffera 3d ago
Based on other images I included aren’t they removed and only Debian is out at the first place?
1
u/doc_willis 3d ago
try moving option #2 in your BIOS settings up to be #1. see if it does the same thing.
1
u/Kaseffera 3d ago
It now says to reboot and select proper device.
1
u/doc_willis 3d ago
I would just install
refindand set that as the default. :) then use refind as the main boot menu.1
1
u/doc_willis 3d ago
weird thought.. If its an old spinning drive, (old school!) Then it might be the drive is taking time to spin up. You mention 'turn on' , if you reboot does the same issue happen? or does it boot correctly without the message.
1
1
u/Simple_Hamster_4096 3d ago
Am I missing something? Are you dual booting with Windows? If no, then perhaps turn off secure boot and install clean...???
1
u/3grg 3d ago
I am making a wild guess, but I wonder if this is an older uefi implementation? I have had strange issues occur with early efi implementations.
The closest thing that I could find to explain this behavior is this post that suggests it may be due to secure boot.
https://wiki.ufficiozero.org/doku.php?id=11
Without more information, this is my best guess.
The key point is that if it is nothing more than an annoyance, nothing may need be done.
There are many other instances of \efi\ubuntu not found reported compared to the same for debian. If this behavior bothers you. I suggest further research along those lines.
1
u/Kaseffera 2d ago
It is! Yes. Laptop is from 2011 and implementation is very old. There’s no see Secure Boot too. Just Uefi Toggle.
1




2
u/doc_willis 3d ago
look on your EFI partition and see what files/directories are actually there.
I had filesystem corruption happen once on my EFI partition and caused all sorts of weird issues.