UEFI no longer recognizes Garuda drive

OK, so I've got a NEW AND INTERESTING crazy issue! So, maybe this is purely hardware related, because I DID recently install an ASUS BIOS update, to the latest and debatabley greatest version at the time of this writing which is 3402. Maybe some of you have seen something similar, but after updating I had to do a cold boot, maybe the first actual COLD boot in, well, I can't even remember the last time I powered the whole system down. Certainly not since the last power outage in my neighborhood! So, moving on, the UEFI firmware detects my drive, it's a Sabrent Rocket 4.0 500GB drive occupying the second NVMe slot on my MB....the primary/1st slot is holding a Corsair Force MP600 Gen4 x4 1TB drive that's holding my (ugh! I wish it weren't so!) Win10 install, the 2nd NVMe (the Sabrent) is where Garuda is installed, and my 4TB WD Black HDD is connected via SATA and is the "storage" drive both both systems....Now, I just use F8 during boot to bring up the boot menu and choose which drive/OS to boot from, usually, even though grub DID find my Windows install and add it to the boot menu on the nvme1n1p1 EFI partition....The Corsair drive is encrypted using VeraCrypt system encryption because I don't trust freaking MS and their freaking BitLocker bullshit and the Garuda drive is encrypted using LUKS- minus the FAT EFI partition (nvme1n1p1).....now fast forward to currently and my UEFI boot menu no longer shows the Sabrent drive or the boot partition as a bootable drive- to boot my installation at this point I have to use a USB stick with the live image and use the "detect UFI partitions" menu option, where it IMMEDATELY finds ALL the partitions on my drive, boots no problem and keeps on keeping on....what I can't figure out is, obviously there's nothing wrong with my grub configuration and there's obviously nothing wrong with the boot partition, so why isn't my firmware detecting it and allowing me to select it at boot time or put it in the boot sequence? I'm not saying I necessarily dislike the idea of needing to use the USB stick to boot the OS, as I feel like it just adds another layer of security, and although I won't get into WHY I'm so security conscious, let's just say I'd just as soon avoid anyone (the NSA included) from being able to access my data.......bottom line, though, is why doesn't my UEFI firmware any longer see the drive?

Have any of you ever seen such a thing? Do you think it's likely the UEFI firmware update, should I try reverting? And can anyone think of a potential solution?


The NMVe drives sometimes have issues being detected that's why I've personally steered clear of them.

There's no universal cure. You'll have to search all the Arch distros for a fix.

1 Like

Your hardware listens to your prayers. :wink:
It's a pure hardware/firmware/UEFI problem/dis-function.
If you really want to change this lawful pet functionality, maybe let it out of power for a day and try again.
Desktop? Remove MB battery for half an hour.

If no change, install an older UEFI version

Or ask the vendor.

1 Like

Yeah i might try a few of the older uefi versions....i jumped from like 2602 to the latest version without any incremental updates along the way, so it's very possible an older one may be more stable... Guess I'll just be playing guessing games with it for a while lol