"The selected boot device failed" error... [Solved]

[Uliwat432]

Hello, everyone. Hope you're having a good start to your week.

I'm trying to install Linux and facing this issue: I install it, but then when I turn it off then turn it on again later, the installation didn't happen. I can only use MX Linux from the Live USB stick; if I try to turn it on without the USB stick, I get that error message on the subject line.

I'm migrating from Windows 10, used Rufus. I erased Windows 10. So, no double-boot.

Also, I apologize if this problem has been solved before; I did look around and found fairly similar situations such as this one: viewtopic.php?f=92&t=52377&p=523994&hil ... ed#p523994 but different PC's etc. so, I thought I should try asking cause my system might be very different.

I'm on MX Linux 19.2 "Patito feo", 64-bit. My laptop: HP Notebook-15-bw005la. Copying and pasting quick system info:

Code: Select all

System:    Host: <filter> Kernel: 5.10.0-5mx-amd64 x86_64 bits: 64 compiler: N/A 
           parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=en_US 
           tz=America/Mexico_City 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_ahs_x64 patito feo March 31  2021 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: HP product: HP Laptop 15-bw0xx v: Type1ProductConfigId 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: HP model: 8330 v: 27.26 serial: <filter> UEFI: Insyde v: F.11 date: 07/05/2017 
Battery:   ID-1: BAT1 charge: 26.3 Wh condition: 26.3/31.1 Wh (85%) volts: 12.2/11.1 
           model: Hewlett-Packard PABAS0241231 type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: AMD A9-9420 RADEON R5 5 COMPUTE CORES 2C+3G bits: 64 
           type: MCP arch: Excavator family: 15 (21) model-id: 70 (112) stepping: N/A 
           microcode: 6006704 L2 cache: 1024 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 11976 
           Speed: 2695 MHz min/max: 1400/3000 MHz boost: enabled Core speeds (MHz): 1: 2695 
           2: 2694 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Stoney [Radeon R2/R3/R4/R5 Graphics] vendor: Hewlett-Packard 
           driver: amdgpu v: kernel bus ID: 00:01.0 chip ID: 1002:98e4 
           Display: x11 server: X.Org 1.20.10 driver: amdgpu,ati 
           unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz 
           OpenGL: renderer: AMD STONEY (DRM 3.40.0 5.10.0-5mx-amd64 LLVM 11.0.1) 
           v: 4.5 Mesa 20.3.4 direct render: Yes 
