I guys I make a mess with my endeavour installation and I don’t know hot to solve this without format again everything.
I had an SSD with:
Win 10 + endeavour single ext4 partition.
For some incompatibility with laptop I’ve get rid of win 10 and install win 8.1 but as I thought now boot is messed and I can only boot win.
I tried to restore grub with live USB but it doesn’t work or maybe I’ve followed the wrong steps.
Can you please help me to solve this so I can also understand what happened?
Thanks
pebcak
October 1, 2021, 12:31pm
2
Hi @manadipendente and welcome to EnOS’ forum!
Please boot up your live usb and run the following command in a terminal:
sudo parted -l
and
efibootmgr -v
Copy the output and paste it to your reply using the </> button to format. Hopefully this will give enough info about your setup to some forum member who can help you out.
PARTED
Model: ATA SAMSUNG MZ7TE256 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot, esp
2 106MB 123MB 16.8MB Microsoft reserved partition msftres
3 123MB 83.9GB 83.8GB ntfs Basic data partition msftdata
4 83.9GB 256GB 172GB ext4 root
Model: USB DISK (scsi)
Disk /dev/sdb: 8054MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 32.8kB 1963MB 1963MB ISO9660 hidden
2 1963MB 2066MB 103MB fat16 Appended2 boot, esp
3 2066MB 2066MB 307kB Gap1 hidden, msftdata
EFIBOOT
BootCurrent: 0020
Timeout: 2 seconds
BootOrder: 0002,0001,001B,001C,001D,001E,001F,0020,0021
Boot0001* EndeavourOS HD(1,GPT,f0328a4a-a3ef-4279-bfd4-37cae381dfa0,0x800,0x32000)/File(\EFI\EndeavourOS\grubx64.efi)
Boot0002* Windows Boot Manager HD(1,GPT,f0328a4a-a3ef-4279-bfd4-37cae381dfa0,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...6................
Boot0014 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0015 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0016 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0017 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0018 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0019 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot001A MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot001B* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001C* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot001D* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001E* ATA HDD1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot001F* ATA HDD2 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
Boot0020* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0021* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0022* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot0023* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot0024* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0025* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
Boot0026* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
I hope this can help
pebcak
October 1, 2021, 12:47pm
4
manadipendente:
BootCurrent: 0020
Timeout: 2 seconds
BootOrder: 0002,0001,001B,001C,001D,001E,001F,0020,0021
Boot0001* EndeavourOS HD(1,GPT,f0328a4a-a3ef-4279-bfd4-37cae381dfa0,0x800,0x32000)/File(\EFI\EndeavourOS\grubx64.efi)
Boot0002* Windows Boot Manager HD(1,GPT,f0328a4a-a3ef-4279-bfd4-37cae381dfa0,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...6................
Looks like you already have an EFI boot entry for EnOS. You could try changing the boot priority in your Bios/firmware settings.
Or change the boot order from the live usb:
sudo efibootmgr -o 0001,0002,001B,001C,001D,001E,001F,0020,0021
If the boot entry is “intact” you should be able to boot into your EnOS.
Once in EnOS you would, most probably, need to do the following in order for Windows to be added to your Grub boot menu:
https://discovery.endeavouros.com/installation/grub-dual-booting/2021/07/
I have an error: no such partition and in in grub rescue
pebcak
October 1, 2021, 1:53pm
6
You could try installing the bootloader once again.
Run:
sudo su
mount /dev/sda4 /mnt
mount /dev/sda1 /mnt/boot/efi
arch-chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EnOS
grub-mkconfig -o /boot/grub/grub.cfg
Also check the UUIDs in /etc/fstab correspond to the ones you get from
lsblk -fs
When done, type exit
to get out of chroot.
Check again
efibootmgr -v
to make sure that the new boot entry "EnOS’ is first in order.
Reboot.
Hopefully this will resolve the issue.
3 Likes