MX Linux Forum

Posted: **Thu Apr 09, 2020 10:01 am**

Hi,

Many options at the grub list disappeared, only the operating systems and the test remain displayed. I don"t know how it happened, i did nothing ... Thanks for any commentary.

Posted: **Thu Apr 09, 2020 10:22 am**

on an installed system, that's all there is.

Posted: **Thu Apr 09, 2020 10:45 am**

Well there were more options before, for example, there was one that allow me to go into other systems and start from over there into the system, and others ..

Posted: **Thu Apr 09, 2020 10:51 am**

Normally the config file /boot/grub/grub.cfg does not vanish on its own, but if you need to regenerate it, "MX boot repair" is your friend.

Posted: **Thu Apr 09, 2020 11:24 am**

There are a few options ... which one do i have to ...?:

Posted: **Thu Apr 09, 2020 12:25 pm**

keos wrote: Thu Apr 09, 2020 11:24 am There are a few options ... which one do i have to ...?:

You might try the first two options. But we do not know what happend, so not sure whether it helps.

Posted: **Thu Apr 09, 2020 12:30 pm**

Which one? MBR root ESP

Posted: **Thu Apr 09, 2020 12:34 pm**

keos wrote: Thu Apr 09, 2020 12:30 pm Which one?

You should read first "How to ask for help?"
The main point would be to provide information about your system, so someone can help you.

Posted: **Thu Apr 09, 2020 12:42 pm**

If you are booting already likely ball you need is to rebuild the grub menu (update-grub)

Posted: **Thu Apr 09, 2020 12:45 pm**

:lipsrsealed:

Code: Select all

keos@keos-mx:~
$ inxi -F
System:
  Host: keos-mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 
  Desktop: Xfce 4.14.2 
  Distro: MX-19.1_x64 patito feo October 21  2019 
Machine:
  Type: Laptop System: Dell product: Inspiron 3583 v: N/A 
  serial: <root required> 
  Mobo: Dell model: 0WHCP7 v: A00 serial: <root required> 
  UEFI: Dell v: 1.5.1 date: 05/30/2019 
Battery:
  ID-1: BAT0 charge: 39.9 Wh condition: 39.9/42.0 Wh (95%) 
CPU:
  Topology: Quad Core model: Intel Core i5-8265U bits: 64 
  type: MT MCP L2 cache: 6144 KiB 
  Speed: 800 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 
  2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel 
  Display: x11 server: X.Org 1.20.4 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1366x768~60Hz 
  OpenGL: 
  renderer: Mesa DRI Intel HD Graphics (Whiskey Lake 3x8 GT2) 
  v: 4.5 Mesa 18.3.6 
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio 
  driver: snd_hda_intel 
  Sound Server: ALSA v: k4.19.0-6-amd64 
Network:
  Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit 
  Ethernet 
  driver: r8169 
  IF: eth0 state: up speed: 100 Mbps duplex: full 
  mac: d8:d0:90:46:9d:0f 
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
  Adapter 
  driver: ath10k_pci 
  IF: wlan0 state: down mac: 32:99:41:65:c6:fa 
  Device-3: Qualcomm Atheros type: USB driver: btusb 
Drives:
  Local Storage: total: 245.93 GiB used: 5.79 GiB (2.4%) 
  ID-1: /dev/nvme0n1 model: PC SN520 NVMe WDC 256GB 
  size: 238.47 GiB 
  ID-2: /dev/sda type: USB vendor: SanDisk model: Cruzer Glide 
  size: 7.45 GiB 
Partition:
  ID-1: / size: 29.11 GiB used: 5.76 GiB (19.8%) fs: ext4 
  dev: /dev/nvme0n1p4 
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 227 Uptime: 19m Memory: 7.67 GiB 
  used: 1.13 GiB (14.7%) Shell: bash inxi: 3.0.36 
keos@keos-mx:~
$

dolphin i did it many times.

Posted: **Thu Apr 09, 2020 1:04 pm**

Perhaps also show partition layout this way:

Code: Select all

lsblk --fs

and

Code: Select all

sudo parted --list

Posted: **Thu Apr 09, 2020 1:10 pm**

Code: Select all

keos@keos-mx:~
$ lsblk --fs
NAME FSTYPE LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda  vfat         B8E5-F2DC                                           
nvme0n1
│                                                                     
├─nvme0n1p1
│    vfat         DAB1-D49A                             460.2M     6% /boot/efi
├─nvme0n1p2
│    ext4   Manjaro
│                 8e5faa71-cff4-4e40-84a9-fe22a204dccb                
├─nvme0n1p3
│    ext4   Endeavouros
│                 dace6e36-8d39-4c7e-9c41-32191c8117a2                
├─nvme0n1p4
│    ext4   rootMX19
│                 af011a48-5b6e-41c5-8f95-82a4af45382b   21.9G    20% /
├─nvme0n1p5
│    ext4         b6888e4e-41c9-4925-9a71-1907d061b6a2                
├─nvme0n1p6
│    ext4         218bcaea-0fc0-41bd-8c12-40ab72265b57                
└─nvme0n1p7
     ext4         f6cc25e1-c248-4a32-b563-16c021502574                
keos@keos-mx:~
$ sudo parted --list
[sudo] password for keos: 
Model: SanDisk Cruzer Glide (scsi)
Disk /dev/sda: 8003MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End     Size    File system  Flags
 1      0.00B  8003MB  8003MB  fat32


Model: PC SN520 NVMe WDC 256GB (nvme)
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  513MB   512MB   fat32              boot, esp
 2      513MB   33.2GB  32.7GB  ext4
 3      33.2GB  66.2GB  33.0GB  ext4
 4      66.2GB  98.1GB  31.9GB  ext4
 5      98.1GB  130GB   31.9GB  ext4
 6      130GB   162GB   32.0GB  ext4
 7      162GB   194GB   32.2GB  ext4


keos@keos-mx:~
$

May be this can help too ...

viewtopic.php?f=104&t=56956#p566150

Posted: **Thu Apr 09, 2020 1:18 pm**

Can you pull out the USB flash drive "SanDisk Cruzer Glide",
and run

Code: Select all

sudo update-grub

and post the shown output.

Posted: **Thu Apr 09, 2020 1:20 pm**

Code: Select all

