Lost bios entry

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
tmarsh
Level 1
Level 1
Posts: 16
Joined: Tue Jul 06, 2021 10:39 am

Lost bios entry

Post by tmarsh »

I have been dual-booting windows 10 and Linux Mint 20.2, both on separate drives. When upgrading to Windows 11 I decided to do a fresh install on a new (swapped 512 to 1GB) nvme drive, LM is on an ssd. The bios entry for Mint is not there now, I tried to boot from the Mint ssd but it looks like grub is not there, must have been on the old nvme? What are my options for recovering grub?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
Jo-con-Ël
Level 11
Level 11
Posts: 3509
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: Lost bios entry

Post by Jo-con-Ël »

tmarsh wrote: Fri Nov 26, 2021 3:05 pm I decided to do a fresh install on a new (swapped 512 to 1GB) nvme drive
Maybe it was a typo and you mean 512GB and 1TB. Did you remember when upgrading to W11 if you made a change in UEFI setting interface? Would you please confirm the way (UEFI/BIOS) you have installed W11?

Waiting for an English-native user to help you, meanwhile, you can try booting Linux MInt 20.2 Live if you still have that Installation media and post back following codes result. Open a terminal (Alt+Ctrl+T), copy and paste one line each time and press enter. Then, post back result using </>Code option in forum editor as indicated here.

Code: Select all

inxi -Fxxxz
sudo fdisk -l
sudo blkid
sudo efibootmgr -v

As an alternative, with a working internet connection, you can run Boot Repair (Menu>Administration>Boot Repair), choose BootInfo summary option ( do not run Recommended repair option now), confirm when asked about to share summary, copy and post back url when offered.
Last edited by Jo-con-Ël on Fri Nov 26, 2021 7:57 pm, edited 5 times in total.
Arrieritos semos y en el camino nos encontraremos.
User avatar
AndyMH
Level 21
Level 21
Posts: 13563
Joined: Fri Mar 04, 2016 5:23 pm
Location: Wiltshire

Re: Lost bios entry

Post by AndyMH »

What you did without knowing is install grub onto the win drive not your mint drive. There is a bug in the installer where it puts grub in the first EFI partition it finds not what you tell it.

So... to stop this happening again: You need to install grub to your mint drive, probably sda.

Boot your install stick and run the commands suggested by Jo-con-Ël and post the output:

Code: Select all

sudo fdisk -l
sudo blkid
sudo efibootmgr -v
fdisk tells us about your drives and partitions, blkid gives us the UUIDs for all your partitions and efibootmgr will confirm if the stick is booting in UEFI or legacy mode.

Then follow Jo-con-Ël's advice and run boot repair, there is a copy on your mint install stick. See if it offers to re-install grub and post the summary. If it doesn't offer to install grub on your mint sdd we can tell you how to do it manually.

I suspect you are booting in UEFI mode and you will need a EFI partition on your mint ssd before you can install grub. The output from the above will confirm this.
Thinkcentre M720Q - LM21.3 cinnamon, 4 x T430 - LM21.3 cinnamon, Homebrew desktop i5-8400+GTX1080 Cinnamon 19.0
tmarsh
Level 1
Level 1
Posts: 16
Joined: Tue Jul 06, 2021 10:39 am

Re: Lost bios entry

Post by tmarsh »

Thanks for the replies. Yes, 512GB! The bios was set to boot UEFI & legacy but to install windows I had to set it to UEFI only. UEFI doesn't give any other OSs at boot so after installing windows I reverted to UEFI & legacy but the only addition is my cd drive, the LM entry is not there. Using boot override and selecting the disk that LM is on doesn't work so I guess I need grub to install it there. I'll follow your suggestions and get back to you.
tmarsh
Level 1
Level 1
Posts: 16
Joined: Tue Jul 06, 2021 10:39 am

Re: Lost bios entry

Post by tmarsh »

I ran boot repair from a live session and this is the output:
boot-repair-4ppa130 [20211127_1506]

