My bootloader keeps disappearing

For some reason, my Manjaro bootloader keeps disappearing. I have to reinstall the bootloader then, and it boots fine after, once or twice, but then I get a message saying that there is no valid bootloader on the system. I've reinstalled my bootloader maybe a dozen times now, and this is driving me crazy.

What's strange is that I can still see the manjaro directory in my EFI partition, along with Grub and all the required files. I don't know why they aren't being recognized by my system.

I'm running the latest manjaro-gnome, on a Lenovo Yoga-C930, which uses EFI. I'm dual-booting Manjaro and Windows. Windows only runs in "secure boot" mode, so I'm booting Manjaro with secure boot disabled.

I don't boot into Windows hardly ever, so I don't think this is something that Windows is doing.

I have the EFI partition mounted to /boot/efi. There might be some weird stuff in there, though. Here's the contents of /boot/efi:

drwxr-xr-x 2 root root     4096 Okt  5 21:15 73dcbf575b5b440bbfdaa2578892f462/
-rwxr-xr-x 1 root root    31232 Okt  5 20:37 amd-ucode.img*
drwxr-xr-x 2 root root     4096 Okt  4  2018 BOOT/
drwxr-xr-x 6 root root     4096 Okt  5 21:22 EFI/
drwxr-xr-x 2 root root     4096 Jun 21 22:23 f2430490894d40fc817da3434dd7c0a9/
drwxr-xr-x 2 root root     4096 Okt  5 20:42 grub/
-rwxr-xr-x 1 root root 30584291 Okt  5 20:37 initramfs-5.2-x86_64-fallback.img*
-rwxr-xr-x 1 root root  8581459 Okt  5 20:37 initramfs-5.2-x86_64.img*
-rwxr-xr-x 1 root root 30682610 Okt  5 20:41 initramfs-5.3-x86_64-fallback.img*
-rwxr-xr-x 1 root root  8584160 Okt  5 20:41 initramfs-5.3-x86_64.img*
-rwxr-xr-x 1 root root  2577920 Okt  5 20:37 intel-ucode.img*
-rwxr-xr-x 1 root root       21 Okt  5 20:37 linux52-x86_64.kver*
-rwxr-xr-x 1 root root       20 Okt  5 09:49 linux53-x86_64.kver*
drwxr-xr-x 3 root root     4096 Okt  6 10:49 loader/
-rwxr-xr-x 1 root root  6257024 Okt  5 20:37 vmlinuz-5.2-x86_64*
-rwxr-xr-x 1 root root  6347136 Okt  5 09:49 vmlinuz-5.3-x86_64*

And here's the output of tree /boot/efi:

jon@jon-laptop ~> tree /boot/efi
/boot/efi
├── 73dcbf575b5b440bbfdaa2578892f462
├── amd-ucode.img
├── BOOT
│   └── BOOT.SDI
├── EFI
│   ├── Boot
│   │   └── bootx64.efi
│   ├── Insyde
│   ├── manjaro
│   │   └── grubx64.efi
│   └── Microsoft
│       ├── Boot

  --- A bunch of MS stuff here --

├── f2430490894d40fc817da3434dd7c0a9
├── grub
│   ├── grub.cfg
│   └── grubenv
├── initramfs-5.2-x86_64-fallback.img
├── initramfs-5.2-x86_64.img
├── initramfs-5.3-x86_64-fallback.img
├── initramfs-5.3-x86_64.img
├── intel-ucode.img
├── linux52-x86_64.kver
├── linux53-x86_64.kver
├── loader
│   ├── entries
│   │   ├── nixos-generation-47.conf
│   │   ├── nixos-generation-48.conf
│   │   ├── nixos-generation-49.conf
│   │   ├── nixos-generation-50.conf
│   │   ├── nixos-generation-51.conf
│   │   ├── nixos-generation-52.conf
│   │   └── nixos-generation-53.conf
│   ├── loader.conf
│   └── random-seed
├── vmlinuz-5.2-x86_64
└── vmlinuz-5.3-x86_64

There are some relics of NixOS there that I can probably remove. But does anything look off?

can you returns

inxi -Fxxxza
sudo parted -l
sudo efibootmgr

is you disk set on AHCI in bios ?

1 Like

Sure.