keos@keos-mx:~
$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-4.19.0-6-amd64
Found initrd image: /boot/initrd.img-4.19.0-6-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Found Manjaro Linux (19.0.2) on /dev/nvme0n1p2
Found EndeavourOS Linux (rolling) on /dev/nvme0n1p3
Adding boot menu entry for EFI firmware configuration
done
keos@keos-mx:~
$

Posted: **Thu Apr 09, 2020 1:30 pm**

keos wrote: Thu Apr 09, 2020 1:20 pm

Code: Select all

keos@keos-mx:~
$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-4.19.0-6-amd64
Found initrd image: /boot/initrd.img-4.19.0-6-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Found Manjaro Linux (19.0.2) on /dev/nvme0n1p2
Found EndeavourOS Linux (rolling) on /dev/nvme0n1p3
Adding boot menu entry for EFI firmware configuration
done
keos@keos-mx:~
$

OK. So you are saying you do not see the Manjaro and EndeavourOS menu entries, when booting, right?
Perhaps let's of a look into the whole file: /boot/grub/grub.cfg.

Posted: **Thu Apr 09, 2020 1:38 pm**

No, what i'm saying is that there were other options at the entries in MXLinux that vanished, they are not more in the list of options (means at MXLinux).

-- one of these options allow me before to get into others OS (from there i was able to do something inside Manjaro,now i need to do the same but ...)

Posted: **Thu Apr 09, 2020 1:48 pm**

keos wrote: Thu Apr 09, 2020 1:38 pm No, what i'm saying is that there were other options at the entries in MXLinux that vanished, they are not more in the list of options (means at MXLinux).

-- one of these options allow me before to get into others OS (from there i was able to do something inside Manjaro,now i need to do the same but ...)

What options? ... Are you talking about submenu? Perhaps someone else can understand this better?

Posted: **Thu Apr 09, 2020 1:57 pm**

Yes, a kind of submenu if you prefer -- i'm not able to copy the results of /boot/grub/grub.cfg I can't download the page while coping ...

Posted: **Thu Apr 09, 2020 2:08 pm**

keos wrote: Thu Apr 09, 2020 1:57 pm Yes, a kind of submenu if you prefer -- i'm not able to copy the results of /boot/grub/grub.cfg I can't download the page while coping ...

open Terminal and run

Code: Select all

fpad /boot/grub/grub.cfg

Copy'n'paste the content here [code]between code tags[/code]

Posted: **Thu Apr 09, 2020 2:21 pm**

Code: Select all

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  af011a48-5b6e-41c5-8f95-82a4af45382b
else
  search --no-floppy --fs-uuid --set=root af011a48-5b6e-41c5-8f95-82a4af45382b
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1024x768
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=es_US
  insmod gettext
fi
terminal_output gfxterm
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  af011a48-5b6e-41c5-8f95-82a4af45382b
else
  search --no-floppy --fs-uuid --set=root af011a48-5b6e-41c5-8f95-82a4af45382b
fi
insmod gfxmenu
insmod png
set theme=($root)/boot/grub/themes/linen/theme.txt
export theme
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=10
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=10
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'MX 19.1 patito feo' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-af011a48-5b6e-41c5-8f95-82a4af45382b' {
	load_video
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_gpt
	insmod ext2
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root  af011a48-5b6e-41c5-8f95-82a4af45382b
	else
	  search --no-floppy --fs-uuid --set=root af011a48-5b6e-41c5-8f95-82a4af45382b
	fi
	echo	'Loading Linux 4.19.0-6-amd64 ...'
	linux	/boot/vmlinuz-4.19.0-6-amd64 root=UUID=af011a48-5b6e-41c5-8f95-82a4af45382b ro  splash
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-4.19.0-6-amd64
}
submenu 'Advanced options for MX 19.1 patito feo' $menuentry_id_option 'gnulinux-advanced-af011a48-5b6e-41c5-8f95-82a4af45382b' {
	menuentry 'MX 19.1 patito feo, with Linux 4.19.0-6-amd64' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-6-amd64-advanced-af011a48-5b6e-41c5-8f95-82a4af45382b' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  af011a48-5b6e-41c5-8f95-82a4af45382b
		else
		  search --no-floppy --fs-uuid --set=root af011a48-5b6e-41c5-8f95-82a4af45382b
		fi
		echo	'Loading Linux 4.19.0-6-amd64 ...'
		linux	/boot/vmlinuz-4.19.0-6-amd64 root=UUID=af011a48-5b6e-41c5-8f95-82a4af45382b ro  splash
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.19.0-6-amd64
	}
	menuentry 'MX 19.1 patito feo, with Linux 4.19.0-6-amd64 (systemd)' --class mx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-6-amd64-init-systemd-af011a48-5b6e-41c5-8f95-82a4af45382b' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  af011a48-5b6e-41c5-8f95-82a4af45382b
		else
		  search --no-floppy --fs-uuid --set=root af011a48-5b6e-41c5-8f95-82a4af45382b
		fi
		echo	'Loading Linux 4.19.0-6-amd64 ...'
		linux	/boot/vmlinuz-4.19.0-6-amd64 root=UUID=af011a48-5b6e-41c5-8f95-82a4af45382b ro  splash init=/lib/systemd/systemd
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.19.0-6-amd64
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
if [ "${grub_platform}" == "efi" ]; then
   if [ "${grub_cpu}" == "x86_64" ]; then
:  
menuentry "Memory Test (64-bit UEFI)" {
	insmod part_gpt
	insmod ext2
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root  af011a48-5b6e-41c5-8f95-82a4af45382b
	else
	  search --no-floppy --fs-uuid --set=root af011a48-5b6e-41c5-8f95-82a4af45382b
	fi
	chainloader	/boot/uefi-mt/mtest-64.efi
}
  fi
