I made a big mistake and installed garuda. while windows 10 was on another ssd.
I had no idea garuda would erase the win10 UEFI.
Anyways, Im now trying to create a rescue / install usb for win 10 and dont know how to get garuda to create such a install usb. Im a bit stranded here.
Can you please help me with a fix to my problem.
Is the win10 rescue USB even necessary ?
Hi there, welcome to the forum.
Normally Garuda does not erase anything unless selected in the partitioning step of the installer.
Could you please provide your
efibootmgr
Maybe you have two EFI system partitions, one in each disk, and you can select the other at BIOS level when needed or change the order in efibootmgr.
sudo fdisk -l
Disk model: INTEL SSDPEKNW020T8
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: dos
Disk identifier: 0x671ed331
Device Boot Start End Sectors Size Id Type
/dev/nvme1n1p1 * 2048 4000794623 4000792576 1,9T 7 HPFS/NTFS/exFAT
Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: KINGSTON SNV2S1000G
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: A032F8E2-7AB6-40B6-A444-48B6FC2492EB
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1953523711 1953521664 931,5G Microsoft basic data
Disk /dev/sdc: 232,89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 850
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: dos
Disk identifier: 0x18c4e44c
Device Boot Start End Sectors Size Id Type
/dev/sdc1 63 488395119 488395057 232,9G 42 SFS
Disk /dev/sdb: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: CT2000BX500SSD1
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: 5C8B966D-B805-446B-9D56-FA78A2C95AD8
Device Start End Sectors Size Type
/dev/sdb1 34 32767 32734 16M Microsoft reserved
/dev/sdb2 32768 3907026943 3906994176 1,8T Microsoft basic data
Disk /dev/sda: 232,89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 840
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: dos
Disk identifier: 0x52b3f6e3
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 206847 204800 100M 6 FAT16
/dev/sda2 206848 488394751 488187904 232,8G 7 HPFS/NTFS/exFAT
Disk /dev/sdd: 3,64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870
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: 2BCD3FA3-0281-43F7-9C31-EEA41F2B8B27
Device Start End Sectors Size Type
/dev/sdd1 4096 618495 614400 300M EFI System
/dev/sdd2 618496 7814032064 7813413569 3,6T Linux filesystem
Disk /dev/zram0: 62,72 GiB, 67345842176 bytes, 16441856 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sde: 14,93 GiB, 16034824192 bytes, 31318016 sectors
Disk model: USB Flash Drive
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: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sde1 2048 31309823 31307776 14,9G 7 HPFS/NTFS/exFAT
The last one is the USB I try to use as rescue USB. I already figured out how to format it to ntfs! Unfortunately I cant get the win10.iso to ‘extract’ properly on it yet.
I took a look and it doesn’t appear Windows is using UEFI to begin with, actually:
A UEFI system will have another partition there (the EFI partition). It looks like Windows was installed in “legacy” mode.
If you have disabled CSM in order to install Garuda, you will have to re-enable it to boot back to Windows. It will not be possible to to get them both on the same boot menu if one is in UEFI mode and one is in legacy mode; you will have to manually switch from one to the other in the BIOS menu every time.
no UEFI for your windows install means that you’ll need to set your BIOS to UEFI mode and reinstall windows and then Garuda.
before doing so however you may want to back up your data from your windows user profile folder in from a live disk.
you should be able to navigate the drive and copy your personal data to another device.
don’t forget to copy the hidden ‘Appdata’ folder in C:/users/(profilename), it has many saved things like video game save files and other saved application data you will more than likely want to keep, browser profile data for one.
once you’ve backed up your data, i highly recommend re-partitioning the drive before you reinstall windows and give it it’s own space while saving another space for Garuda.
a ‘pro-tip’ for everyone is to always set your BIOS options correctly regardless of the OS you use.
Ok, that might seem like a troll question, but sadly im running into a problem reading USBs.
I tried many usbs but everytime now I get:
An error occurred while accessing ‘Win10’, the system responded: The requested operation has failed: Error mounting system-managed device /dev/sde1: Unknown error when mounting none
The partition manager can partition them - succesfully - But then cannot open them.
Yesterday it seemed to work.
Restarting didnt help.
Edit:
The solution is to mount it in the partition manager, not the dolphin explorer.
Im a linux noob stumbling around.