[SOLVED]Has the Mint boot menu changed?

[wasd33]

About a month ago, I noticed my computer would not display a menu that appeared between a BIOS splash and the Mint login screen which would list my Mint and Windows 10 installations. I am unsure if this is GRUB specifically because it was not the menu where I could write commands, but one (that wasn't BIOS) simply listing Mint and Windows as boot options, along with a few others I don't exactly remember.

Ultimately, I have two questions:
1. As shown in the GPARTED table below, am I OK with /boot/efi being fat32 and root / being ext4 file format?
2. Was not having the GRUB menu I described an expected change in Mint?

I read through the thread here (viewtopic.php?p=2305793#p2305793) where I learned a user had two different file formats for their drives.

blkid output:

Code: Select all

/dev/sdc2: UUID="5E09-638D" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="445ac799-4f7a-46c3-864b-68b9fbd4e9de"
/dev/sdc1: LABEL="Recovery" BLOCK_SIZE="512" UUID="26DA08A9DA087779" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="b88505fc-a7c4-4875-ae8b-588997e6d2b8"
/dev/sdc4: LABEL="Turbo" BLOCK_SIZE="512" UUID="38320AD2320A94D2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6074faf6-7268-45ed-942d-272c7f3169d0"
/dev/sda2: UUID="82F7-91B9" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="5f7003fe-9fe0-4c61-9c9f-1298d8e6d588"
/dev/sda3: UUID="20f98859-6e4e-40b9-acd9-038f955cf719" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="643aa3b3-d2aa-43c5-95d7-b52485eeb0de"

inxi output:

Code: Select all

System:
  Kernel: 5.15.0-67-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.8 tk: GTK 3.24.33 wm: muffin vt: 7
    dm: GDM3 42.0, LightDM 1.30.0 Distro: Linux Mint 21.1 Vera
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Micro-Star product: MS-7C02 v: 1.0
    serial: <superuser required>
  Mobo: Micro-Star model: B450 TOMAHAWK (MS-7C02) v: 1.0
    serial: <superuser required> UEFI: American Megatrends v: 1.E0
    date: 06/09/2020
CPU:
  Info: 6-core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP smt: enabled
    arch: Zen+ rev: 2 cache: L1: 576 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 2215 high: 3905 min/max: 1550/3400 boost: enabled
    cores: 1: 1377 2: 1377 3: 1377 4: 3898 5: 1558 6: 3905 7: 1377 8: 1378
    9: 1380 10: 3507 11: 1559 12: 3896 bogomips: 81589
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: eVga.com.
    driver: nvidia v: 525.85.05 pcie: speed: 2.5 GT/s lanes: 16 ports:
    active: none off: DP-3,HDMI-A-1 empty: DP-1,DP-2,Unknown-1
    bus-ID: 26:00.0 chip-ID: 10de:1e87 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 95 s-size: 1198x389mm (47.2x15.3")
    s-diag: 1260mm (49.6")
  Monitor-1: DP-4 pos: primary,top-right res: 2560x1440 dpi: 123
    size: 527x296mm (20.7x11.7") diag: 604mm (23.8")
  Monitor-2: HDMI-0 pos: bottom-l res: 1920x1080 hz: 60 dpi: 96
    size: 509x286mm (20.0x11.3") diag: 584mm (23")
  OpenGL: renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
    v: 4.6.0 NVIDIA 525.85.05 direct render: Yes
Audio:
  Device-1: NVIDIA TU104 HD Audio vendor: eVga.com. driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 26:00.1 chip-ID: 10de:10f8
    class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 28:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Corsair HS60 Surround Adapter type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-9:2 chip-ID: 1b1c:0a3b
    class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k5.15.0-67-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-10:3 chip-ID: 8087:0a2a class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 3.18 TiB used: 751.95 GiB (23.1%)
  ID-1: /dev/sda vendor: Seagate model: ST2000LX001-1RG174 size: 1.82 TiB
    speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: SDM1 scheme: GPT
  ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-22MFCA0
    size: 931.51 GiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: 1A01 scheme: GPT
  ID-3: /dev/sdc vendor: Western Digital model: WDS500G2B0B-00YS70
    size: 465.76 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 00WD
    scheme: GPT
Partition:
  ID-1: / size: 1.79 TiB used: 751.94 GiB (41.0%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat
    dev: /dev/sda2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: nvidia temp: 39 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
  Packages: 2842 apt: 2814 flatpak: 28
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/megasync.list
    1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/xUbuntu_22.04/ ./
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://mirrors.ocf.berkeley.edu/linuxmint-packages vera main upstream import backport
    2: deb http://mirror.math.ucdavis.edu/ubuntu jammy main restricted universe multiverse
    3: deb http://mirror.math.ucdavis.edu/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://mirror.math.ucdavis.edu/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
    1: deb https://deb.opera.com/opera-stable/ stable non-free
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
    1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main
  Active apt repos in: /etc/apt/sources.list.d/spotify.list
    1: deb http://repository.spotify.com stable non-free
Info:
  Processes: 358 Uptime: 59m wakeups: 15 Memory: 15.57 GiB
  used: 3.3 GiB (21.2%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11/12 Shell: Bash v: 5.1.16 running-in: tilda inxi: 3.3.13

GPARTED:

Some related options within BIOS:
SATA Mode: AHCI
Boot mode: UEFI only (the firmware also allows selecting Legacy, which I have not chosen)
I have noticed, however, with Boot mode not including Legacy a few boot priority options disappear from the menu.

The drives I can see in BIOS are:
SATA1: ST2000 (where I have Mint installed)
SATA2: WD10, which serves as storage
WDC WD S500 (my Windows 10 installation).

Thank you for the support and being an awesome community!

[AndyMH]

About a month ago, I noticed my computer would not display a menu that appeared between a BIOS splash and the Mint login screen which would list my Mint and Windows 10 installations.

Would this be co-incident with when you installed LM21? The reason I ask is that you have a bios_grub partition which is only needed for legacy boot, yet you say you are booting UEFI. If the output from efibootmgr says EFI variables are not supported you are booting legacy. This would explain why you don't see a grub menu (win installed UEFI, mint installed legacy).

Your #1 is normal.

[ronsmeyer]

Make a backup before changing.

In /etc/default/grub -- (You need root access to do this) "sudo xed /etc/default/grub"

Change GRUB_TIMEOUT_STYLE to "menu".
Change GRUB_TIMEOUT to 10, or however many seconds you want.
Run "sudo update-grub".
Reboot.

Code: Select all

GRUB_TIMEOUT_STYLE="menu"
GRUB_TIMEOUT=10

https://easylinuxtipsproject.blogspot.com/p/grub.html

[wasd33]

Would this be co-incident with when you installed LM21?

Yes, it was around that time.

The reason I ask is that you have a bios_grub partition which is only needed for legacy boot, yet you say you are booting UEFI. If the output from efibootmgr says EFI variables are not supported you are booting legacy. This would explain why you don't see a grub menu (win installed UEFI, mint installed legacy).

Here's my output when I enter efibootmgr:

Code: Select all

]BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,000E,0000,0001,000D
Boot0000* Windows Boot Manager
Boot0001  Hard Drive
Boot0003* ubuntu
Boot000D  CD/DVD Drive
Boot000E* ubuntu

Your #1 is normal.

By this you're referring to my question about the GPARTED table?

[wasd33]

Make a backup before changing.

I will 100% make a backup. I use the Timeshift default of not storing the entire /home directory (documents, pictures, etc. - I may have worded that incorrectly), however is there a separate tool you recommend? It's an unrelated question, but I appreciate it!

In /etc/default/grub -- (You need root access to do this) "sudo xed /etc/default/grub"

Change GRUB_TIMEOUT_STYLE to "menu".
Change GRUB_TIMEOUT to 10, or however many seconds you want.
Run "sudo update-grub".
Reboot.

Code: Select all

GRUB_TIMEOUT_STYLE="menu"
GRUB_TIMEOUT=10

https://easylinuxtipsproject.blogspot.com/p/grub.html

If the issue stemmed from the LM21 update as the earlier post suggested, how would editing the conf file relate? I appreciate your recommendation, I'm just curious how proposed solutions differ.

[ronsmeyer]

If the issue stemmed from the LM21 update as the earlier post suggested, how would editing the conf file relate? I appreciate your recommendation, I'm just curious how proposed solutions differ.

Did you look at it? What does your "/etc/default/grub" say?

Sometimes, system updates reset parameters to defaults. This is one thing to check, and easy to fix. When I removed my Windows partition, Grub did this.

If the file says "GRUB_TIMEOUT_STYLE="hidden", the Grub menu is not being displayed because the parameter file says not to display it.
"GRUB_TIMEOUT=10" is how long to display the menu. The time can be any arbitrary number of seconds you think is sufficient for your needs. I use 10.

If the file already says "menu" with a number of seconds to display, then that isn't the problem, and we need to look elsewhere.
But if the parameters are telling Grub to hide the menu, messing around with the partitions will never make the menu display, and you will waste a lot of time.

If Grub isn't displaying its menu, this is a very common cause.

As far as backup, just make a copy:

Code: Select all

cd /etc/default
sudo cp grub grub.backup

[AZgl1800]

I put this in my Notebook a while back, to PREVENT updates from changing my Grub Menu defaults.
----

https://easylinuxtipsproject.blogspot.c ... html#ID6.1 .

locked it 2/5/2023

Locking Grub to its current version
6.1. Especially on a multiboot computer with more than one Linux, it can help to prevent problems when you lock all Grub-related packages to their current version (freeze them). In each installed Linux distro. Thus effectively preventing updates for Grub from messing up your boot order.

For that, do the following in each installed Linux distribution:

a. Launch a terminal window.
(You can launch a terminal window like this: *Click*)

b. Copy/paste the following command line into the terminal:

Code: Select all

sudo apt-mark hold "grub*"

Press Enter. Type your password when prompted. In Ubuntu this remains entirely invisible, not even dots will show when you type it, that's normal. In Mint this has changed: you'll see asterisks when you type. Press Enter again.

Want to undo? Undoing is easy; for that, you can use this command:

Code: Select all

sudo apt-mark unhold "grub*"

[Jo-con-Ël]

It looks like you installed some updates (kernel or grub itselt) when booting on Legacy BIOS mode (at least one time) or removed Windows disk, or any other reason so UEFI option/s on Windows disk was/were not detected when updating grub.

Now you are booting on UEFI mode I would run sudo update-grub and see results on nex boot.

Be sure on computer Setup boot mode is set on UEFI only always as you say it is now and boot first option on boot order priority is ubuntu on sda (Seagate ST2000LX001) not on sdc (WDS500G2B0B-00YS70). Use UEFI BBS hard drive prority if needed to be sure it is.

Then if you get no GRUB menu at all, you can edit /etc/default/grub and do as indicated by ronsmeyer.

Post back following codes result in any case.

Code: Select all

sudo parted -l
sudo efibootmgr -v

(Edited) There was no "r "on update-grub codes (I wrote that before lunch). Sorry.

[AndyMH]

Jo-con-Ël has beaten me to it. You are booting UEFI mode, so should be the same as win, it could be as simple as sudo update-grub, it should find win and next time you boot you will get a grub menu. If it finds win, but no grub menu, then it means editing the grub config file.

[wasd33]

If the issue stemmed from the LM21 update as the earlier post suggested, how would editing the conf file relate? I appreciate your recommendation, I'm just curious how proposed solutions differ.

Did you look at it? What does your "/etc/default/grub" say?

Sometimes, system updates reset parameters to defaults. This is one thing to check, and easy to fix. When I removed my Windows partition, Grub did this.

If the file says "GRUB_TIMEOUT_STYLE="hidden", the Grub menu is not being displayed because the parameter file says not to display it.
"GRUB_TIMEOUT=10" is how long to display the menu. The time can be any arbitrary number of seconds you think is sufficient for your needs. I use 10.

If the file already says "menu" with a number of seconds to display, then that isn't the problem, and we need to look elsewhere.
But if the parameters are telling Grub to hide the menu, messing around with the partitions will never make the menu display, and you will waste a lot of time.

If Grub isn't displaying its menu, this is a very common cause.

Indeed, here's the output from checking grub:

Code: Select all

cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

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

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

As far as backup, just make a copy:

Code: Select all

cd /etc/default
sudo cp grub grub.backup

To ensure my understanding, this would just save my current grub settings as a file for me to refer back to if needed?

[wasd33]

I put this in my Notebook a while back, to PREVENT updates from changing my Grub Menu defaults.
----

https://easylinuxtipsproject.blogspot.c ... html#ID6.1 .

locked it 2/5/2023

Locking Grub to its current version
6.1. Especially on a multiboot computer with more than one Linux, it can help to prevent problems when you lock all Grub-related packages to their current version (freeze them). In each installed Linux distro. Thus effectively preventing updates for Grub from messing up your boot order.

For that, do the following in each installed Linux distribution:

a. Launch a terminal window.
(You can launch a terminal window like this: *Click*)

b. Copy/paste the following command line into the terminal:

Code: Select all

sudo apt-mark hold "grub*"

Press Enter. Type your password when prompted. In Ubuntu this remains entirely invisible, not even dots will show when you type it, that's normal. In Mint this has changed: you'll see asterisks when you type. Press Enter again.

Want to undo? Undoing is easy; for that, you can use this command:

Code: Select all

sudo apt-mark unhold "grub*"

Thank you for the tip, I will certainly do this once I've gotten boot to where I want it

[wasd33]

It looks like you installed some updates (kernel or grub itselt) when booting on Legacy BIOS mode (at least one time) or removed Windows disk, or any other reason so UEFI option/s on Windows disk was/were not detected when updating grub.

Now you are booting on UEFI mode I would run sudo update-grub and see results on nex boot.

Be sure on computer Setup boot mode is set on UEFI only always as you say it is now and boot first option on boot order priority is ubuntu on sda (Seagate ST2000LX001) not on sdc (WDS500G2B0B-00YS70). Use UEFI BBS hard drive prority if needed to be sure it is.
Captura de pantalla_2023-03-23_10-33-51.png
Then if you get no GRUB menu at all, you can edit /etc/default/grub and do as indicated by ronsmeyer.

Post back following codes result in any case.

Code: Select all

sudo parted -l
sudo efibootmgr -v

(Edited) There was no "r "on update-grub codes (I wrote that before lunch). Sorry.

Thank you for the suggestions, I will update grub, then make a backup and incorporate any necessary changes as ronsmeyer has indicated, then post back with results from the codes you provided.

[ronsmeyer]

To ensure my understanding, this would just save my current grub settings as a file for me to refer back to if needed?

Correct

Code: Select all

# To backup do: 
cd /etc/default/
sudo cp grub grub.backup 
# 'cp' is copy. This results in two identical files, 'grub' and 'grub.backup'

# If you want to restore the backup, do
cd /etc/default
sudo mv grub grub.with-my-changes
sudo mv grub.backup grub 
sudo update-grub

# 'mv' is move, but in the same directory effectively it is rename  - move the file to a new name. 
# The extension can be anything you want. I just picked some examples. 
# 'grub' will be renamed to 'grub.with-my-changes'
# 'grub.backup' will renamed to 'grub'
# do 'sudo update-grub' and reboot

[wasd33]

While I would still like input on my boot setup, I am considering the immediate issue of not having the menu solved.

Quick edit: a major thank you to everyone who replied with their helpful insight!

Steps taken:
1. Ran sudo update-grub

2. Shutdown and started computer, did not enter BIOS menu, and was taken to the GRUB menu I had expected to see. It did not countdown and I had to select which partition to enter.

3. In this boot, I made a backup of my current GRUB configuration, grub.backup, and as a text file (I'm paranoid and I was a little more comfortable with a regular text editor)

4. Entered the grub configuration file as ronsmeyer suggested using sudo xed /etc/default/grub

5. Changed the GRUB_TIMEOUT setting to my preferred time. GRUB_TIMEOUT_STYLE still listed as hidden, which I did not change.

6. Considering etc/default/grub showed the menu while still set to hidden, I shutdown and booted again to check. GRUB_TIMEOUT_STYLE is still listed as hidden, and displayed the 12 second timer I had indicated. Is there a risk in changing this to menu as ronsmeyer recommended?

Current output from sudo parted -l:

Code: Select all

Model: ATA ST2000LX001-1RG1 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  2097kB  1049kB                                     bios_grub
 2      2097kB  540MB   538MB   fat32        EFI System Partition  boot, esp
 3      540MB   2000GB  2000GB  ext4


Model: ATA WDC WD10EZEX-22M (scsi)
Disk /dev/sdb: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      17.4kB  16.8MB  16.8MB               Microsoft reserved partition  msftres
 2      16.8MB  1000GB  1000GB               Storage pool


Model: ATA WDC WDS500G2B0B (scsi)
Disk /dev/sdc: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  524MB  523MB   ntfs         Basic data partition          hidden, diag
 2      524MB   628MB  104MB   fat32        EFI system partition          boot, esp
 3      628MB   645MB  16.8MB               Microsoft reserved partition  msftres
 4      645MB   500GB  499GB   ntfs         Basic data partition          msftdata

Current output from sudo efibootmgr -v:

Code: Select all

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,000E,0000,0001,000D
Boot0000* Windows Boot Manager	HD(2,GPT,445ac799-4f7a-46c3-864b-68b9fbd4e9de,0xfa000,0x31800)/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.}...d................
Boot0001  Hard Drive	BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........S.T.2.0.0.0.L.X.0.0.1.-.1.R.G.1.7.4...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .D.Z.7.Z.8.8.B.Y........BO..NO..........W.D.C. .W.D.1.0.E.Z.E.X.-.2.2.M.F.C.A.0...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L. . . . .W. .-.D.C.W.6.C.4.Y.U.S.E.7.F.7........BO..NO..........W.D.C. . .W.D.S.5.0.0.G.2.B.0.B.-.0.0.Y.S.7.0...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.9.1.5.0.6.6.0.8.3.4.4.6. . . . . . . . ........BO
Boot0003* ubuntu	HD(2,GPT,5f7003fe-9fe0-4c61-9c9f-1298d8e6d588,0x1000,0x100800)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot000D  CD/DVD Drive	BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)..GO..NO..........A.S.U.S. . . . .D.R.W.-.2.4.B.3.S.T. . . .j...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.3.J.0.D.L.C.0.0.7.1.5.1. . . . . . . . ........BO
Boot000E* ubuntu	HD(2,GPT,445ac799-4f7a-46c3-864b-68b9fbd4e9de,0xfa000,0x31800)/File(\EFI\UBUNTU\SHIMX64.EFI)..BO

Additionally, I'll look into implementing AZgl1800's recommendation to lock grub.

[Jo-con-Ël]

To avoid problems/confusions on the future, IMO you can consider disabling BIOS Legacy support (so that Hard drive boot option to boot MInt on BIOS Legacy mode will disapear from computer's boot manager) and remove LM UEFI loader from Windows disk that you don´t need (now).

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,000E,0000,0001,000D
Boot0000* Windows Boot Manager HD(2,GPT,445ac799-4f7a-46c3-864b-68b9fbd4e9de,0xfa000,0x31800)/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.}...d................
Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..
Boot0003* ubuntu HD(2,GPT,5f7003fe-9fe0-4c61-9c9f-1298d8e6d588,0x1000,0x100800)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot000D CD/DVD Drive BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)..GO..NO..........A.S.U.S. . .
Boot000E* ubuntu HD(2,GPT,445ac799-4f7a-46c3-864b-68b9fbd4e9de,0xfa000,0x31800)/File(\EFI\UBUNTU\SHIMX64.EFI)..BO

In your case BIOS legacy support (CSM) as per your user manual would be enabled on Advanced options>Windows OS Configuration>BIOS UEFI/CSM mode.

To remove Mint UEFI loader from Windows disk, mount that sdc2 partition and remove /EFI/ubuntu folder, From terminal copy and paste

Code: Select all

sudo mount /dev/sdc2 /mnt
sudo rm -R /mnt/EFI/ubuntu
sudo umount /mnt

Then run sudo update-grub again to see, on next boot, there is only one ubuntu option on computer's boot menu (F11) .

[wasd33]

To avoid problems/confusions on the future, IMO you can consider disabling BIOS Legacy support (so that Hard drive boot option to boot MInt on BIOS Legacy mode will disapear from computer's boot manager) and remove LM UEFI loader from Windows disk that you don´t need (now).

BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,000E,0000,0001,000D
Boot0000* Windows Boot Manager HD(2,GPT,445ac799-4f7a-46c3-864b-68b9fbd4e9de,0xfa000,0x31800)/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.}...d................
Boot0001 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..
Boot0003* ubuntu HD(2,GPT,5f7003fe-9fe0-4c61-9c9f-1298d8e6d588,0x1000,0x100800)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot000D CD/DVD Drive BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)..GO..NO..........A.S.U.S. . .
Boot000E* ubuntu HD(2,GPT,445ac799-4f7a-46c3-864b-68b9fbd4e9de,0xfa000,0x31800)/File(\EFI\UBUNTU\SHIMX64.EFI)..BO

In your case BIOS legacy support (CSM) as per your user manual would be enabled on Advanced options>Windows OS Configuration>BIOS UEFI/CSM mode.

CSM.resized.png

To remove Mint UEFI loader from Windows disk, mount that sdc2 partition and remove /EFI/ubuntu folder, From terminal copy and paste

Code: Select all

sudo mount /dev/sdc2 /mnt
sudo rm -R /mnt/EFI/ubuntu
sudo umount /mnt

Then run sudo update-grub again to see, on next boot, there is only one ubuntu option on computer's boot menu (F11) .

I knew something about my boot table read weird, but I couldn't quite articulate it. I'll definitely look into cleaning it up as you suggested, thanks!