fi
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Manjaro Linux (19.0.2) (on /dev/nvme0n1p2)' --class manjarolinux --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8e5faa71-cff4-4e40-84a9-fe22a204dccb' {
	insmod part_gpt
	insmod ext2
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root  8e5faa71-cff4-4e40-84a9-fe22a204dccb
	else
	  search --no-floppy --fs-uuid --set=root 8e5faa71-cff4-4e40-84a9-fe22a204dccb
	fi
	linux /boot/vmlinuz-5.6-x86_64 root=UUID=8e5faa71-cff4-4e40-84a9-fe22a204dccb rw quiet apparmor=1 security=apparmor udev.log_priority=3
	initrd /boot/initramfs-5.6-x86_64.img
}
submenu 'Advanced options for Manjaro Linux (19.0.2) (on /dev/nvme0n1p2)' $menuentry_id_option 'osprober-gnulinux-advanced-8e5faa71-cff4-4e40-84a9-fe22a204dccb' {
	menuentry 'Manjaro Linux (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.6-x86_64--8e5faa71-cff4-4e40-84a9-fe22a204dccb' {
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  8e5faa71-cff4-4e40-84a9-fe22a204dccb
		else
		  search --no-floppy --fs-uuid --set=root 8e5faa71-cff4-4e40-84a9-fe22a204dccb
		fi
		linux /boot/vmlinuz-5.6-x86_64 root=UUID=8e5faa71-cff4-4e40-84a9-fe22a204dccb rw quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd /boot/initramfs-5.6-x86_64.img
	}
	menuentry 'Manjaro Linux (Kernel 5.6.2-1-MANJARO x64) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.6-x86_64--8e5faa71-cff4-4e40-84a9-fe22a204dccb' {
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  8e5faa71-cff4-4e40-84a9-fe22a204dccb
		else
		  search --no-floppy --fs-uuid --set=root 8e5faa71-cff4-4e40-84a9-fe22a204dccb
		fi
		linux /boot/vmlinuz-5.6-x86_64 root=UUID=8e5faa71-cff4-4e40-84a9-fe22a204dccb rw quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd /boot/initramfs-5.6-x86_64.img
	}
	menuentry 'Manjaro Linux (Kernel 5.6.2-1-MANJARO x64 - fallback initramfs) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.6-x86_64--8e5faa71-cff4-4e40-84a9-fe22a204dccb' {
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  8e5faa71-cff4-4e40-84a9-fe22a204dccb
		else
		  search --no-floppy --fs-uuid --set=root 8e5faa71-cff4-4e40-84a9-fe22a204dccb
		fi
		linux /boot/vmlinuz-5.6-x86_64 root=UUID=8e5faa71-cff4-4e40-84a9-fe22a204dccb rw quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd /boot/initramfs-5.6-x86_64-fallback.img
	}
	menuentry 'Manjaro Linux (Kernel 5.5.15-1-MANJARO x64) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.5-x86_64--8e5faa71-cff4-4e40-84a9-fe22a204dccb' {
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  8e5faa71-cff4-4e40-84a9-fe22a204dccb
		else
		  search --no-floppy --fs-uuid --set=root 8e5faa71-cff4-4e40-84a9-fe22a204dccb
		fi
		linux /boot/vmlinuz-5.5-x86_64 root=UUID=8e5faa71-cff4-4e40-84a9-fe22a204dccb rw quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd /boot/initramfs-5.5-x86_64.img
	}
	menuentry 'Manjaro Linux (Kernel 5.5.15-1-MANJARO x64 - fallback initramfs) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.5-x86_64--8e5faa71-cff4-4e40-84a9-fe22a204dccb' {
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  8e5faa71-cff4-4e40-84a9-fe22a204dccb
		else
		  search --no-floppy --fs-uuid --set=root 8e5faa71-cff4-4e40-84a9-fe22a204dccb
		fi
		linux /boot/vmlinuz-5.5-x86_64 root=UUID=8e5faa71-cff4-4e40-84a9-fe22a204dccb rw quiet apparmor=1 security=apparmor udev.log_priority=3
		initrd /boot/initramfs-5.5-x86_64-fallback.img
	}
}