============================== Boot Info Summary ===============================
Boot Info Summary
=> No boot loader is installed in the MBR of /dev/nvme0n1.
=> No boot loader is installed in the MBR of /dev/sdb.
=> No boot loader is installed in the MBR of /dev/sdc.
=> No boot loader is installed in the MBR of /dev/sdd.

nvme0n1p1: _____________________________________________________________________

File system: ntfs
Boot sector type: Windows 2000/XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe

sdb1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 2000/XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdc1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 2000/XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

sdc2: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sdd1: __________________________________________________________________________

File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi
/efi/Microsoft/Boot/memtest.efi

sdd2: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 20.2
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub

sdd3: __________________________________________________________________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:

sdd4: __________________________________________________________________________

File system: swap
Boot sector type: -
Boot sector info:

sde: ___________________________________________________________________________

File system: iso9660
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: /mnt/BootInfo/FD/sde: /dev/sde already mounted or mount point busy.


================================ 2 OS detected =================================

OS#1: Linux Mint 20.2 Uma (20.2) on sdd2
OS#2: Windows 7 on nvme0n1p1

============================ Architecture/Host Info ============================

CPU architecture: 64-bit
Live-session OS is Linuxmint 64-bit (Linux Mint 20.2, uma, x86_64)


===================================== UEFI =====================================

BIOS is EFI-compatible, but it is not setup in EFI-mode for this live-session.
This session has been detected as 'live' because /proc/cmdline contains (boot=casper)
This session has been detected as 'live' because df -Th / contains overlay

6c3c0841d95db54525baed19280d20bd sdd1/Boot/bootx64.efi
6c3c0841d95db54525baed19280d20bd sdd1/Microsoft/Boot/bootmgfw.efi
c0298ecf493cea8ea468b939856c1486 sdd1/Microsoft/Boot/bootmgr.efi


============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

nvme0n1 : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes
sdb : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, no-os, 2048 sectors * 512 bytes
sdc : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, no-os, 2048 sectors * 512 bytes
sdd : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p1 : is-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdb1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdc1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sdc2 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios
sdd1 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
sdd2 : is-os, 64, apt-get, signed grub-pc grub-efi , grub2, grub-install, grubenv-ok, update-grub, farbios
sdd3 : no-os, 32, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, farbios

Partitions info (2/3): _________________________________________________________

nvme0n1p1 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot
sdb1 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdc1 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdc2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdd1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdd2 : isnotESP, fstab-has-bad-efi, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
sdd3 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot

Partitions info (3/3): _________________________________________________________

nvme0n1p1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, nvme0n1
sdb1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdb
sdc1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdc
sdc2 : maybesepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdc
sdd1 : not-sepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdd
sdd2 : not-sepboot, with-boot, fstab-without-boot, not-sep-usr, with--usr, fstab-without-usr, std-grub.d, sdd
sdd3 : maybesepboot, no-boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, std-grub.d, sdd

fdisk -l (filtered): ___________________________________________________________

Disk nvme0n1: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: F667FB80-6A7B-03AF-E0FE-99FD9EDAEB00
Start End Sectors Size Type
nvme0n1p1 2048 1953519615 1953517568 931.5G Microsoft basic data
Disk sdb: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: D4C8ED60-C52B-03AC-583B-32F54A31EB00
Start End Sectors Size Type
sdb1 2048 1953523711 1953521664 931.5G Microsoft basic data
Disk sdc: 111.81 GiB, 120034123776 bytes, 234441648 sectors
Disk identifier: 980E4DAF-FF50-4241-8DF2-94DEC1F448ED
Start End Sectors Size Type
sdc1 2048 126031871 126029824 60.1G Microsoft basic data
sdc2 126031872 234440703 108408832 51.7G Microsoft basic data
Disk sdd: 223.58 GiB, 240057409536 bytes, 468862128 sectors
Disk identifier: 314C7E00-E3AA-03AE-801F-538CEAB8EB00
Start End Sectors Size Type
sdd1 2048 976656 974609 475.9M EFI System
sdd2 976896 197265407 196288512 93.6G Linux filesystem
sdd3 197265408 453236735 255971328 122.1G Linux filesystem
sdd4 453236736 468860927 15624192 7.5G Microsoft basic data
Disk sde: 29.9 GiB, 32080200192 bytes, 62656641 sectors
Disk identifier: 0x4d49930e
Boot Start End Sectors Size Id Type
sde1 * 0 4186111 4186112 2G 0 Empty
sde2 616 8551 7936 3.9M ef EFI (FAT-12/16/32)
sde3 4186112 62656640 58470529 27.9G 83 Linux

