Hello everyone, yesterday I successfully installed the Garuda Gaming Edition on my computer without any issues. However, after the installation, when I clicked “Restart” to complete the post-installation setup, the disk no longer appears — neither in Fast Boot nor in the BIOS. It’s as if the drive doesn’t exist at all.
Let me explain more clearly: my primary drive, C (1TB M.2 SSD), has Windows installed on it, and since there wasn’t enough unallocated space, I installed Garuda on my secondary drive, D (500GB M.2 SSD), by creating a 90GB partition for it. (I did this installation just for testing purposes — if I liked it, I was planning to switch fully to Garuda.)
As I mentioned, the installation finished successfully, but after restarting, the secondary 500GB SSD (previously labeled as D) no longer shows up — neither in Fast Boot nor in the BIOS. Is there any solution for this? What could I have done wrong?
I’m new to Linux. In my BIOS settings, the system is set to UEFI mode, and both Secure Boot and Fast Boot are disabled, as well as TPM 2.0.
I don’t know what AHCI means, so I’m not sure whether it’s enabled or disabled.
Since I’m new to Linux, I don’t know at which stage or with which key I should open the console to enter the command mentioned in the thread, or how to view the output if I run it from the live desktop panel.
To provide clearer and more helpful information, let me explain my issue again:
My main drive (C drive in Windows) has Windows installed. Because there’s no free space, I couldn’t shrink or partition it to install Linux.
My secondary drive (D drive in Windows) is used to store games, documents, photos, and other data, independent of the operating system. From this D drive, I created a 90GB partition (which appeared as F drive in Windows) to test Linux. I installed Garuda Linux successfully on this 90GB F partition.
However, after restarting the system, in the Fast Boot menu only the primary C drive (with Windows) and the USB drive containing the Linux ISO are visible.
In the BIOS boot priority list, I can see the Samsung EVO 1TB SSD and the USB drive, but the second drive — the ADATA 500GB SSD — is missing. Therefore, neither the 500GB SSD nor the 90GB Linux partition can be accessed.
Interestingly, when I boot into Windows, I can see both the C and D drives, but the F partition (where I installed Linux) has disappeared.
So, my question is: was my mistake installing Linux on the secondary drive instead of the primary one? Would installing it on the main Samsung EVO 1TB SSD solve the issue, or is that unrelated?
M$ have no access to os garuda linux. It can’t read nothing from partitions created with ext 3/4 / btrfs / zfs / lvm. That is not a error. Only with special apps the user have access to this kind of partitions.
Default yes, it is unrelated and the better choice was garuda linux to installed on another drive.
Important is only what is with uefi partiton and your bios settings for csm / uefi / ahci mode.
You must make the right settings for this inside bios.
Look in the bios option “boot.” Change the boot order to garuda current you load default M$(windows).
and…also important is
Boot the live iso and post then the garuda-inxi. Open konsole / terminal → garuda-inxi or use rani to do this.
I’ll send the output you mentioned to the forum as soon as possible.
However, I’m not sure how to obtain that output. Should I type the command you provided into the panel while using the Garuda live desktop?
If so, how can I save the information or data that the panel returns as an output file?
Or is the command you mentioned intended to work only on an already installed system? Because I can’t access the installed Garuda system — I can only use the live environment.
When I run the live desktop, everything works fine until I complete the installation and reboot. So how can the garuda-inxi command capture or report a problem that hasn’t occurred yet?
That make no sense, sorry. (tech specs like this)
You don’t have read the info as you have opened this topic.
Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>), or put three tildes (~) above and below the text
I understand. Thank you for your help. I’m at work right now, but I’ll try to submit the report to the forum as soon as I get off. I really hope my issue gets resolved — I’d love to switch to Garuda Linux since I liked it a lot. If it doesn’t work out, my only option will be to return to the Windows ecosystem.
Let me explain the BIOS changes I made before installing Garuda Linux:
Secure Boot: Disabled
TPM 2.0: Disabled
UEFI: Enabled
With these settings, I downloaded the latest Garuda ISO from the official website last night and wrote it to a USB flash drive using Ventoy. Then, I booted from the USB drive and launched the Garuda live desktop.
From there, I ran the Garuda installation wizard. During the setup, I selected my second drive, allocated 90 GB of space, and allowed the installer to format it as Btrfs. I set the mount point as /. It didn’t allow me to proceed if I tried to select /boot or other options.
At one stage — I don’t remember exactly when — I got a warning saying something like “Go back to assign the partition named X” (X being the partition name). Since I didn’t know what to do, I just continued and clicked Install now.
The installation proceeded normally, showing messages such as “Formatting partition as Btrfs” and “Extracting installation files”. It finished successfully and gave me the option to Restart.
However, after restarting, Garuda does not appear as a boot option — neither in the BIOS boot priority list nor when I try fast boot options.
Only / = btrfs isn’t enough. You must have a bootable uefi partition for the boot loader.
Without, it’s impossible with your system to boot into garuda linux.
That is / was your mistake. You have to created a partition vfat32 size 300MB, bootable and mounted as /boot Default is this partiton on the beginnig of the drive.
Next time if you read error messages, search in the great www, use here the forum search.
The warning you mentioned was probably about the 300 MB pre-load/boot area, but I didn’t know how to create it, so I just proceeded. I don’t have much knowledge about Linux; Windows usually sets up the boot memory and settings on its own. Therefore, it would be very helpful if you could explain step-by-step how to set it up. There aren’t many forums or sites with information about Linux, or people with knowledge about it, in my region, so it will be difficult for me to search and find. I would appreciate it if you could help me.
The installer app, calamares, did everything for you if you point to a (free) partition on your hard drive, it’s just easy.
No need to create or format /, /boot/efi and so on.
Describe your issue in detail. The more we know, the better we can help
Show us the results of your searches, and what you’ve tried
After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>), or put three tildes (~) above and below the text
The template above should be deleted before posting your help request.
But only if he use the windows drive, not another.
Then he “must” make this manual or can “only” delete. (my mind)
My example on a vm dr460nized with gpt partition table + ntfs partition.
Only two options exist.
21/24 checks run in 0.68 seconds ⌛
Powered by garuda-health 🦅
--- CRITICAL ---
- No (intended) kernels are installed in /boot (fix available)
--- HIGH ---
- Snapper snapshots directory is missing (fix available)
--- LOW ---
- Failed systemd services found: snapper-cleanup.service
Run garuda-health --fix to apply fixes.
--- Applying Fixes ---
Fixing "Snapper snapshots directory is missing":
The following command will be executed:
garuda-update remote reset-snapper
Continue? [y/N]: y
You are still booted into a snapshot.
Snapper configuration reset to default successfully.
Fixing "No (intended) kernels are installed in /boot":
The following command will be executed:
sudo dracut-rebuild
Continue? [y/N]: y
:: Rebuilding all initramfs due to changes in dracut files.
:: Building initramfs for linux-zen (6.16.8-zen3-1-zen)
:: Building fallback initramfs for linux-zen (6.16.8-zen3-1-zen)
Note: It may be necessary to manually update the system's bootloader configuration to prevent boot issues.
Initramfs rebuilt successfully using dracut.
--- Re-running checks after applying fixes ---
--- System Health Check Report ---
21/24 checks run in 0.60 seconds ⌛
Powered by garuda-health 🦅
--- HIGH ---
- Snapper snapshots directory is missing (fix available)
--- LOW ---
- Failed systemd services found: snapper-cleanup.service
Run garuda-health --fix to apply fixes.`
Now these were written in the console. What path should I follow?
Missing information requested in the template may result in not receiving assistance 