menuentry 'EndeavourOS Linux (rolling) (on /dev/nvme0n1p3)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-dace6e36-8d39-4c7e-9c41-32191c8117a2' {
	insmod part_gpt
	insmod ext2
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root  dace6e36-8d39-4c7e-9c41-32191c8117a2
	else
	  search --no-floppy --fs-uuid --set=root dace6e36-8d39-4c7e-9c41-32191c8117a2
	fi
	linux /boot/vmlinuz-linux root=UUID=dace6e36-8d39-4c7e-9c41-32191c8117a2 rw quiet loglevel=3
	initrd /boot/initramfs-linux.img
}
submenu 'Advanced options for EndeavourOS Linux (rolling) (on /dev/nvme0n1p3)' $menuentry_id_option 'osprober-gnulinux-advanced-dace6e36-8d39-4c7e-9c41-32191c8117a2' {
	menuentry 'EndeavourOS Linux, with Linux linux (on /dev/nvme0n1p3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux--dace6e36-8d39-4c7e-9c41-32191c8117a2' {
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  dace6e36-8d39-4c7e-9c41-32191c8117a2
		else
		  search --no-floppy --fs-uuid --set=root dace6e36-8d39-4c7e-9c41-32191c8117a2
		fi
		linux /boot/vmlinuz-linux root=UUID=dace6e36-8d39-4c7e-9c41-32191c8117a2 rw quiet loglevel=3
		initrd /boot/initramfs-linux.img
	}
	menuentry 'EndeavourOS Linux, with Linux linux (fallback initramfs) (on /dev/nvme0n1p3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-linux--dace6e36-8d39-4c7e-9c41-32191c8117a2' {
		insmod part_gpt
		insmod ext2
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root  dace6e36-8d39-4c7e-9c41-32191c8117a2
		else
		  search --no-floppy --fs-uuid --set=root dace6e36-8d39-4c7e-9c41-32191c8117a2
		fi
		linux /boot/vmlinuz-linux root=UUID=dace6e36-8d39-4c7e-9c41-32191c8117a2 rw quiet loglevel=3
		initrd /boot/initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
	fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

One of these options or submenu are good for the grub reparation.

Posted: **Thu Apr 09, 2020 2:44 pm**

Where is grub installed? Is it via Mint bootloader?
I mean which OS is controlling grub?

Posted: **Thu Apr 09, 2020 2:51 pm**

If you:

Ran MX Boot Repair
Chose "Reinstall GRUB bootloader on ESP, MBR or PBR (root) and Clicked Apply,
Chose Install on: MBR (default) and Clicked Apply

then you would have GRUB from MX-19 installed on the MBR (Master Boot Record) of the disk,
BUT, this is a UEFI system, so where you boot from is going depend the EFI boot parameters.

I suspect a different GRUB is being called, not MX-19's?

What's shown by:

Code: Select all

efibootmgr

You probably want to try MX Boot Repair again, but:

Choose "Reinstall GRUB bootloader on ESP, MBR or PBR (root) and Click Apply,
Choose Install on: ESP and Click Apply

I see I was

-ed by anticaptialista (again

)

Posted: **Thu Apr 09, 2020 3:16 pm**

Code: Select all

root@keos-mx:~# LANG=C efibootmgr
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0005,0002,0001,0004
Boot0000 Windows Boot Manager
Boot0001* manjaro
Boot0002 LinuxMint
Boot0003* MX19
Boot0004* endeavouros
Boot0005 debian
root@keos-mx:~#

Debian and Linuxmint are not installed anymore(?)

Are you asking for to run boot repair and Install on: ESP and Click Apply?

Posted: **Thu Apr 09, 2020 4:09 pm**

OK, this I got from your posted grub.cfg:

keos_grub.png

So what are you missing?

Posted: **Thu Apr 09, 2020 4:18 pm**

When you click on advanced options and it open, there are many more options as grub repair, etc

-- if you have an iso live you will see these options over there too, i don't know how to take a capture as you did ...

Posted: **Thu Apr 09, 2020 4:22 pm**

keos wrote: Thu Apr 09, 2020 4:18 pm When you click in advances option and it open there are many more options as grub repair, etc

Hmm, "grub repair" on Grub menu, not sure what those shall be?
I see those under advanced option:
Manjaro:

keos_majaro_submenu.png

endeavorOS

endeavorOS_submenu.png

Not enough?

Posted: **Thu Apr 09, 2020 4:25 pm**

I'm talking about MXLinux ...if you have an iso live you will see these options over there too ...

Posted: **Thu Apr 09, 2020 4:26 pm**

keos wrote: Thu Apr 09, 2020 4:25 pm I'm talking about MXLinux ...

On installed MX systems, the only "advanced" boot menu items are for choosing either sysVinit or systemd.

the live system has lots of options, include grub rescue type options, but the installed systems do not, and they aren't supposed to.

Posted: **Thu Apr 09, 2020 4:29 pm**

keos wrote: Thu Apr 09, 2020 4:25 pm I'm talking about MXLinux ...if you have an iso live you will see these options over there too ...

I see only the two entries for mx linux for sysvinit and systemd:

keos_mxlinux_submenu.png

What other entries you have in mind? Other kernels?
Or did you added manually some entries using Grub Customizer?

Posted: **Thu Apr 09, 2020 4:35 pm**

That is what you said before ... what can i say? ... these options were here before in my installed system and now they are not here anymore you are the experts i'm nobody, but i'm telling you what happened, it vanished from my system, if you don't believe what i said, case closed.

Thank you any way

Posted: **Thu Apr 09, 2020 4:36 pm**

keos wrote: Thu Apr 09, 2020 4:25 pm ...if you have an iso live you will see these options over there too ...

Did you added those manually from the live ISO?
Those are on the live ISO:

live-efi-grub.png

live-efi-grub-rescue.png

Posted: **Thu Apr 09, 2020 4:38 pm**

keos wrote: Thu Apr 09, 2020 3:16 pm

Code: Select all

root@keos-mx:~# LANG=C efibootmgr
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0005,0002,0001,0004
Boot0000 Windows Boot Manager
Boot0001* manjaro
Boot0002 LinuxMint
Boot0003* MX19
Boot0004* endeavouros
Boot0005 debian
root@keos-mx:~#

Debian and Linuxmint are not installed anymore(?)

Thanks for the output, nicely done.

I now realize, I screwed up, and need to beg for more info.

I should have asked for:

Code: Select all

LANG=C efibootmgr --verbose

so we can verify that "Boot0003* MX19" goes where we expect.

keos wrote: Thu Apr 09, 2020 3:16 pm Are you asking for to run boot repair and Install on: ESP and Click Apply?

Not yet.

They're EVERYWHERE! 3rd time today!

Posted: **Thu Apr 09, 2020 4:46 pm**

keos wrote: Thu Apr 09, 2020 4:35 pm That is what you said before ... what can i say? ... these options were here before in my installed system and now they are not here anymore you are the experts i'm nobody, but i'm telling you what happened, it vanished from my system, if you don't believe what i said, case closed.

Don't worry, I believe you. Can you remember what have changed before you missed those entries?
Any major updates or did removed something else?
Can we see what's on those folder
do run

Code: Select all

ls -dl /etc/grub*/* /boot/grub/*

Posted: **Fri Apr 10, 2020 8:41 am**

One day i saw them, it was at the beginning of having installed the system; i had problems with Manjaro then i went into one of this entries to fix Manjaro ... i had grub-customiser installed, so i don't remember more about it. Those entrances were hidden, they were not visible, and I will never return to look until yesterday that i had another problem with Manjaro ...

Either way if they're not supposed to be there then it doesn't matter much.

Code: Select all

keos@keos-mx:~
$ ls -dl /etc/grub*/* /boot/grub/*
drwxr-xr-x 2 root root    4096 ene 29 19:22 /boot/grub/fonts
-r--r--r-- 1 root root   12730 abr  9 16:12 /boot/grub/grub.cfg
-rw-r--r-- 1 root root    1024 abr  9 16:11 /boot/grub/grubenv
drwxr-xr-x 2 root root   12288 mar 21 20:14 /boot/grub/i386-pc
drwxr-xr-x 8 root root    4096 oct 20 10:48 /boot/grub/themes
-rw-r--r-- 1 root root 2396122 oct 20 11:03 /boot/grub/unicode.pf2
drwxr-xr-x 2 root root   12288 mar 22 09:18 /boot/grub/x86_64-efi
-rwxr-xr-x 1 root root   10046 sep 18  2019 /etc/grub.d/00_header
-rwxr-xr-x 1 root root    6258 ago 30  2019 /etc/grub.d/05_debian_theme
-rwxr-xr-x 1 root root   13658 abr  1 07:55 /etc/grub.d/10_linux
-rwxr-xr-x 1 root root   12894 sep 18  2019 /etc/grub.d/20_linux_xen
-rwxr-xr-x 1 root root    1468 feb 11 11:44 /etc/grub.d/20_memtest86+
-rwxr-xr-x 1 root root   12073 sep 18  2019 /etc/grub.d/30_os-prober
-rwxr-xr-x 1 root root    1418 sep 18  2019 /etc/grub.d/30_uefi-firmware
-rwxr-xr-x 1 root root     214 sep 18  2019 /etc/grub.d/40_custom
-rwxr-xr-x 1 root root     216 sep 18  2019 /etc/grub.d/41_custom
-rw-r--r-- 1 root root     483 sep 18  2019 /etc/grub.d/README
keos@keos-mx:~
$

Posted: **Fri Apr 10, 2020 8:52 am**

Code: Select all

keos@keos-mx:~
$ sudo -i
[sudo] password for keos: 
root@keos-mx:~# LANG=C efibootmgr --verbose
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0005,0002,0001,0004
Boot0000  Windows Boot Manager	HD(1,GPT,055b2cfe-1ad4-4dcf-8e57-ba97840c0794,0x800,0x145000)/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.}....................
Boot0001* manjaro	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\manjaro\grubx64.efi)
Boot0002  LinuxMint	PciRoot(0x0)/Pci(0x1d,0x4)/Pci(0x0,0x0)/NVMe(0x1,00-1B-44-4A-44-11-E8-8F)/HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)
Boot0003* MX19	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\MX19\grubx64.efi)
Boot0004* endeavouros	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\endeavouros\grubx64.efi)
Boot0005  debian	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\debian\shimx64.efi)
root@keos-mx:~#

Posted: **Fri Apr 10, 2020 12:09 pm**

keos wrote: Fri Apr 10, 2020 8:52 am

Code: Select all

keos@keos-mx:~
$ sudo -i
[sudo] password for keos: 
root@keos-mx:~# LANG=C efibootmgr --verbose
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0005,0002,0001,0004
:
Boot0001* manjaro	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)
                         /File(\EFI\manjaro\grubx64.efi)
                         
Boot0002  LinuxMint	PciRoot(0x0)/Pci(0x1d,0x4)/Pci(0x0,0x0)
                         /NVMe(0x1,00-1B-44-4A-44-11-E8-8F)
                          /HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)
                          
Boot0003* MX19          HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)
                         /File(\EFI\MX19\grubx64.efi)
                         
Boot0004* endeavouros	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)
                         /File(\EFI\endeavouros\grubx64.efi)
                         
Boot0005  debian	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)
                         /File(\EFI\debian\shimx64.efi)

Looks reasonable, I think, (not sure of the LinuxMint entry):
Active:

#3 MX19 --> ESP partition, file: /EFI/MX19/grubx64.efi
#1 manjaro --> ESP partition, file: /EFI/manjaro/grubx64.efi
#4 endeavouros --> ESP partition, file: /EFI/endeavouros/grubx64.efi

Inactive:

#5 debian --> ESP partition, file: /EFI/debian/shimx64.efi
#1 LinuxMint --> ESP partition, ??? VBR(Volume Boot Record)/PBR(Partition Boot Record)?

So, you should be getting to the MX-19 Grub menu, and I think you are.

What's present on the MX-19 Grub menu(s) should be modifiable by adjusting the grub config on MX-19 and updating grub from MX-19.

Posted: **Fri Apr 10, 2020 3:31 pm**

Code: Select all

root@keos-mx:~# update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-4.19.0-6-amd64
Found initrd image: /boot/initrd.img-4.19.0-6-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Found Manjaro Linux (19.0.2) on /dev/nvme0n1p2
Found EndeavourOS Linux (rolling) on /dev/nvme0n1p3
Adding boot menu entry for EFI firmware configuration
done
root@keos-mx:~#

Somebody else told me in another foro that because this is an UEFI wherever... something like a mark (my own words) will remain in the BIOS, then i checked at that moment and Debian and MInt were there even when i uninstalled both of them.

It is different at Gparted:

Captura de pantalla-5.png

And at the Bios the order is like this:

*MX19
Debian
LinuxMint
*Manjaro
*Endeavouros

Posted: **Fri Apr 10, 2020 5:00 pm**

keos wrote: Fri Apr 10, 2020 3:31 pm Somebody else told me in another foro that because this is an UEFI wherever... something like a mark (my own words) will remain in the BIOS, then i checked at that moment and Debian and MInt were there even when i uninstalled both of them.

EFI-loader need to be clear manually
**>> from both the UEFI/BIOS NVRAM entries, which you see when running "efibootmgr -v"

Code: Select all

efibootmgr -v   --bootnum XXXX --delete-bootnum

E.g.:

Code: Select all

LANG=C efibootmgr --verbose
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0005,0002,0001,0004
Boot0000  Windows Boot Manager	HD(1,GPT,055b2cfe-1ad4-4dcf-8e57-ba97840c0794,0x800,0x145000)/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.}....................
Boot0001* manjaro	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\manjaro\grubx64.efi)
Boot0002  LinuxMint	PciRoot(0x0)/Pci(0x1d,0x4)/Pci(0x0,0x0)/NVMe(0x1,00-1B-44-4A-44-11-E8-8F)/HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)
Boot0005  debian	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\debian\shimx64.efi)

To remove LinuxMint: (Boot0002 )

Code: Select all

efibootmgr  -v  --bootnum 0002 --delete-bootnum

To remove Debian: ( Boot0005 debian)

Code: Select all

efibootmgr  -v  --bootnum 0005 --delete-bootnum

and

**>> and also the EFI-directory on the ESP holding the EFI-loader:
navigate on
/boot/efi/EFI
and remove the corresponding directory entries:
for LinuxMint:
/boot/efi/EFI/ubuntu
or
/boot/efi/EFI/linuxmint (?)
and for Debian:
/boot/efi/EFI/debian

Posted: **Fri Apr 10, 2020 6:26 pm**

I did it and everything looks good at the Bios but how do i know where exactly are my OS installed, means partitions, Gparted is saying something different that the above command... thanks

Code: Select all

root@keos-mx:~# LANG=C efibootmgr --verbose
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0001,0004
Boot0000  Windows Boot Manager	HD(1,GPT,055b2cfe-1ad4-4dcf-8e57-ba97840c0794,0x800,0x145000)/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.}....................
Boot0001* manjaro	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\manjaro\grubx64.efi)
Boot0003* MX19	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\MX19\grubx64.efi)
Boot0004* endeavouros	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\endeavouros\grubx64.efi)
root@keos-mx:~#

Captura de pantalla-6.png

Posted: **Fri Apr 10, 2020 6:45 pm**

keos wrote: Fri Apr 10, 2020 6:26 pm I did it and everything looks good at the Bios but how do i know where exactly are my OS installed, means partitions, Gparted is saying something different that the above command... thanks

Very good question!
You don't see it. The EFI-(grub)-loader get loaded by the UEFI-firmware.
The "efibootmgr -v" does only show the efi-loader on the ESP (EFI System Partition) which has been registred into the firmware NVRAM.
The magic is within the EFI-(grub-)loader, e.g. within /boot/efi/EFI/MX19/grubx64.efi.
Within this efi-"binary" /boot/efi/EFI/MX19/grubx64.efi the location of the boot/grub-partition is burned into.

[Klare Sache und damit hopp!] "Tadellöser & Wolff" - Walter Kempowski.

Posted: **Fri Apr 10, 2020 7:31 pm**

No, I do not see it clearly ... it looks like there are two images for only one reality ... No, i'm far away for to be a magician.

What command can i use to know exactly where are every OS/partitions?
Can i trust Gparted?

Posted: **Fri Apr 10, 2020 7:45 pm**

keos wrote: Fri Apr 10, 2020 7:31 pm What command can i use to know exactly where are every OS/partitions?
Can i trust Gparted?

No. You can only boot into the selected EFI-loader, and
get a piece of paper an write down where you are booted into.
Alternatively and .. if you're inclined .. you can md5sum-compare the /boot/efi/EFI/<name>/grubx64.efi loader
with the one within the booted system at /boot/grub/x86_64-efi/core.efi.
Example:
Your /boot/efi/EFi/MX19/grubx64.efi
is identical to (when booted into MX19)
/boot/grub/x86_64-efi/core.efi
Just run and "binary"-compare using md5sum:
md5sum /boot/grub/x86_64-efi/core.efi
and
md5sum /efi/EFi/MX19/grubx64.efi
and you'll see you have the identical efi-bootloader.
So by this you can find out which efi-bootloader belongs to what system you boot into.

Posted: **Fri Apr 10, 2020 8:05 pm**

I do not explain myself well, what I need to know is where are the operating systems / partitions for the case when i need to uninstall / install? Can I use/trust Gparted for that purpose?. Thanks.

Posted: **Fri Apr 10, 2020 8:34 pm**

keos wrote: Fri Apr 10, 2020 8:05 pm I do not explain myself well, what I need to know is where are the operating systems / partitions for the case when i need to uninstall / install? Can I use/trust Gparted for that purpose?. Thanks.

It's always a good idea to label the partition with the name of the OS when installing (or afterwards using Gparted). So by this way you can trust Gparted and your own partion labels before wiping or re-using the partitions, after uninstalling.
... or take a piece of paper and write down where you have installed what

Posted: **Fri Apr 10, 2020 9:40 pm**

Well, it might have TOO much detail, but there-in lie the nuggets you seek.

So, do:

Code: Select all

sudo apt update

Code: Select all

 sudo apt install boot-info-script

And install bootinfoscript

Sadly, there is no Man page in MX-19!

But, MX-18.3 = Yes!

But, there is --help :

Code: Select all

$ bootinfoscript --help

Usage Boot Info Script:
-----------------------

  Run the script as sudoer:

    sudo /usr/sbin/bootinfoscript <outputfile>

  or if your operating system does not use sudo:

    su -
    /usr/sbin/bootinfoscript <outputfile>

  When running the script, without specifying an output file, all the output
  is written to the file "RESULTS.txt" in the same folder as the script.

  But when run from /bin, /sbin, /usr/bin, or another system folder, the file
  "RESULTS.txt" is written to the home directory of the user.

  When the file "RESULTS.txt" already exists, the results will be written to
  "RESULTS1.txt". If "RESULTS1.txt" exists, the results will be written to
  "RESULTS2.txt", ...

  To get version number, release date, last git commit and git retrieval date
  of this script, use (no root rights needed):

    /usr/sbin/bootinfoscript -v
    /usr/sbin/bootinfoscript -V
    /usr/sbin/bootinfoscript --version

  To get this help text, use (no root rights needed):

    /usr/sbin/bootinfoscript -h
    /usr/sbin/bootinfoscript -help
    /usr/sbin/bootinfoscript --help

  To automatically gzip a copy of the output file, use (root rights needed):

    /usr/sbin/bootinfoscript -g <outputfile>
    /usr/sbin/bootinfoscript --gzip <outputfile>

  To write the output to stdout instead of a file, use (root rights needed):

    /usr/sbin/bootinfoscript --stdout

  The last development version of Boot Info Script can be downloaded, with:
    (no root rights needed)

    /usr/sbin/bootinfoscript --update <filename>

  If no filename is specified, the file will be saved in the home dir as
  "bootinfoscript_YYYY-MM-DD_hh:mm:ss".

Spent some reading the help.

Here's a small sample of output from my T500 while running MX-19 x64 (sda7,sda8):

Code: Select all

$ inxi -SMxxxza
System:
  Host: mx-3 Kernel: 4.19.0-8-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-8-amd64 
  root=UUID=f9bca753-XXXX-XXXX-XXXX-XXXXXXXXXXXX ro quiet nosplash 
  consoleblank=600 
  Console: tty 11 dm: LightDM 1.26.0 
  Distro: MX-19.1_x64 patito feo October 21  2019 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Laptop System: LENOVO product: 2082BKU v: ThinkPad T500 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 2082BKU serial: <filter> BIOS: LENOVO 
  v: 7VET81WW (3.11 ) date: 11/19/2009

Run bootinfoscript to gather info...

Code: Select all

sudo bootinfoscript  boot-info-2020-04-10-T500-MX19x64.txt

Quick overview of partitions, containing 3 MX intallations, 2 swap partitions:

Code: Select all

"blkid" output: ________________________________________________________________
Device           UUID                                   TYPE       LABEL
/dev/sda1        e2e2adf1-XXXX-XXXX-XXXX-XXXXXXXXXXXX   swap       Swap
/dev/sda10       a3e58873-XXXX-XXXX-XXXX-XXXXXXXXXXXX   swap       Swap-MX19
/dev/sda5        68b84fb4-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Root-MX18.3
/dev/sda6        004bc773-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Home-MX18.3
/dev/sda7        f9bca753-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Root-MX19
/dev/sda8        caf65465-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Home-MX19
/dev/sda9        20439be9-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       MX-19_386

Some bits have been obsured, and some have been collapsed to ":"

Code: Select all

                  Boot Info Script 0.77      [10 June 2018]


============================= Boot Info Summary: ===============================

 => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    for (,msdos5)/boot/grub. It also embeds following components:

    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos biosdisk
    ---------------------------------------------------------------------------

sda1: __________________________________________________________________________

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

sda2: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info:

sda5: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v2.00) is installed in the boot sector of sda5
                       and looks at sector 21435136 of the same hard drive
                       for core.img. core.img is at this location and looks
                       for (,msdos5)/boot/grub. It also embeds following
                       components:

                       modules
                       -------------------------------------------------------
                       fshelp ext2 part_msdos biosdisk
                       -------------------------------------------------------
    Operating System:  Debian GNU/Linux 9 (stretch)
    Boot files:        /boot/grub/grub.cfg /etc/fstab
                       /boot/grub/i386-pc/core.img

sda6: __________________________________________________________________________

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

sda7: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of
                       sda7 and looks at sector 181288984 of the same hard
                       drive for core.img, but core.img can not be found at
                       this location.
    Operating System:  Debian GNU/Linux 10 (buster)
    Boot files:        /boot/grub/grub.cfg /etc/fstab
                       /boot/grub/i386-pc/core.img

sda8: __________________________________________________________________________

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

sda9: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v2.00) is installed in the boot sector of sda9
                       and looks at sector 327579640 of the same hard drive
                       for core.img. core.img is at this location and looks
                       for (,msdos9)/boot/grub. It also embeds following
                       components:

                       modules
                       -------------------------------------------------------
                       fshelp ext2 part_msdos biosdisk
                       -------------------------------------------------------
    Operating System:  Debian GNU/Linux 10 (buster)
    Boot files:        /boot/grub/grub.cfg /etc/fstab
                       /boot/grub/i386-pc/core.img

sda10: _________________________________________________________________________

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

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

Drive: sda _____________________________________________________________________
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disk model: ST9320423AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1               2,048     8,390,655     8,388,608  82 Linux swap / Solaris
/dev/sda2           8,390,656   625,141,759   616,751,104   5 Extended
/dev/sda5           8,392,704    58,724,351    50,331,648  83 Linux
/dev/sda6          58,726,400   159,389,695   100,663,296  83 Linux
/dev/sda7         159,391,744   209,723,391    50,331,648  83 Linux
/dev/sda8         209,725,440   310,388,735   100,663,296  83 Linux
/dev/sda9         310,390,784   377,499,647    67,108,864  83 Linux
/dev/sda10        377,501,696   385,890,303     8,388,608  82 Linux swap / Solaris


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/sda1        e2e2adf1-XXXX-XXXX-XXXX-XXXXXXXXXXXX   swap       Swap
/dev/sda10       a3e58873-XXXX-XXXX-XXXX-XXXXXXXXXXXX   swap       Swap-MX19
/dev/sda5        68b84fb4-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Root-MX18.3
/dev/sda6        004bc773-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Home-MX18.3
/dev/sda7        f9bca753-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Root-MX19
/dev/sda8        caf65465-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Home-MX19
/dev/sda9        20439be9-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       MX-19_386

========================= "ls -l /dev/disk/by-id" output: ======================
	:
================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/sda7        /                        ext4       (rw,noatime)
/dev/sda8        /home                    ext4       (rw,noatime)


=========================== sda5/boot/grub/grub.cfg: ===========================
	:
=============================== sda5/etc/fstab: ================================

--------------------------------------------------------------------------------
# Pluggable devices are handled by uDev, they are not in fstab
UUID=68b84fb4-XXXX-XXXX-XXXX-XXXXXXXXXXXX / ext4 defaults,noatime 1 1
UUID=004bc773-XXXX-XXXX-XXXX-XXXXXXXXXXXX /home ext4 defaults,noatime 1 2
UUID=e2e2adf1-XXXX-XXXX-XXXX-XXXXXXXXXXXX swap swap defaults 0 0
--------------------------------------------------------------------------------

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

           GiB - GB             File                                 Fragment(s)

  10.221126556 = 10.974851072   boot/grub/grub.cfg                             2
  10.221092224 = 10.974814208   boot/grub/i386-pc/core.img                     1
  10.147022247 = 10.895282176   boot/vmlinuz-4.19.0-5-amd64                    1
   8.413097382 = 9.033494528    boot/vmlinuz-4.19.0-6-amd64                    1
   4.936534882 = 5.300563968    boot/vmlinuz-4.19.0-8-amd64                    1
   4.936534882 = 5.300563968    vmlinuz                                        1
   8.413097382 = 9.033494528    vmlinuz.old                                    1
   9.016540527 = 9.681436672    boot/initrd.img-4.19.0-5-amd64                 3
   8.649356842 = 9.287176192    boot/initrd.img-4.19.0-5-amd64.old-dkms        3
   9.315483093 = 10.002423808   boot/initrd.img-4.19.0-6-amd64                 1
   8.758747101 = 9.404633088    boot/initrd.img-4.19.0-6-amd64.old-dkms        1
   5.579185486 = 5.990604800    boot/initrd.img-4.19.0-8-amd64                 5
   5.579185486 = 5.990604800    initrd.img                                     5
   9.315483093 = 10.002423808   initrd.img.old                                 1

=========================== sda7/boot/grub/grub.cfg: ===========================
	:
=============================== sda7/etc/fstab: ================================
	:
=================== sda7: Location of files loaded by Grub: ====================
	:
=========================== sda9/boot/grub/grub.cfg: ===========================
	:
=============================== sda9/etc/fstab: ================================
	:
=================== sda9: Location of files loaded by Grub: ====================
	:
EOF

*WHEW*

On UEFI systems there quite a bit of detail about the ESP partition,
but I haven't anything that shows the EFI "NVRAM" contents.

If you roll up your sleeves, dig into the output,
and add the output of sudo efibootmgr -v,
you'll have most everything you're could be looking for.

Posted: **Sat Apr 11, 2020 6:10 am**

Code: Select all

                  Boot Info Script 0.77      [10 June 2018]


============================= Boot Info Summary: ===============================


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

no valid partition table found
"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/nvme0n1                                                       
/dev/nvme0n1p1   DAB1-D49A                              vfat       
/dev/nvme0n1p2   8e5faa71-cff4-4e40-84a9-fe22a204dccb   ext4       Manjaro
/dev/nvme0n1p3   dace6e36-8d39-4c7e-9c41-32191c8117a2   ext4       Endeavouros
/dev/nvme0n1p4   af011a48-5b6e-41c5-8f95-82a4af45382b   ext4       rootMX19
/dev/nvme0n1p5   b6888e4e-41c9-4925-9a71-1907d061b6a2   ext4       
/dev/nvme0n1p6   218bcaea-0fc0-41bd-8c12-40ab72265b57   ext4       
/dev/nvme0n1p7   f6cc25e1-c248-4a32-b563-16c021502574   ext4       

========================= "ls -l /dev/disk/by-id" output: ======================

total 0
lrwxrwxrwx 1 root root 13 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f-part6 -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-eui.1919394465030001001b444a4411e88f-part7 -> ../../nvme0n1p7
lrwxrwxrwx 1 root root 13 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503-part6 -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 15 abr 11 04:34 nvme-PC_SN520_NVMe_WDC_256GB_191939446503-part7 -> ../../nvme0n1p7

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/nvme0n1p1   /boot/efi                vfat       (rw,noatime,fmask=0113,dmask=0002,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/nvme0n1p4   /                        ext4       (rw,relatime)

Code: Select all

keos@keos-mx:~
$ sudo efibootmgr -v
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0001,0004
Boot0000  Windows Boot Manager	HD(1,GPT,055b2cfe-1ad4-4dcf-8e57-ba97840c0794,0x800,0x145000)/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.}....................
Boot0001* manjaro	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\manjaro\grubx64.efi)
Boot0003* MX19	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\MX19\grubx64.efi)
Boot0004* endeavouros	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\endeavouros\grubx64.efi)
keos@keos-mx:~
$

All of this still very obscure to me, i think that is not going anywhere ...

-- at this time, and after installed all these systems ... i will go for to trusth Gparted.

Thank you very much for your help.

Posted: **Sat Apr 11, 2020 3:50 pm**

m_frank wrote: Fri Apr 10, 2020 9:40 pm
Well, it might have TOO much detail, ...
(the suggestion to use boot-info-script)
:

fehlix wrote: Fri Apr 10, 2020 8:34 pm :
It's always a good idea to label the partition with the name of the OS when installing (or afterwards using Gparted).
So by this way you can trust Gparted and your own partion labels before wiping or re-using the partitions, after uninstalling.
... or take a piece of paper and write down where you have installed what

keos wrote: Sat Apr 11, 2020 6:10 am

Code: Select all

                  Boot Info Script 0.77      [10 June 2018]
============================= Boot Info Summary: ===============================
	:
============================ Drive/Partition Info: =============================
no valid partition table found
"blkid" output: ________________________________________________________________
Device           UUID                                   TYPE       LABEL
/dev/nvme0n1                                                       
/dev/nvme0n1p1   DAB1-D49A                              vfat       
/dev/nvme0n1p2   8e5faa71-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Manjaro
/dev/nvme0n1p3   dace6e36-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       Endeavouros
/dev/nvme0n1p4   af011a48-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       rootMX19
/dev/nvme0n1p5   b6888e4e-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       
/dev/nvme0n1p6   218bcaea-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       
/dev/nvme0n1p7   f6cc25e1-XXXX-XXXX-XXXX-XXXXXXXXXXXX   ext4       

========================= "ls -l /dev/disk/by-id" output: ======================
	:
================================ Mount points: =================================

Device           Mount_Point              Type       Options
/dev/nvme0n1p1   /boot/efi                vfat       (rw,noatime,fmask=0113,dmask=0002,allow_utime=0020,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/nvme0n1p4   /                        ext4       (rw,relatime)

Code: Select all

keos@keos-mx:~
$ sudo efibootmgr -v
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0001,0004
Boot0000  Windows Boot Manager	HD(1,GPT,055b2cfe-1ad4-4dcf-8e57-ba97840c0794,0x800,0x145000)/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.}....................
Boot0001* manjaro	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\manjaro\grubx64.efi)
Boot0003* MX19	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\MX19\grubx64.efi)
Boot0004* endeavouros	HD(1,GPT,7ee8288d-1cbb-40a9-abb8-9fac305bb0a4,0x800,0xf4000)/File(\EFI\endeavouros\grubx64.efi)
keos@keos-mx:~
$

All of this still very obscure to me, i think that is not going anywhere ...

-- at this time, and after installed all these systems ... i will go for to trust Gparted.

Thank you very much for your help.

I appreciate that the bootinfoscript output can be overwhelming, like trying to drink from a fire-hose, and wasn't suggesting that it replace the nice graphical overview that gparted provides. It's probably not for every day use.

On the other hand, if you are trying to get:

What's installed in the MBR and where it points,
What's installed in a partition's VBR/PBR and where it points,
The OS installed in a partition,
The grub.cfg in a partition and its contents,
The /etc/fstab of the OS in a partition,
The fs (File System) of a partition,
The location of files loaded by Grub,
The boot files in a partition

Because you're trying to figure out which grub.cfg controls the boot menu or why the new kernel isn't loaded on boot, etc.

You'll find bootinfoscript useful.

Now, if only it also:

showed the the EFI NVRAM boot order and boot entries (UEFI systems)
had a higher level overview? A tool to distill the long detailed output?

Maybe boot-info-script should be installed by default?

MX Linux Forum

Many submenu-options at the grub list vanished

Many submenu-options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished

Re: Many submenu-options at the grub list vanished