Real noobish question... started endeavouros from USB stick now no start disks

I don’t know where to begin, I have a desktop computer with 3 SSDs, one for Win 11 (work stuff) and one for different Linux distors. The third is a common storage disk for both systems.
I am very accustomed to computers and different OS. I have used different Linux distros for the last 10-15 years.

Today after work I thought I would check out endeavourOS, so I installed it on a free USB stick, restarted and started from it. EndeavourOS showed up I started GParted to check what disk to use, /dev/sdb, formatted using trusted gparted.
Checked no mistakes made, still a Win-disk and a newly formatted disk to use.
Started the installer, did not finalize that, came to the step where one chooses what disk to install to. Then one of my kids got home and wanted to play a game, sure I said and quit the installer and restarted the computer.

Now I end up in UEFI/BIOS, system says there is no boot disk, I see that the three disks are connected. But none of them have a bootalble system.

What did just happen? On the sdb disk I had PopOS with a failed Grub install, the system were set to start from the Win11 disk.

I have no idea what just happened, anyone that ha any clue and can give me a hint?

Please send output of

sudo fdisk -l
sudo efibootmgr -v

Tell which disk has which purpose on first command.
If I understood correctly, your PC booted directly into Windows previously and now it can’t boot at all.

I wish I could, the computer don’t regonize any disk as a boot device.
Could it be the faulty grub install that caused this?
If I install EOS on its disk I can give the output of those commands.

Could be so that the boot record for Windows was written to the disk I formatted?

Boot from the install media and run the commands given from there.

sudo fdisk -l

Disk /dev/sda: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: KINGSTON SKC6005
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 622A20A8-B852-447B-9A72-8ED6E1734F3D

Device         Start        End   Sectors   Size Type
/dev/sda1       2048      34815     32768    16M Microsoft reserved
/dev/sda2      34816  997765119 997730304 475,8G Microsoft basic data
/dev/sda3  997765120  998944767   1179648   576M Windows recovery environment
/dev/sda4  998946816 1000212479   1265664   618M Windows recovery environment


Disk /dev/sdb: 465,76 GiB, 500107862016 bytes, 976773168 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: gpt
Disk identifier: 89219815-511B-DB4E-B0F7-378594E26658

Device         Start       End   Sectors   Size Type
/dev/sdb1       4096    618495    614400   300M EFI System
/dev/sdb2     618496 904713355 904094860 431,1G Linux filesystem
/dev/sdb3  904713356 976768064  72054709  34,4G Linux swap


Disk /dev/sdc: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000BX500SSD1 
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: CD927079-468B-492D-84D5-B13331CA9B4C

Device     Start        End    Sectors   Size Type
/dev/sdc1     34      32767      32734    16M Microsoft reserved
/dev/sdc2  32768 1953521663 1953488896 931,5G Microsoft basic data

sudo efibootmgr -v
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* endeavouros-6567	HD(1,GPT,6d83452a-cabf-c945-b637-80013607668e,0x1000,0x96000)/File(\EFI\ENDEAVOUROS-6567\GRUBX64.EFI)
      dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 2a 45 83 6d bf ca 45 c9 b6 37 80 01 36 07 66 8e 02 02 / 04 04 48 00 5c 00 45 00 46 00 49 00 5c 00 45 00 4e 00 44 00 45 00 41 00 56 00 4f 00 55 00 52 00 4f 00 53 00 2d 00 36 00 35 00 36 00 37 00 5c 00 47 00 52 00 55 00 42 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0001* UEFI OS	HD(1,GPT,6d83452a-cabf-c945-b637-80013607668e,0x1000,0x96000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
      dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 2a 45 83 6d bf ca 45 c9 b6 37 80 01 36 07 66 8e 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 00 00 42 4f

I should also add that I installed EOS on the Samsung Drive, Windows is on the Kingston drive.

If you reboot and call up the boot manager (F12 on my laptop), what happens if you tell it to boot from the windows drive?

I am not good with windows, I have it on this laptop on a separate drive, only because it is new :smiley:

Edited for typo it is F12 not F11 :blush:

Thing is that when I do that the UEFI says there is no boot device. Now there is, this EOS Samsung SSD. It seems like Win doesnt have a boot record.

You are going to have to repair the windows bootloader, found this which looks comprehensive:

I have been out of the loop for more than a decade, so will bow out :smiley:

1 Like

if you create a new bootloader like grub or any other it will write a new entry into efi system firmware and this one will be the new default boot entry of the system.

So it could be that you have installed EndeavourOS on USB drive and it does not see this one (may unplugged?) so there is no boot device…

But you should be able to press F12 on boot and get a manual device list to boot.

Doe snot…

No ESP (EFI System Partition) would normally indicate that the system is installed in Legacy/MBR/Bios mode.

I guess in order to be able to boot your Windows install, you would need to enable Legacy/CSM boot mode in your firmware settings.

2 Likes

Da snot! :wink:

1 Like

good catch…

1 Like

I will make a guess here:

It looks like you actually started EndeavourOS installation and proceeded far enough to install a bootloader but bootloader installation failed.

Also, for some reason, Windows bootloader was residing on the disk you just formatted so you wiped Windows boot files too. Your boot files don’t reside on Windows partition because there is no EFI system partition.

Install EndeavourOS as normal (to /dev/sdb) if you wish to use EndeavourOS. If you want to repair Windows, you need a Windows boot disk.

1 Like

Thing is when I tried to setup Grub it failed. At least I was not able to boot into PopOS.
Win still worked for some reason, up until today that is.

Well it is Windows you have to reinstall it twice a year or so…

You are most probably right. Thing is when I use the Win install media and try to repair it doesn’t find anything. So I have decided to reinstall the whole shebang.

If you are going to reinstall the whole shebang then make sure secure boot and CSM are disabled and it is set to UEFI only. Install Windows back on the disc you want it installed and then install EndeavourOS on the other disc. Should not be any problem to dual boot Windows with EndeavourOS.