Yes secure boot disabled
fast boot disabled
and also something called CSM disabled
Perfect thatâs what you want. Are you able to boot on the live ISO and use gparted and show the image of what it shows for the partitions? Just to verfy.
Edit: You can post a screen image of gparted.
So if you try to install and use replace partition and click on the partition you want to install it to which would be /dev/sda7 and i assume you used systemd-boot as i see the /dev/sda6 which is the /efi ⌠what happens?
I also tried the replace patition mode and installer freeze at 82%
Is it freezing because of downloading mirror issues? I would try booting on the live ISO and update the mirrors first. Then run the installer and try again.
Edit: Iâm not sure what country you are in and what mirrors you would be using?
I donât think it is a mirror issue since I tried the offline as well and no matter what I do it freezes when it shall install the bootloader at around 80 % and then I cant get any log filesâŚso maybe if there could be some strange way to monitor the logfiles on another machine so it will stay there when it freezes. I also did update the mirrors. the german ones
I would try using US mirrors. I just donât see a reason why it should fail.
iâll try. us mirrors. replace /dev/sda7
Freezes at 82% Installing Bootloader⌠
Try this:
Your goal is to install without the system to freeze. If it goes successfully, then you have time to make a plan for the bootloader.
There are several options, that all include chrooting to complete the system.
Apart from standard systemd-boot and grub, you might use refind, or even create an EFI entry for the kernel. Also, you can use some trick from inside windows (as long as there is a bootloader file).
Thanks for the support everybody. Right now I succeded on installing EOS without boot loader. So the plan now is to somehow get a boot loader installed so I would be able to actually start the EOS. Earlier problems with that is that as soon as the new boot loader try to write something system freezes again, so I have to trick the windows boot loader to think is is the âlinux oneâ
Microsoft Windows boot loader location
On certain UEFI motherboards like some boards with an Intel Z77 chipset, adding entries with efibootmgr or bcfg from the UEFI Shell will not work because they do not show up on the boot menu list after being added to NVRAM.
This issue is caused because the motherboards can only load Microsoft Windows. To solve this you have to place the .efi file in the location that Windows uses.
Copy the BOOTx64.EFI file from the Arch Linux installation medium (FSO:) to the Microsoft directory your ESP partition on your hard drive (FS1:). Do this by booting into EFI shell and typing:
Shell> mkdir FS1:\EFI\Microsoft
Shell> mkdir FS1:\EFI\Microsoft\Boot
Shell> cp FS0:\EFI\BOOT\BOOTx64.EFI FS1:\EFI\Microsoft\Boot\bootmgfw.efi
After reboot, any entries added to NVRAM should show up in the boot menu.
but I still need to also install the boot loader I guess
Still thinking, but open to suggestions
What is your current disk layout?
sudo parted -l
Could you mount your system partition:
sudo mount /dev/sda7 /mnt
and post the output of the following commands?
cat /mnt/etc/fstab
ls -al /mnt/boot
Also:
sudo blkid -o list
I already mounted with sda6 and sda7
sudo mount /dev/sda7 /mnt
sudo mount /dev/sda6 /mnt/efi
should I unmount sda6 again?
No, itâs alright.
We can try installing Grub (the package) and see if we can create an EFI boot entry manually.
Run this to chroot:
sudo arch-chroot /mnt
In chroot:
pacman -S grub
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=EnOS --no-nvram
If this works without errors, then
efibootmgr -c -d /dev/sda -p 6 -w -L EnOS -l '\EFI\EnOS\grubx64.efi'
Taking to account the failed attempts so far, this is just another try to see if we can finally get this thing going for you.
If not, we have to find some other solution.
Failure is no option 
1 Like
First thing worked grub installed - no errors
Next command efibootmgr -c -d /dev/sda -p 6 -w -L EnOS -l '\EFI\EnOS\grubx64.efi'
System freeze 
So guess we should look for another solution. Do you think I can keep what is already installed? or has it been broken by what I just did?
Nothing broken. You can keep it.
Iâm just stumped that so many attempts to create an EFI boot entry fails resulting in a frozen system.
If
grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=EnOS --no-nvram
was successful and if other forum mates wonât be coming up with a better and a working solution, there might be a way to create a boot entry for EnoS but from Windows (!), using something like EasyBCD.
Cannot guaranty that it would work. But just pointing out another option.
I tried EasyBCD and it did not work because of âwindows limitationsâ and eFi boot mode it says.
Iâll research some moreâŚmayby give refind a try. Thanks alot.
1 Like