That is the only error you got so I’m not sure why it’s reporting that as i don’t know what you did to lose the entries in grub?
when i try just sudo chroot it works, but then this wont work
grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-mkconfig: line 52: /usr/share/grub/grub-mkconfig_lib: No such file or directory
i also tried this as instructed in the previous post but alas does not work either
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EnOS
grub-install: error: cannot find a device for /boot/efi (is /dev mounted?).
i have no idea, nothing is on the GRUB and it just shows the UEFI Firmware setting.
think i might have done something to the entries in the grub.cfg, as i was looking at something in their. i was using vim so must have removed something maybe? or commented something out?
Well you have to be arch-chrooted and if it’s not finding it then needs to be determined why? Maybe @pebcak could help as he seems to be good at this.
1 Like
Did you edit the default grub command?
yes well luckly, i dont have anything important saved on their, as i duel boot EOS as im still learning and i like messing around with things.
i would also like to thank you rick, when ever i have had a problem you have always been one of the first to respond and help me out so thanks for that 
You can post the grub file. Post the link
cat /etc/default/grub | eos-sendlog
i opened it up in vim. i was also renaming the entries in grub customizer, after that i was looking more into grub customization and had a look in the grub.cfg file, i was using vim to edit this file so i think i might have put something in their perhaps?
# GRUB boot loader configuration
GRUB_DEFAULT="saved"
GRUB_DISTRIBUTOR="EndeavourOS"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 nowatchdog nvme_load=YES nvidia-drm.modeset=1"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK="y"
# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
# Uncomment to use basic console
GRUB_TERMINAL_INPUT="console"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT="console"
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX="keep"
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID="true"
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY="true"
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_BACKGROUND="/usr/share/endeavouros/splash.png"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
GRUB_SAVEDEFAULT="true"
# Uncomment to disable submenus in boot menu
GRUB_DISABLE_SUBMENU="y"
# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
GRUB_DISABLE_OS_PROBER="false"
GRUB_TIMEOUT_STYLE="menu"
GRUB_TIMEOUT="10"
GRUB_THEME="/boot/grub/themes/CyberRe/theme.txt"
GRUB_GFXMODE="auto"
Okay…all i can tell you is that grub customizer is bad news. It can screw things up very quickly.
sound advice, ill give it a miss from now on. also probably would have been a good idea to start with Pop_os or something easier but decided to jump right into a arch based distro and now i cant live without the AUR lmao
I would not use grub-customizer. You are better off without it.
1 Like
Can’t really see any issue here but if you have grub customizer it’s probably in the entries somewhere in the actual grub files.
1 Like
okay cheers for all your help man, you are always first to post on topics i make and i appreciate you helping this noob out. thanks for being patient also.
lesson i have learned today.
how to mount my linux partition so i can chroot into it, unfortunately it isnt working but this information may be useful in the future. if something similar like this happens again.
DO NOT use grub customizer,
1 Like
The easiest way to recover from grub customizer is to rename the directory /etc/grub.d to something else and then reinstall the package grub. That will set your grub config back to default.
Then re-run sudo grub-mkconfig -o /boot/grub/grub.cfg
2 Likes
hey mate, thanks for replying but i choose the easy way out and just reintalled EOS.
if this happens again, which it hopefully wont as i am just going to stay away from Grub Customizer. ill give this ago.
should i just mark something as the solution?
I feel with you, had to reinstall linux many times, because of “experiments”.
For grub, I learned lately that the config is really simple and that I don’t need extras tools.
sudo mount /dev/nvme1n1p2 /mnt -o subvol=@
sudo mount /dev/nvme1n1p1 /mnt/boot/efi
sudo arch-chroot /mnt
This is how I used to arch-chroot on btrfs (only skimmed this thread, just got up!!). My endeavour btrfs was on nvme1n1p(x) (now on XFS!).
2 Likes
yeah ngl, like learning this stuff, linux really is just fun to play around with. when i first started i hated the terminal, i thought it was so stupid. but now i love using it. im also studying ethical hacking and i feel like its an OS system im going to have to get used too.