Installed Garuda on separate SSD to WIndows 11 SSD (NVME), Windows bootloader updated but on boot cannot find device, grub rescue

Hi All

I have read through a lot of guides and FAQs first but am struggling to find the best answer to try and resolve my issue without a fresh install and the need to disconnect my Windows OS which is installed onto my Samsung EVO M.2 NVME SSD.

Throughout this process within the BIOS (UEFI) I have secure and fast boot disabled, and my SATA controller mode set to ACHI.

I know this is a related to this post here around the same multiiple SSD setup but in Ubuntu:

Dual Booting win 10 and Ubuntu 18.04 on two separate physical ssds - Ask Ubuntu

I understood that during the Garuda installation it was going to add/update a partition on my main M.2 SSD, to allow an option for Garuda to boot, I was ok with this as long as it didn’t affect my ability to boot into Windows (which it hasn’t). During the installation I had Garuda itself installed onto a new SSD.

After a successful install onto the new SSD I changed the boot order to be the new option now showing in the BIOS for: “Garuda (M.2_1: Samsung SSD 970 EVO).” Garuda itself was installed onto a new SSD like I’ve mentioned already so I assume this is the Garuda boot file placing itsellf onto my main Windows 11 M.2 SSD.

However when the PC attempts to boot from this option I get hit with a black screen with the following:

error: no such device: edd3d8fd…
error: unknown filesystem.
Entering resuce mode…
grub rescue>

On typing “ls” I see that the SSD with Garuda on is showing (hd5), (hd5,gpt1)

The device UID shown in the error message is the correct device name that has been assigned to this SSD, confirmed by booting up Garuda off the USB stick and checked it in the device listing.

Any ideas please folks? I can still boot into Windows just fine by changing the 1st boot option back to: “Windows Boot Manager (M.2_1: Samsung SSD 970 EVO)”.

Thanks in advance :slight_smile:

It’s explained in this forum a thousand times.
Live ISO, garuda-welcome, chroot, grub-install /def/xyz, update-grub.

Please, always post garuda-inxi, maybe from live ISO if nothing works.
Without garuda-inxi this request will be moved to 412 Precondition Failed

1 Like

Thanks SGS.

Which drive should Grub be installed onto, the SSD with Garuda on it or the M.2?

EDIT: I will follow this guide:

What part of this did you not understand?

You ignored the template and my polite request, hence my question.

As a precaution, I’m moving it to 412 Precondition Failed because consistently is one of my easiest exercises.

I made first post a wiki, so you can add the log from garuda-inxi.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.