parted -lm (filtered): _________________________________________________________

sdb:1000GB:scsi:512:4096:gpt:ATA ST1000DX001-1CM1:;
1:1049kB:1000GB:1000GB:ntfs:Basic data partition:msftdata;
sdc:120GB:scsi:512:512:gpt:ATA KINGSTON SV300S3:;
1:1049kB:64.5GB:64.5GB:ntfs:Basic data partition:msftdata;
2:64.5GB:120GB:55.5GB:ext4:Basic data partition:msftdata;
1:1049kB:500MB:499MB:fat32:EFI System Partition:boot, esp;
2:500MB:101GB:100GB:ext4::;
3:101GB:232GB:131GB:ext4::;
4:232GB:240GB:8000MB:linux-swap(v1):Basic data partition:msftdata;
sde:32.1GB:scsi:512:512:unknown:Samsung Flash Drive:;
nvme0n1:1000GB:nvme:512:512:gpt:WDC WDS100T2B0C:;
1:1049kB:1000GB:1000GB:ntfs:Basic data partition:msftdata;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sdb
└─sdb1 ntfs 01D66296381B0680 3754d850-6296-01d6-2868-aa1b4b31eb00 Hybrid 1TB Basic data partition
sdc
├─sdc1 ntfs 01D7735E96598C10 d9224de0-2ed6-01d7-f022-916c6b97eb00 120SSD Basic data partition
└─sdc2 ext4 f976ae96-5e73-d701-d062-ae965e73d701 000016b9-62d0-96ae-5e7b-d707722d0000 Basic data partition
sdd
├─sdd1 vfat FB99-0167 18a8b800-71d5-01d7-0058-548ceab8eb00 EFI System Partition
├─sdd2 ext4 b5a2611a-91bd-401d-aab2-5a960db9c47a 2948d07a-6e96-45c8-8742-6e476b9e7ddf
├─sdd3 ext4 ae5ddaac-bb97-4678-82d5-a433b60f8ef7 ad2dabc9-b02f-4fe1-8dcd-b8d41b8f2f42
└─sdd4 swap d25157b6-c0ae-4b05-8b5c-85aca15b9e3a 00005ff5-3710-1993-d5f9-d71beabf0000 Basic data partition
sde iso9660 2021-07-03-16-15-26-00 Linux Mint 20.2 MATE 64-bit
├─sde1 iso9660 2021-07-03-16-15-26-00 4d49930e-01 Linux Mint 20.2 MATE 64-bit
├─sde2 vfat C26E-047E 4d49930e-02
└─sde3 ext4 6c109e5b-99ae-4ffe-971b-8b231b89d0e3 4d49930e-03 writable
nvme0n1
└─nvme0n1p1 ntfs 01D7B53DFA59F170 00001007-50c0-fb3b-3dbd-d7010e200000 1TBNVME Basic data partition

df (filtered): _________________________________________________________________

Avail Use% Mounted on
disk/by-label/writable[/install-logs-2021-11-27.0/log] 25.9G 0% /var/log
nvme0n1p1 705.5G 24% /media/mint/1TBNVME
sdb1 789.3G 15% /mnt/boot-sav/sdb1
sdc1 45.2G 25% /mnt/boot-sav/sdc1
sdc2 33G 26% /mnt/boot-sav/sdc2
sdd1 445.6M 6% /mnt/boot-sav/sdd1
sdd2 75G 13% /mnt/boot-sav/sdd2
sdd3 108.2G 4% /mnt/boot-sav/sdd3
sde1 0 100% /cdrom

Mount options: __________________________________________________________________