System:
  Host: jon-laptop Kernel: 5.2.19-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.2-x86_64 
  root=UUID=73e4ed50-5577-4fc0-8e1e-4df4303f7e07 rw quiet udev.log_priority=3 
  audit=0 resume=/dev/disk/by-uuid/028e3651-ab3a-4b7f-ac58-2929a62bbfb2 
  Desktop: Gnome 3.34.0 wm: gnome-shell dm: GDM 3.34.0 Distro: Manjaro Linux 
Machine:
  Type: Convertible System: LENOVO product: 81C4 v: Lenovo YOGA C930-13IKB 
  serial: <filter> Chassis: type: 31 v: Lenovo YOGA C930-13IKB serial: <filter> 
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: <filter> UEFI: LENOVO 
  v: 8GCN32WW date: 10/09/2018 
Battery:
  ID-1: BAT1 charge: 50.6 Wh condition: 50.6/60.0 Wh (84%) volts: 8.6/7.7 
  model: Simplo BASE-BAT type: Li-poly serial: <filter> status: Unknown 
CPU:
  Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP 
  arch: Kaby Lake family: 6 model-id: 8E (142) stepping: A (10) microcode: B4 
  L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31880 
  Speed: 1182 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 966 2: 900 3: 900 
  4: 900 5: 900 6: 900 7: 901 8: 900 
  Vulnerabilities: 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 
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5917 
  Display: wayland server: X.org 1.20.5 driver: i915 compositor: gnome-shell 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) 
  v: 4.5 Mesa 19.2.0 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel 
  v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 
  Sound Server: ALSA v: k5.2.19-1-MANJARO 
Network:
  Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel port: 3040 
  bus ID: 6b:00.0 chip ID: 8086:2526 
  IF: wlp107s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 238.47 GiB used: 120.46 GiB (50.5%) 
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFS256GD9TNG-62A0A size: 238.47 GiB 
  block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
  serial: <filter> rev: 80001E00 scheme: GPT 
Partition:
  ID-1: / raw size: 78.12 GiB size: 76.40 GiB (97.79%) used: 37.11 GiB (48.6%) 
  fs: ext4 dev: /dev/nvme0n1p5 
  ID-2: /home raw size: 110.18 GiB size: 107.95 GiB (97.98%) used: 83.19 GiB (77.1%) 
  fs: ext4 dev: /dev/nvme0n1p6 
  ID-3: swap-1 size: 8.81 GiB used: 49.5 MiB (0.5%) fs: swap 
  swappiness: 10 (default 60) cache pressure: 50 (default 100) dev: /dev/nvme0n1p7 
Sensors:
  System Temperatures: cpu: 41.0 C mobo: 29.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 250 Uptime: 2h 31m Memory: 11.48 GiB used: 4.09 GiB (35.6%) 
  Init: systemd v: 243 Compilers: gcc: 9.2.0 clang: 8.0.1 Shell: fish v: 3.0.2 
  running in: gnome-terminal inxi: 3.0.36 
Model: Unknown (unknown)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 


                                                                          
Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  274MB   273MB   fat32           EFI system partition          boot, esp
 2      274MB   290MB   16,8MB                  Microsoft reserved partition  msftres
 3      290MB   43,4GB  43,1GB                  Basic data partition          msftdata
 5      43,4GB  127GB   83,9GB  ext4
 6      127GB   246GB   118GB   ext4            home
 7      246GB   255GB   9455MB  linux-swap(v1)  swap
 4      255GB   256GB   1049MB  ntfs                                          hidden, diag

jon@jon-laptop ~> sudo efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,2001,2002,2003
Boot0000* EFI USB Device (Samsung Flash Drive FIT)
Boot0001* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network

I'm not sure whether it's AHCI or not. I can try to find that.

Refer this
Boot up Manjaro and at terminal

sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

If problem persists and 'manjaro' entry continues to be missing from 'efibootmgr' after you rebooted, take a look at this.

1 Like

with return of efibootmgr ,
bios or windows remove entry boot in EFI bios for manjaro

explain? I will not assume what you mean before responding.
You may mean something else.

because of this --> entry boot EFI is removed
maybe come from not see nmve disk

Oh, okay.
But windows boots okay and is in nvme disk, meaning bios sees the nvme disk.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by