If I choose Systemd-boot my system enters BIOS on restart. If I choose GRUB it gives a return 1 error. When I try to manually install grub it gives grub-install: command not found error.
First what information can I give you to help with this? I am posting fdisk -l, keep in mind I have been going at this for a while now so this is not the only setup that I have tried.
I suspect the boot file needed for bios to recognize the drive is being placed somewhere the bios cannot find it with systemd-boot. I don’t know how to install grub from the live cd so the command can be found. The usb drive did pass when I checked it.
Because the installer will not let me use both drives on a normal install. I end up having to use them like windows c and d drives; where c is the main drive and d is like a spare drive for storage or backups, etc. I want to use them both for the system, but it is not letting me format the 2nd drive and mount it to /home, for instance. Also, Linux based systems just don’t use root like they used to. You just don’t need the space for it any more. So I would prefer /home be much larger, since that does get used.
give some more info on what exactly the issue is here.. its a fresh install? and it needs indeed some more info why there is a raid system of some kind:
You can also not really simply mic grub and systemd bootloaders.. if you have instzalled selecting systemd-boot it will not switch to grub by installing grub package it would need to switch some things to work. As with systemd-boot ESP efi fat32 Partition is mounted on /efi with Grub on /boot
First, I explained in a previous response why the raid drive. Please read that.
Second, A more full explanation of the situation:
I created the raid drive using mdadm as instructed. No problems. I installed on the raid drive choosing grub and erase disk. The choice failed giving a grub return error 1 message. So, I tried to follow the instructions for manually installing grub and I received a grub-install: command not found error. So I started over deleting the previously made partitions on the raid drive. On this install I tried systemd-boot and erase disk. It installed and on restart it just entered bios. The bios reports the drives as existing but in the boot section no drives exist until I reboot with the usb, and then only the usb partitions exist (in the boot section). So I tried manually partitioning the raid drive, but that gives the exact same results in both cases.
instructed by archwiki? The installer is not offering raid creation.
from the error on “grub-install not found” it looks like you tried to run this from the Live Session not from inside chrooted into your installed system. As of if you install selecting Grub it should have it installed. Even if not you could reinstall grub package from inside the arech-chroot on the installed system.
the system you have just installed is the target you want to fix, to act like it would be booted you use chroot to handle inside the installed system and not on the Live Session of the Installer ISO.
I know my bios is up to date, but I am not able to read (German?) Deustch? I can not even remember if those are the same language or not. Lol I am embarassed. Please forgive me for that.
They snuck in an update this year?! Go Asus. Alrighty, I guess I should work on that. Also, it makes me nervous because of recent trends of over zealous controls that both corporate and government have been heaping on us.
There are 13 newer UEFI Bios updates for this motherboard.
Edit: My suggestion is to update the UEFI Bios. Then make sure the Bios settings are set correctly. Disable Secure Boot, Fast Boot , CSM and RAID. Hard drives settings should be AHCI.
Then wipe the drives with any raid setup you created and install fresh without any RAID setup using the install and select grub.