disk/by-label/writable[/install-logs-2021-11-27.0/log] rw,relatime
nvme0n1p1 ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
sdb1 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sdc1 rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
sdc2 rw,relatime
sdd1 rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
sdd2 rw,relatime
sdd3 rw,relatime
sde1 ro,noatime,nojoliet,check=s,map=n,blocksize=2048

====================== sdd2/boot/grub/grub.cfg (filtered) ======================

Linux Mint 20.2 MATE b5a2611a-91bd-401d-aab2-5a960db9c47a
Linux Mint 20.2 MATE, with Linux 5.13.0-21-generic b5a2611a-91bd-401d-aab2-5a960db9c47a
Linux Mint 20.2 MATE, with Linux 5.11.0-38-generic b5a2611a-91bd-401d-aab2-5a960db9c47a
Windows Boot Manager (on nvme0n1p2) osprober-efi-1E55-F436
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###

========================== sdd2/etc/fstab (filtered) ===========================

# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdc2 during installation
UUID=b5a2611a-91bd-401d-aab2-5a960db9c47a / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p2 during installation
UUID=1E55-F436 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sdc3 during installation
UUID=ae5ddaac-bb97-4678-82d5-a433b60f8ef7 /home ext4 defaults 0 2
# swap was on /dev/sdc4 during installation
UUID=d25157b6-c0ae-4b05-8b5c-85aca15b9e3a none swap sw 0 0

======================= sdd2/etc/default/grub (filtered) =======================

GRUB_DEFAULT=2
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

==================== sdd2: Location of files loaded by Grub ====================

GiB - GB File Fragment(s)
79.192398071 = 85.032189952 boot/grub/grub.cfg 1
8.270503998 = 8.880386048 boot/vmlinuz 2
16.061199188 = 17.245581312 boot/vmlinuz-5.11.0-38-generic 1
8.270503998 = 8.880386048 boot/vmlinuz-5.13.0-21-generic 2
16.061199188 = 17.245581312 boot/vmlinuz.old 1
9.414699554 = 10.108956672 boot/initrd.img 5
6.813472748 = 7.315910656 boot/initrd.img-5.11.0-38-generic 2
9.414699554 = 10.108956672 boot/initrd.img-5.13.0-21-generic 5
6.813472748 = 7.315910656 boot/initrd.img.old 2

===================== sdd2: ls -l /etc/grub.d/ (filtered) ======================

-rwxr-xr-x 1 root root 18151 Aug 12 09:18 10_linux
-rwxr-xr-x 1 root root 42359 May 20 2021 10_linux_zfs
-rwxr-xr-x 1 root root 12894 May 20 2021 20_linux_xen
-rwxr-xr-x 1 root root 12059 May 20 2021 30_os-prober
-rwxr-xr-x 1 root root 1424 May 20 2021 30_uefi-firmware
-rwxr-xr-x 1 root root 214 May 20 2021 40_custom
-rwxr-xr-x 1 root root 216 May 20 2021 41_custom


======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown BootLoader on sde

