I am trying to reinstall garuda dragonized kde on my system, and am running into some issues with it installing grub.
I have tried manual partitioning, replace partition, as well as install alongside and ran into the same error at the end of install, to which I am greeted with the grub recovery screen upon reboot.
The bootloader could not be installed. The installation command <pre>grub-install --target=i386-pc --recheck --force /dev/nvme0n1</pre> returned error code 1.
My output from fdisk -L (for the drive windows and garuda should be installed on)
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO 500GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 1673D03E-0608-46BE-86D1-DE7F888796B0
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 206847 204800 100M EFI System
/dev/nvme0n1p2 206848 239615 32768 16M Microsoft reserved
/dev/nvme0n1p3 239616 500654807 500415192 238.6G Microsoft basic data
/dev/nvme0n1p4 500654808 976773134 476118327 227G EFI System
This system uses EFI boot and this drive uses GPT as its partition table
Any point in the right direction would be appreciated, I have looked at the garuda boot repair option but can't seem to find a forum post that explains it for my use case.
garuda-inxi isnt showing up as a command on the live iso, after updating the pkgfiles and trying to install from garuda-common-settings(-git) somethings broke there too
output from normal inxi
the efi thats set right now is from the installer, not quite positive why it is showing that entire partition as an efi system rather then dividing a smaller efi like it was when I did it manually.
Can you clarify a little on the last sentence? I am a little lost at
But if you use nvme0n1p4 in calamares the installer do the rest. IIRC
One distinctly odd piece of your output is the filesystem of nvme0n1p4 is marked as EFI, even though that should be the root filesystem. I don’t know if that is enough to throw off grub, but it is definitely not what you want.
When you are in the manual partition part of the installer, you should be mounting two partitions. One mounted at /boot/efi and not formatted (the EFI partition, at nvme0n1p1), and the second at / formatted btrfs at nvme0n1p4.
When I did the manual partitoning, I used what I found on this post for uefi systems
specifically this
For uefi
You need to create one 300 mb fat32 partition and mount it as >/boot/efi and flag it with esp and boot
And one btrfs partition mount it as /
One odd thing however is my install shows /boot as a mount point but not /boot/efi. I tried installing with just /boot and I ran into the same grub issue.
The whole it flagging the entire partition as an EFI system is recent, that only happened after I tried to install by “replacing a partition”
I apologize, I should have put /boot/efi, that is correct for this system. I edited my post above.
There is a lot going on in that post you linked!
You don't need to create any FAT32 partition. You already have the EFI partition that Windows made. There is plenty of space and multiple systems can "piggyback" on the same EFI drive as long as it is on the same physical drive.
Make sure you select p1 (your EFI partition) in the manual partition process (click the "edit" button or whatever), choose to mount it at /boot/efi, but do not format because you want to preserve the data that is already on there.
Then, you should also select p4, choose "format", and if it doesn't default to btrfs then change it to btrfs. Choose / for the mount point on the dropdown menu. If you want to give the FS a label (Garuda, for example) feel free but it is not required. Don't select any of the flag boxes for p4.
Does that sound like something you have already tried?
I haven't tried piggybacking off the windows efi system, I believe I was creating a second one when I was manually partitioning . (Which may have been my issue in the first place)
Do i need to set the bios-grub flag for that efi partition as well? Right now it is just flagged as boot.
I might be wrong about this, but I don't think those flags are that important unless you are booting legacy. Grub doesn't care about the flags and is able to find what it needs other ways, and an EFI partition is defined by its special GUID type (not by any flags). I have never bothered to manipulate those flags myself--I would just leave them as they come up by default.
Just tried your solution, ran into the same error code unfortunately,
The bootloader could not be installed.
The installation command
<pre>grub-install --target=i386-pc --recheck --force /dev/nvme0n1</pre> returned error code 1.~~~
After checking, legacy boot is disabled on everything in bios. I tried disabling CCM as well but that made be unable to boot the live iso anymore (install media is mbr maybe?)
At this point I am starting to think I may be better of chrooting into the system and manually installing grub, if thats even a viable option.
Ill try that out, I just set it up the same way as I have all my other boots. Download the iso, pass it to etcher and go from there. I'll boot back onto windows and redo the boot media.
That ended up being the solution!
Thank you so much for the help! Everything is installed and booting properly.
For later readers of this post,
I disabled CSM to force all things to be efi, then used Ventoy to set up the live boot media to use GPT partitions, rather then the MBR that was set on it from Etcher.
)