I beg your help about a fresh eos installation on an old laptop Asus X552M. The installation stopped at grub step exited with error 1. I read all topics it was possible to help me in my case, I tried all tips which were advised but none worked for me
As I understood, I can consider than eos is installed, I just need to correct the issue with grub, am I right?
Below the commands and their returns I got:
[firstname.lastname@example.org ~]$ sudo efibootmgr -V
Which mean this 17?
[email@example.com ~]$ sudo bootctl status
Couldn’t find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
Firmware: UEFI 2.31 (American Megatrends 5.09)
Secure Boot: disabled (disabled)
TPM2 Support: no
Boot into FW: supported
Current Boot Loader:
Product: systemd-boot 251.2-1-arch
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Load drop-in drivers
✗ Boot loader sets ESP information
Passed to OS: no
System Token: not set
Copying and executing commands, without knowing what they do, will eventually lead you to a system and/or hardware damage. Be cautious and read documentation. I say this because you have made several mistakes.
From the installer ISO, start a terminal and confirm your target (installation) drive is /dev/sda.
Then mount the two partitions (root and esp) and try to install grub again. If there is an error message, post all terminal content here, so we can advise you further.
Thank’s a lot for your help, I agree about the mistakes I could have done, this kind of troubleshooting is too hard for me, all documentations I will able to read, I will have so many questions behind
I did your troubleshooting, I accessed to the boot menu, now only these 2 lines are displayed, nothing more, finished by an hard reboot
Loading Linux linux-lts …
Loading initial ramdisk …
As requested, the logs you asked me to do:
[firstname.lastname@example.org ~]$ sudo mount /dev/sda2 /mnt
[email@example.com ~]$ sudo mount /dev/sda1 /mnt/boot/efi
[firstname.lastname@example.org ~]$ sudo grub-install --target=x86_64-efi --efi-directory=/mnt/boot/efi --boot-directory=/mnt/boot --bootloader-id=Grub --force
Installing for x86_64-efi platform.
Could not prepare Boot variable: Input/output error
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
[email@example.com ~]$ sudo grub-install --target=x86_64-efi --efi-directory=/mnt/boot/efi --boot-directory=/mnt/boot --bootloader-id=SystemGrub --force --removable
Installing for x86_64-efi platform.
Installation finished. No error reported.
If you want to maintain your sanity, you need to start reading and learning about Linux systems, since you are attempting to be a Linux system administrator.
Or did you think that it’s just a game, like those you like to play in WinOS? No, no, no!
The second grub installation command seems it has succeeded. You are probably ready.
You should be able to boot to EnOS, using the UEFI Quick Boot menu (shortcut key can be found in User Manual), and try all entries. If there is one that displays the drive (like HDD TOSHIBA… or similar), try it first.
You tried this on the USB installer system, which is not possible, and… does not make much sense
Anyway, it looks like you have one of the bad UEFI firmware and you may need more work than is usually required.
I suggest you have patience, or just try Ubuntu, Mint, Fedora or WinOS.
you have some confusion about the Live Session and the installed system.
You can not run a command on the live session to change the installed system without following the right mount and path … /boot/grub/grub.cfg is a path on the “ISO”
To change installed system you need to mount the needed partitions to a mount point like /mnt and you can change stuff using the path under /mnt on installed systemfiles…
If you need to run commands onto installed system you will need to use chroot or better arch-chroot to get into the installed system and be able to run commands like you where booted into the same…