Audio:     Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:01.1 
           chip ID: 1002:15b3 
           Device-2: AMD Family 15h Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 00:09.2 chip ID: 1022:157a 
           Sound Server: ALSA v: k5.10.0-5mx-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus ID: 02:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8723DE 802.11b/g/n PCIe Adapter vendor: Hewlett-Packard 
           driver: rtw_8723de v: N/A port: 2000 bus ID: 03:00.0 chip ID: 10ec:d723 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 960.33 GiB used: 695.0 MiB (0.1%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> 
           rev: RSM7 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 3.0 size: 28.82 GiB 
           block size: physical: 512 B logical: 512 B serial: <filter> scheme: MBR 
Partition: ID-1: / raw size: N/A size: 8.90 GiB used: 695.0 MiB (7.6%) fs: overlay 
           source: ERR-102 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 45.0 C mobo: 20.0 C gpu: amdgpu temp: 44 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           2: deb http://mxrepo.com/mx/repo/ buster ahs
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 204 Uptime: 1h 24m Memory: 11.18 GiB used: 1.65 GiB (14.7%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

I think I have a fair idea of what I must do, but wanted to consult with you first, clear doubts and make sure I got it right step-by-step...

I think it has something to do with turning off secure boot and UEFI Firmware. If there's a way to get it done without having to re-install Windows, let me know. If not, I think I'll install Windows again from an USB stick, turn off secure boot and then remove it and use straight Linux (though I'd still have Windows on the USB stick in case I needed it for anything, right?), and I'd also appreciate your help in getting all of the steps right in using Windows again, turning off secure boot, removing Windows and successfully running MX Linux without the USB stick.

I also looked into this thread and the steps look useful, but it's for Mint, not MX; so, maybe it's completely different. https://learningpenguin.net/2018/07/13/ ... -mode/amp/

I think I have to make it boot from the hard disk?

Is changing UEFI to Legacy a possibility? Is it advisable?

Would a virtual box help with this?

Also, I've read that another solution could be having my laptop formatted (or just the hard disk, I think or something along those lines to unable secure boot).Thoughts?

Making sure MBR is on disk, not USB? Maybe install in ESP instead of MBR?

And I think that once I have secure boot off, I have to use boot repair (from the live USB)?

Also, sorry if it's missing any info; feel free to ask questions, ask for more specs etc.

Thank you in advance!

[Huckleberry Finn]

Welcome to the forum (and also to Linux and MX Linux) :)

Copying and pasting quick system info:

Just, I wish you just directly pasted without copying. Because there were code tags and users skip them when copying. So, can you please edit your post (pencil icon) and highlight all the info then click this icon </>

Edit: Thank you, that's it :)

[Huckleberry Finn]

Till then: viewtopic.php?p=652361#p652361

(If you don't have Rufus anymore and the others look confusing, we can tell how to. You can prepare another stick with that one on live session with GPT option checked, or start with toram parameter and use that usb stick again, we'll tell in case you need)

[j2mcgreg]

My Probook dates from the same time as yours and in HPs of that era "legacy" has been interpreted to mean that you can roll back to an earlier version of Windows. It does not mean that you can do a non-uefi install of another operating system (I found this out the hard way). In your bios all you have to do is disable secure boot and select your primary boot device. Here's my QSI for reference:

Code: Select all

System:    Host: <filter> Kernel: 4.9.221-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
           v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.221-antix.1-amd64-smp 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19.4_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: HP product: HP ProBook 450 G5 v: N/A serial: <filter> Chassis: 
           type: 10 serial: <filter> 
           Mobo: HP model: 837D v: KBC Version 02.2D.00 serial: <filter> UEFI: HP 
           v: Q85 Ver. 01.03.00 date: 07/20/2018 
Battery:   ID-1: BAT0 charge: 44.6 Wh condition: 45.1/45.1 Wh (100%) volts: 12.7/11.4 
           model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Unknown 
CPU:       Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP arch: Kaby Lake 
           family: 6 model-id: 8E (142) stepping: A (10) microcode: E0 L2 cache: 6144 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 
           Speed: 800 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           5: 800 6: 800 7: 800 8: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: conditional, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Hewlett-Packard driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:5917 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.3.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard 
           driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 
           Sound Server: ALSA v: k4.9.221-antix.1-amd64-smp 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: Hewlett-Packard driver: r8169 v: 2.3LK-NAPI port: 3000 bus ID: 01:00.0 
           chip ID: 10ec:8168 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: 3000 
           bus ID: 02:00.0 chip ID: 8086:24fd 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 465.76 GiB used: 19.14 GiB (4.1%) 
           ID-1: /dev/sda vendor: Seagate model: ST500LM021-1KJ152 size: 465.76 GiB block size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: YXM1 scheme: GPT 
Partition: ID-1: / raw size: 463.48 GiB size: 455.21 GiB (98.21%) used: 19.14 GiB (4.2%) 
           fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 46.0 C mobo: 0.0 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ buster main contrib non-free
           2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
           No active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
Info:      Processes: 282 Uptime: 13m Memory: 7.76 GiB used: 764.4 MiB (9.6%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in 
           running in: quick-system-in inxi: 3.0.36 

You'll see that I am running the 4.9 kernel. I had a problem with the sound card and using this kernel was a quick fix. The sound card problem has since been rectified but since the Probook is performing well, I haven't bothered to switch back to the default.

[Uliwat432]

(If you don't have Rufus anymore and the others look confusing, we can tell how to. You can prepare another stick with that one on live session with GPT option checked, or start with toram parameter and use that usb stick again, we'll tell in case you need)

I think I don't have Rufus anymore (must have gotten deleted when I erased Windows); any way to know for sure? I tried looking for it in All Apps, and nothing.

[Huckleberry Finn]

Ah, ok.. No Rufus on Linux .. That's not a must, I just meant in case you use it somewhere on Windows.. So, you can go on with MX Live Usb Maker from Menu. You can use that live session and prepare another stick (if you have one available) -do as demonstrated in the link: check "GPT partitioning" - then boot with and use that stick for installation.

Or, if the current live usb is the only available stick, it's possible to boot with that using the "toram" feature: That way all the live-system will be loaded to Ram first, then you can use that stick to prepare same way.. (We'll tell how to "toram" if needed.. Roughly: The way you added lang=en_US tz=America/Mexico_City add toram )..

[Uliwat432]

Ah, ok.. No Rufus on Linux .. That's not a must, I just meant in case you use it somewhere on Windows.. So, you can go on with MX Live Usb Maker from Menu. You can use that live session and prepare another stick (if you have one available) -do as demonstrated in the link: check "GPT partitioning" - then boot with and use that stick for installation.

Or, if the current live usb is the only available stick, it's possible to boot with that using the "toram" feature: That way all the live-system will be loaded to Ram first, then you can use that stick to prepare same way.. (We'll tell how to "toram" if needed.. Roughly: The way you added lang=en_US tz=America/Mexico_City add toram )..

For now, this is the only available stick but I could buy a new one in roughly a month; let's try toram first, then....I'm gonna do a search on booting with toram, but feel free to tell me a step-by-step process to make sure I don't get anything wrong, or link me to a tutorial page etc.

[MXRobo]

@Uliwat432 "toram"
viewtopic.php?p=653604#p653604

[fehlix]

Hello, everyone. Hope you're having a good start to your week.

I'm trying to install Linux and facing this issue: I install it, but then when I turn it off then turn it on again later, the installation didn't happen. I can only use MX Linux from the Live USB stick; if I try to turn it on without the USB stick, I get that error message on the subject line.

If the installation went through without any errors and you installed GRUB into the ESP, the issue might related to UEFI/NVRAM settings within the system firmware. What I would try first to check whether you can boot into the installed MX Linux, using "Boot Rescue Menu" from the MX LiveUSB boot menu and select search for "GRUB EFI boot loaders".
If it would boot from boot rescue menu I would try to find within UEFI firmware settings an option to boot from (EFI) file.
So don't think creating another LiveUSB would solve the original issue.

Also when booted from LiveUSB show the current partition structure and UEFI/NVRAM entries,
with running these three commads:

Open terminal as normal user and run

Code: Select all

lsblk --fs -o +PARTUUID

and

Code: Select all

sudo parted --list

and

Code: Select all

sudo efibootmgr -v

Copy/paste the text output between those [code]code tags [/code] e.g. using [</>] button,
for better readability.

[Uliwat432]

Hey, guys...so, I did the toram thing...either I did it wrong or it didn't work...I went to the menu, it was the 4th option, took a while to load it into ram etc. (and the customized toram appears now as part of the main boot menu...if I click it, it loads it to ram all over again) then I tried installing Linux, it was fine and then I turned it off, turned it on again without the Live USB and BAM! again "the selected boom device failed". So, did I forget about something?

As for the next suggestion, when I looked for EFI boot, I got a "No EFI boot loaders found" message.

And here are the three commands:

Code: Select all

demo@mx1:~
$ lsblk --fs -o +PARTUUID
NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT PARTUUID
loop0
     squash                                                           /live/linu 
sda                                                                              
├─sda1
│    vfat         5B7C-B227                                                      e2a410a7-5fc5-484f-ad46-9d74fa23864b
├─sda2
│    ext4   rootMX19
│                 e93cdb66-8e8d-4109-8b03-b7112d753eda                           92e82611-83e7-4d40-903c-bdd2ca3c87bb
└─sda3
     swap   swapMX
                  61f670a5-bf17-4f11-b124-64db49f1101e                [SWAP]     0df356fa-5079-44ff-9d28-3c95dad5a0af
sdb                                                                              
└─sdb1
     vfat   MX-LIVE
                  DCB5-34F8                                                      0fc6f023-01
sr0                                      

And:

Code: Select all

demo@mx1:~
$ sudo parted --list

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for demo: 
Model: ATA ST1000LM035-1RK1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name     Flags
 1      1049kB  269MB   268MB   fat32           ESP      boot, esp
 2      269MB   998GB   998GB   ext4            primary
 3      998GB   1000GB  2147MB  linux-swap(v1)  primary


Model: Kingston DataTraveler 3.0 (scsi)
Disk /dev/sdb: 30.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  30.9GB  30.9GB  primary  fat32        boot, lba

Finally:

Code: Select all

$ sudo efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 2001,0002,3002,0000,2002,2004
Boot0000* EFI Hard Drive (ST1000LM035-1RK172)	PciRoot(0x0)/Pci(0x11,0x0)/Ata(0,0,0)/HD(1,GPT,e2a410a7-5fc5-484f-ad46-9d74fa23864b,0x800,0x80000)RC
Boot0001* USB Hard Drive (UEFI) - KingstonDataTraveler 3.0 (KingstonDataTraveler 3.0)	PciRoot(0x0)/Pci(0x12,0x0)/USB(0,0)/USB(0,0)/HD(1,MBR,0xfc6f023,0x800,0x39a2bf4)RC
Boot0002* MX19	HD(1,GPT,e2a410a7-5fc5-484f-ad46-9d74fa23864b,0x800,0x80000)/File(\EFI\MX19\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot3002* Internal Hard Disk or Solid State Disk	RC
demo@mx1:~
$