00000000 45 52 08 00 00 00 90 90 00 00 00 00 00 00 00 00 |ER..............|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020 33 ed fa 8e d5 bc 00 7c fb fc 66 31 db 66 31 c9 |3......|..f1.f1.|
00000030 66 53 66 51 06 57 8e dd 8e c5 52 be 00 7c bf 00 |fSfQ.W....R..|..|
00000040 06 b9 00 01 f3 a5 ea 4b 06 00 00 52 b4 41 bb aa |.......K...R.A..|
00000050 55 31 c9 30 f6 f9 cd 13 72 16 81 fb 55 aa 75 10 |U1.0....r...U.u.|
00000060 83 e1 01 74 0b 66 c7 06 f1 06 b4 42 eb 15 eb 00 |...t.f.....B....|
00000070 5a 51 b4 08 cd 13 83 e1 3f 5b 51 0f b6 c6 40 50 |ZQ......?[Q...@P|
00000080 f7 e1 53 52 50 bb 00 7c b9 04 00 66 a1 b0 07 e8 |..SRP..|...f....|
00000090 44 00 0f 82 80 00 66 40 80 c7 02 e2 f2 66 81 3e |D.....f@.....f.>|
000000a0 40 7c fb c0 78 70 75 09 fa bc ec 7b ea 44 7c 00 |@|..xpu....{.D|.|
000000b0 00 e8 83 00 69 73 6f 6c 69 6e 75 78 2e 62 69 6e |....isolinux.bin|
000000c0 20 6d 69 73 73 69 6e 67 20 6f 72 20 63 6f 72 72 | missing or corr|
000000d0 75 70 74 2e 0d 0a 66 60 66 31 d2 66 03 06 f8 7b |upt...f`f1.f...{|
000000e0 66 13 16 fc 7b 66 52 66 50 06 53 6a 01 6a 10 89 |f...{fRfP.Sj.j..|
000000f0 e6 66 f7 36 e8 7b c0 e4 06 88 e1 88 c5 92 f6 36 |.f.6.{.........6|
00000100 ee 7b 88 c6 08 e1 41 b8 01 02 8a 16 f2 7b cd 13 |.{....A......{..|
00000110 8d 64 10 66 61 c3 e8 1e 00 4f 70 65 72 61 74 69 |.d.fa....Operati|
00000120 6e 67 20 73 79 73 74 65 6d 20 6c 6f 61 64 20 65 |ng system load e|
00000130 72 72 6f 72 2e 0d 0a 5e ac b4 0e 8a 3e 62 04 b3 |rror...^....>b..|
00000140 07 cd 10 3c 0a 75 f1 cd 18 f4 eb fd 00 00 00 00 |...<.u..........|
00000150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001b0 68 21 00 00 00 00 00 00 0e 93 49 4d 00 00 80 00 |h!........IM....|
000001c0 01 00 00 7f e0 fd 00 00 00 00 00 e0 3f 00 00 fe |............?...|
000001d0 ff ff ef fe ff ff 68 02 00 00 00 1f 00 00 00 92 |......h.........|
000001e0 4f 04 83 31 f6 3c 00 e0 3f 00 81 30 7c 03 00 00 |O..1.<..?..0|...|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200


=============================== StdErr Messages ================================

File descriptor 63 (pipe:[121235]) leaked on lvs invocation. Parent PID 23564: /bin/bash

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of
sdd2,
using the following options: sdd1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s win-legacy-basic-fix use-standard-efi-file

Blockers in case of suggested repair: __________________________________________

The current session is in BIOS-compatibility mode. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software from a live-CD (or live-USB) that is compatible with UEFI booting mode. For example, use a live-USB of Boot-Repair-Disk-64bit (www.sourceforge.net/p/boot-repair-cd), after making sure your BIOS is set up to boot USB in EFI mode.

Final advice in case of suggested repair: ______________________________________


Please do not forget to make your UEFI firmware boot on the Linux Mint 20.2 Uma (20.2) entry (sdd1/efi/****/shim****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.

If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\shim****.efi (**** will be updated in the final message)
The boot of your PC is in BIOS-compatibility/CSM/Legacy mode. You may want to retry after changing it to UEFI mode.
There is an option to repair but I wasn't sure if I should run it? I need my windows installation for working from home.
tmarsh
Level 1
Level 1
Posts: 16
Joined: Tue Jul 06, 2021 10:39 am

Re: Lost bios entry

Post by tmarsh »

Well guys, thanks for all your help. I noticed in the output that grub would be installed on the LM disk so I ran the repair and am now up and running again. Thanks again.
User avatar
Jo-con-Ël
Level 11
Level 11
Posts: 3509
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: Lost bios entry

Post by Jo-con-Ël »

There was a risk running that recommended repair if booting in such "BIOS compatible mode". Lucky you sort that problem w/o doing what was proposed below . :D
The current session is in BIOS-compatibility mode. Please disable BIOS-compatibility/CSM/Legacy mode in your UEFI firmware, and use this software
I`m still wondering about the problem. As there is no new EFI partition on nvme, and Linux loader was destroyed (there was no Ubuntu folder on that EFI partition)... It is not usual and looking at fstab ( # /boot/efi was on /dev/nvme0n1p2 during installation) there was an EFI partition on old nvme with Windows and Mint loader... :roll:

Any way, be advised and do not keep such compatible mode (i.e change boot mode to UEFI only, not UEFI +Legacy) to boot Windows installation media or Linux Live USB/DVD in UEFI mode when installing or repairing next time (hope you don't need). :wink:
Last edited by Jo-con-Ël on Sun Nov 28, 2021 11:48 am, edited 4 times in total.
Arrieritos semos y en el camino nos encontraremos.
tmarsh
Level 1
Level 1
Posts: 16
Joined: Tue Jul 06, 2021 10:39 am

Re: Lost bios entry

Post by tmarsh »

Thanks again. Yes, changed now to UEFI only. I'm not expert at all on these booting issues, I've only managed to dual-boot by following tutorials but I think it was booting direct from the nvme where windows is. So my original set up before changing the drive, I was booting from grub on the LM SSD which included the windows bootloader but I could go in to the bios and change boot order so that it booted from the nvme. Does that nake sense?
User avatar
AndyMH
Level 21
Level 21
Posts: 13563
Joined: Fri Mar 04, 2016 5:23 pm
Location: Wiltshire

Re: Lost bios entry

Post by AndyMH »

As said, not usual and not what I expected.

You have four drives in the system, but I assume sdb (old 1TB hybrid drive) and sdc (120GB HDD) are just data drives (they only have ntfs partitions on them). The two that matter are your nvme drive, nvme0n1, and your 240GB ssd on sdd. Assume win10 is on the nvme drive and mint is on sdd.

At the moment you only have one EFI partition and that is on sdd. So if that drive fails you will not be able to boot win. Ideally you would want an EFI partition on your nvme drive with the win bootloader in that. That way if your ssd dies, you can still boot win. How you make that change for win - no idea!
Thinkcentre M720Q - LM21.3 cinnamon, 4 x T430 - LM21.3 cinnamon, Homebrew desktop i5-8400+GTX1080 Cinnamon 19.0
User avatar
Jo-con-Ël
Level 11
Level 11
Posts: 3509
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: Lost bios entry

Post by Jo-con-Ël »

Please post back following codes result now booting LM installed.

Code: Select all

inxi -Fxxxz
sudo efibootmgr -v
Do not forget to run sudo update-grub to see and try Windows option in GRUB menu.
Arrieritos semos y en el camino nos encontraremos.
tmarsh
Level 1
Level 1
Posts: 16
Joined: Tue Jul 06, 2021 10:39 am

Re: Lost bios entry

Post by tmarsh »

Yes, correct, they are data drives.

inxi -Fxxxz
System: Kernel: 5.13.0-21-generic x86_64 bits: 64 compiler: N/A Console: tty 1 wm: kwin_x11
dm: LightDM 1.30.0 Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine: Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 3211 date: 08/10/2021
CPU: Topology: 6-Core model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen L1 cache: 384 KiB
L2 cache: 3072 KiB L3 cache: 32.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 91027
Speed: 2196 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2195 2: 2196 3: 2195
4: 2195 5: 2196 6: 2196 7: 2196 8: 2195 9: 2203 10: 2195 11: 2197 12: 2195
Graphics: Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 460.91.03 bus ID: 09:00.0
chip ID: 10de:128b
Display: server: X.Org 1.20.11 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
compositor: kwin_x11 resolution: 2560x1440~60Hz
OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 460.91.03 direct render: Yes
Audio: Device-1: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel v: kernel bus ID: 09:00.1
chip ID: 10de:0e0f
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 0b:00.4 chip ID: 1022:1487
Sound Server: ALSA v: k5.13.0-21-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169
v: kernel port: f000 bus ID: 04:00.0 chip ID: 10ec:8168
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: f000 bus ID: 05:00.0
chip ID: 8086:2723
IF: wlp5s0 state: down mac: <filter>
Drives: Local Storage: total: 3.97 TiB used: 17.52 GiB (0.4%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS100T2B0C size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 serial: <filter> rev: 211210WD scheme: GPT
ID-2: /dev/sda type: USB vendor: Western Digital model: WD20 EZRX-22D8PB0 size: 1.82 TiB
serial: <filter> rev: 0508 scheme: GPT
ID-3: /dev/sdb vendor: Seagate model: ST1000DX001-1CM162 size: 931.51 GiB speed: 6.0 Gb/s
rotation: 7200 rpm serial: <filter> rev: CC43 temp: 28 C scheme: GPT
ID-4: /dev/sdc vendor: Kingston model: SV300S37A120G size: 111.79 GiB speed: 6.0 Gb/s
serial: <filter> rev: BBF0 temp: 40 C scheme: GPT
ID-5: /dev/sdd vendor: Gigabyte model: GP-GSTFS31240GNTD size: 223.57 GiB speed: 6.0 Gb/s
serial: <filter> rev: 61.3 temp: 33 C scheme: GPT
Partition: ID-1: / size: 91.63 GiB used: 12.18 GiB (13.3%) fs: ext4 dev: /dev/sdd2
ID-2: /home size: 119.64 GiB used: 5.31 GiB (4.4%) fs: ext4 dev: /dev/sdd3
ID-3: swap-1 size: 7.45 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdd4
Sensors: System Temperatures: cpu: 36.9 C mobo: N/A gpu: nvidia temp: 43 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 40%
Info: Processes: 340 Uptime: 1m Memory: 31.26 GiB used: 1.47 GiB (4.7%) Init: systemd v: 245 runlevel: 5
Compilers: gcc: 9.3.0 alt: 9 Shell: bash (sudo) v: 5.0.17 running in: konsole inxi: 3.0.38
efibootmgr -v
root@thomas-mint:/home/thomas# sudo efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0000,0001,0002,0004
Boot0000* Windows Boot Manager HD(1,GPT,18a8b800-71d5-01d7-0058-548ceab8eb00,0x800,0xedf11)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0001* UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0002* UEFI:Removable Device BBS(130,,0x0)
Boot0003* ubuntu HD(1,GPT,18a8b800-71d5-01d7-0058-548ceab8eb00,0x800,0xedf11)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0004* UEFI:Network Device BBS(131,,0x0)
root@thomas-mint:/home/thomas#
User avatar
Jo-con-Ël
Level 11
Level 11
Posts: 3509
Joined: Sun Jun 20, 2021 12:41 pm
Location: donde habita el olvido

Re: Lost bios entry

Post by Jo-con-Ël »

tmarsh wrote: Sat Nov 27, 2021 12:44 pm I think it was booting direct from the nvme where windows is. So my original set up before changing the drive, I was booting from grub on the LM SSD which included the windows bootloader but I could go in to the bios and change boot order so that it booted from the nvme. Does that nake sense?
Yes. According to UEFI settings, if first option in boot order does not comply (nvme w/o an EFI dedicated partition before reparing) then try the second boot option, and so on.

Before repairing you ware booting Windows from EFI partiton on SSD (don't know how) and Linux Mint loader was on old nvme EFI partition alongside old Windows loader, so you couldn't find/boot it.

Now you are booting both Windows and Linux UEFI options from EFI partition on ssd and Ubuntu is your default choice. Take into account what Andy said in order to create a dedicate EFI partition on nvme.

See tutorials about how to create EFI partition from Windows out there if you don't want reinstalling Windows 11 or create img file with that ssd EFI partition (with Disks select ssd on the left and EFI partition on the right>clic on wheels icon downside>Create partition image)
Screenshot from 2021-11-28 12-16-41.png
Save somewhere (external media is desirable, in my case "compaq" is a partition on a secondary disk for backups) you can find it to restore if needed. :wink:
Screenshot from 2021-11-28 12-24-48.png
Last edited by Jo-con-Ël on Sun Nov 28, 2021 11:59 am, edited 4 times in total.
Arrieritos semos y en el camino nos encontraremos.
tmarsh
Level 1
Level 1
Posts: 16
Joined: Tue Jul 06, 2021 10:39 am

Re: Lost bios entry

Post by tmarsh »

Yes, probably better to do that, I'll have a look at some tutorials. Thanks again for all your help.
Locked

Return to “Installation & Boot”