Installed windows on a new drive, it wiped systemd-boot

Hey! Thanks for responding to this - I’m going to mark this as the solution as it’s basically what I did.

So I booted up from usb, and stumbled across this thread - GRUB is gone after new drive install - #10 by pebcak

As I was following the following instructions in this thread - Help to install bootloader on dual boot (windows 10/endeavouros) - #4 by pebcak
(Of course changed the drives in my case that pertain to my setup

[matcha@matcha-machine ~]$ sudo parted -l
[sudo] password for matcha: 
Model: ATA Samsung SSD 840 (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      2097kB  1076MB  1074MB  fat32           EFI          boot, esp
 2      1076MB  247GB   246GB   ext4            endeavouros
 3      247GB   256GB   9449MB  linux-swap(v1)               swap

sudo mount /dev/sda2 /mnt
sudo mkdir -p /mnt/boot/efi 
sudo mount /dev/sda1 /mnt/boot/efi
sudo arch-chroot /mnt  ------> Stopped following here because I wanted systemd - not grub
pacman -S grub
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=enos-grub
exit

I then pivoted to the following command:

sudo bootctl install --path=/mnt/boot/efi

After that I reloaded and I able to boot back into my EndeavourOS install.

Should I be concerned that I didn’t run reinstall-kernels? or am I safe?

Thanks!

1 Like