Multi Boot with GRUB2

[BiB]

Hi Guys, me again,

I like to try out new Linux OSes, with grub2, so it is a multi boot situation.
os-prober often does not get it right - so how should I configure grub in that case, plz?

BTW, I am very happy I found this sitr showing how to manually write boot entries.
https://www.gnu.org/software/grub/manua ... onfig.html

However, you can write manual entries in /etc/grub.d in the 40 , 30 , ... Files. So maybe no need to manually write the config file??

Now how is your recommended way to multi boot, let's say WIN 10, MINT, and another linuxOS?
I found "boot-repair", but what's your best option?
Thanks!

Thanks so far..
Boris

[deepakdeshp]

Best option is just install the Linux os and it will be automatically added to the grub. Grub will be controlled by the last Linux os installed. You should install Windows first and then the Linux os.

[BiB]

Best option is just install the Linux os and it will be automatically added to the grub. Grub will be controlled by the last Linux os installed. You should install Windows first and then the Linux os.

Yes. Thank you.
However, that's what I always do - also install first win and then Linux. But at least one Linux OS and often the windows OS is not correctly detected by the install process. (as I wrote, I figure is prober does this.).

So how do I set up multi boot correctly?

[Jymm]

I am not sure of Mint, but Mint is based on Ubuntu and the os-prober has been disabled by default, meaning a new installation will not find and existing os and will overwrite the boot loader for it. It is a security issue with uefi.

OS Prober is Disabled in Ubuntu 22.04, Here’s a Workaround
https://www.omgubuntu.co.uk/2021/12/gru ... istros-fix

Maybe someone else has some more information on this issue?

[BiB]

So I am trying out 3 or 4 Linux os plus win 10 ("ameliorated " BTW ).

Maybe it's kind of crazy or complicated but it should definitely be possible, not right?

[Jo-con-Ël]

Most the times you don't need to do nothing special. As it is also said, last installed Linux system will try to direct booting from its own grub and running sudo update-grub it will included other systems detected if installed on the same mode. That is the most important, in order GRUB menu includes other systems installed all systems must be installed in the same UEFI/BIOS legacy mode.

On the other hand, trying to boot other system not installed on the same UEFI mode (so no detected) from custom entries will fail.

As per the other thread now Fedora GRUB is directing boot process and it shows Alpine and Mint entries.

Maybe something failed on installing those system as there is no UEFI boot option on efibootmgr result for those systems (Mint UEFI boot option would be shown as Ubuntu on that list). Also It looks like efibootmgr does not match very well with your firnware.

In any case, Fedora's GRUB would detect other Linux systems even if the were installed w/o loader but on UEFI mode.

Windows is another case...Sometimes is not detected/included on GRUB even if it was intalled on UEFI mode. You said you have installed Windows 10 first but Windows partition is not at the first beguinning of the disk (use te be the second or third one and it is the fith), EFI partition is FAT 16 (use to be FAT 32) and usually Windows creates another Windows reserved partitions on installing.

Also you said you have just update BIOS on the other thread but last BIOS version (for Windows 10 64) is not the installed one but 02.59 Rev.A dated on 2022.

Try booting Linux Mint option on GRUB menu and post back following codes result (copy and paste one line each time on terminal and press Enter) using </> Code option on Mint forum editor as indicated on the other thread.

Code: Select all

sudo fdisk -l
sudo blkid
mokutil --sb-state
sudo efibootmgr -v
ls /boot/efi/EFI/

I am not sure of Mint, but Mint is based on Ubuntu and the os-prober has been disabled by default,....

Mint current 20.X editions are based on Ubuntu 20.04 not Ubuntu 22.04 so os-prober is not disabled by default. Any way, thank you for advising as OP is trying different Distros and LM 23 will be based on Ubuntu 22.04.

(Edited)

[BiB]

**************************************************************************************

concerning your command, I got this:

Code: Select all

root@Z440-powerhost:/mnt# efibootmgr -v
BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0011,0009,0013,000A,000D,000E,000F,000C,0010,0000,0001,0002,0003,0004,0005,0006,0007,0008,000B,0012
Boot0000  Startup Menu	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)....ISPH
Boot0001  System Information	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0002  Bios Setup	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0003  3rd Party Option ROM Management	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0004  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0005  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0006  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0007  System Diagnostics	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0008  Boot Menu	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0009* hp HLDS DVDRW GUD0N 	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)N.....YM....R,Y.....ISPH
Boot000A  USB:  	BBS(65535,,0x0)/PciRoot(0x0)/Pci(0x1d,0x0)......ISPH
Boot000B  Network Boot	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot000C* #0100 ID0A LUN0 ATA      ST3000DM001-9Y	BBS(HD,Harddisk1,0x0)/PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)......ISPH
Boot000D* hp HLDS DVDRW GUD0N 	BBS(CDROM,CDROM1,0x400)/PciRoot(0x0)/Pci(0x1f,0x2)......ISPH
Boot000E* #0100 ID0B LUN0 ATA      SanDisk SSD PL	BBS(HD,Harddisk2,0x0)/PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)......ISPH
Boot000F* #0100 ID09 LUN0 HGST     HUC156060CS420	BBS(HD,Harddisk3,0x0)/PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)......ISPH
Boot0010* IBA GE Slot 00C8 v1550	BBS(Network,Network1,0x0)/PciRoot(0x0)/Pci(0x19,0x0)......ISPH
Boot0011  USB:  	PciRoot(0x0)/Pci(0x1d,0x0)N.....YM....R,Y.....ISPH
Boot0012  HP Recovery	FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(9d8243e8-8381-453d-aceb-c350ee7757ca)......ISPH
Boot0013* Fedora	HD(1,GPT,76816e74-240e-db42-855f-b200c8ea74ae,0x800,0xfa000)/File(\EFI\fedora\shimx64.efi)....ISPH
Boot0014* endeavouros-3613	HD(1,GPT,76816e74-240e-db42-855f-b200c8ea74ae,0x800,0xfa000)/File(\EFI\endeavouros-3613\grubx64.efi)
root@Z440-powerhost:/mnt# 

**************************************************************************************
concerning your other command, this is strange: there is nothing in that efi folder:
[is it in another location, like the MBR? As you know I have no clue about EFI, yet. THis is changing by the minute, though
btw, this e18e34a4-613b-4504-a4ac-5f8a227a6f5e partition is endeavour linux which has installed the current and working grub2.]

Code: Select all

root@Z440-powerhost:/media/mint/e18e34a4-613b-4504-a4ac-5f8a227a6f5e/boot/efi# ls
root@Z440-powerhost:/media/mint/e18e34a4-613b-4504-a4ac-5f8a227a6f5e/boot/efi# cd ..
root@Z440-powerhost:/media/mint/e18e34a4-613b-4504-a4ac-5f8a227a6f5e/boot# cd ..
root@Z440-powerhost:/media/mint/e18e34a4-613b-4504-a4ac-5f8a227a6f5e# cat etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=524C-12E9                            /boot/efi      vfat    umask=0077 0 2
UUID=e18e34a4-613b-4504-a4ac-5f8a227a6f5e /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
# swap was on /dev/sda2 ??? during installation
UUID=696a3a79-bdf5-4531-bae8-2a14a096646a none            swap    sw              0       0

root@Z440-powerhost:/media/mint/e18e34a4-613b-4504-a4ac-5f8a227a6f5e# 

**************************************************************************************

Now, as of the Windows boot entry, I will scrabble something out of my backup file which worked last year (below) and the entries from this useful site (https://www.gnu.org/software/grub/manua ... onfig.html)
switching "hd2,msdos3" to "hd2,gpt3" of course.

Code: Select all

#!/bin/sh
exec tail -n +3 $0
# 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.

menuentry "Windows 10 AMELIORATED" --class windows --class os {
   insmod part_msdos
   insmod ntfs
   insmod ntldr
   search --no-floppy --fs-uuid --set=root ECDCA890DCA8571C --hint-bios=hd0,msdos3 
   ntldr (hd0,msdos3)/bootmgr
}
EOF

As always, gentoo provides some documentation: https://wiki.gentoo.org/wiki/GRUB2/Advanced_storage
'insmod part_gpt (or insmod part_msdos) is needed otherwise GRUB2 will not be able to read the partition table.

insmod mdraid1x is required for RAID v1.1 or higher. If using RAID v0.9 or v1.0 the RAID module might not be needed (mdraid09 for v0.9) because the RAID information is stored at the end of the partition. Any references to insmod raid are obsolete.

insmod ext2 is required for ext partitions. For a other file systems substitute the appropriate module.'

***

...customizing the grub entries (or templates) here in /etc/grub.d ('40_' file)

Code: Select all

# ls
00_header  10_linux  10_linux.bak  20_linux_xen  30_os-prober  30_os-prober.bak  30_uefi-firmware  40_custom  41_custom  README

...and then do 'grub-mkconfig'.

[BiB]

how do I backup my current grub2 setting btw?

it should be the mbr plus the EFI directory, or what??
My EFI seems to be not mounted.... Where is it?

Code: Select all

# dd if=/dev/sdX of=/tmp/sda-mbr.bin bs=512 count=1

Code: Select all

root@Z440-powerhost:/# mount /boot/efi/
root@Z440-powerhost:/# ls -lah boot/efi/
total 8.0K
drwxr-xr-x 2 root root 4.0K jun 27 23:59 .
drwxr-xr-x 4 root root 4.0K jun 28 02:58 ..
root@Z440-powerhost:/# cd boot/efi/
root@Z440-powerhost:/boot/efi# ls

Code: Select all

cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

# / was on /dev/sdc4 during installation
UUID=71e0d363-a39d-463f-a648-389075599073 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda1 during installation
UUID=524C-12E9  /boot/efi       vfat    umask=0077      0       1

# /home was on /dev/sda5 during installation
UUID=48caee49-7912-4601-8fa8-3ef35f53ad1f /home           ext4    defaults        0       2
[...]

[Jo-con-Ël]

1)I told you to post back those codes result from Linux Mint terminal, when booting Linux Mint option from GRUB menu. You wont get ls /boot/efi/EFI results if you are not running Linux Mint (or if browsing Mint partition from another system) as EFI partition is not mounted .

2)I also ask you for another codes result you didn't post back (see edited last post). Those codes results are needed, even more now you are talking about RAID and no RAID volumen was shown on previous (uncomplete?) parted -l image..

3) Do not create custom entries now and take into account what I said before. You wont be able to boot any custom entry if pointing to a BIOS Legacy system (i.e. not installed on UEFI mode). Notice the menu entry you are talking about is a wrong UEFI boot option as it its pointing to Windows loader on Windows partition, that in case BIOS Legacy installation. If Windows was intalled on UEFI mode a valid meny entry will be

menuentry "Windows" --class windows {
insmod part_gpt
search --no-floppy --set=root --fs-uuid 524C-12E9
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}

That custom menuentry is pointing to Windows efi file on EFI partition.

You need to be sure EFI partition UUID is that (that why sudo blkid is need) and Windows loader (bootmgfw.efi) needs to be placed on that path as it would do when installing Windows on UEFI mode (that why i asked for ls /boot/efi/EFI result, to be sure there are ubuntu, Microsoft, Endeavouros, Fedora or whatever other folders where UEFI systems place its loaders when installing on UEFI mode).

Endeaveouros and Fedora were intalled in UEFI mode. They have their own loaders on EFI partiton folders and are shown as BootOpton on efibootmgr, but Windows (windows boot manger) and ubuntu are not shown. Maybe previous EFI partition was removed or formated or Ubuntu fails on installing efi-loader...who knows.

If you have intalled Mint on UEFI mode it will be shown now on Endeaveouros GRUB too, never mind there is no ubuntu folder on EFI partition.

Windows (always) is another case. Even if theres is such Microsoft folder and its efi laoder sometimes (as on RAID setup) it is not detected by grub (ie, running sudo update-grub or sudo os-prober from system directing boot). You need to create a custom entry for Winodws in that case.

Of course, if Microsoft folder does not exist custom entry is not possible. You will need to repair Windows boot first from its installation media.

[BiB]

Ok, thanks.
I ll come back with these results that you asked for later.

Just so you guys know:
Windows was installed in legacy mode and I just rsync it back to a clear NTFS partition.

To your question 1)
Why do you want the results from Linux mint?

[Jo-con-Ël]

Just so you guys know:
Windows was installed in legacy mode and I just rsync it back to a clear NTFS partition.

You will need to install Windows on UEFI mode or convert that Windows BIOS legacy installation wherever it is installed to UEFI (there are tutorials out there). In other cases, you wont be able to boot Windows from GRUB menu (it wont be detected and no custom entry will work) as far as I know. Now you need to boot that installed Windows from computer boot menu choosing the drive where it is installed option (i.e. BIOS legacy boot option).

To your question 1)
Why do you want the results from Linux mint?

To be sure LM was installed on UEFI mode (it looks like so as per fstab), EFI partition is mounted on /boot/efi (so, no problems on booting Mint with EFI partition UUID), confirm there is no ubuntu folder on that EFI partition,...in resume to find an explanation why Linux Mint (ubuntu) is not detected as UEFI Boot Option by your firmware or efibootmgr.

[BiB]

right.. thanks so far.

So 1)
here is the output of parted:

Code: Select all

root@Z440-powerhost:/home/mint# parted -l
Modèle : ATA ST3000DM001-9YN1 (scsi)
Disque /dev/sda : 3001GB
Taille des secteurs (logiques/physiques) : 512B/4096B
Table de partitions : gpt
Drapeaux de disque : 

Numéro  Début   Fin     Taille  Système de fichiers  Nom     Drapeaux
 1      1049kB  525MB   524MB   fat16                        msftdata
 2      525MB   47.8GB  47.2GB  linux-swap(v1)       swap    swap
 3      47.8GB  2247GB  2199GB  ext4
 4      2247GB  2464GB  217GB   ext4                 matrix
 5      2464GB  3001GB  537GB   ext4                 home


Modèle : HGST HUC156060CS4204 (scsi)
Disque /dev/sdb : 600GB
Taille des secteurs (logiques/physiques) : 512B/4096B
Table de partitions : msdos
Drapeaux de disque : 

Numéro  Début   Fin     Taille  Type     Système de fichiers  Drapeaux
 1      1049kB  51.5GB  51.5GB  primary  ntfs
 3      51.5GB  159GB   107GB   primary
 4      159GB   600GB   441GB   primary  btrfs


Modèle : ATA SanDisk SSD PLUS (scsi)
Disque /dev/sdc : 240GB
Taille des secteurs (logiques/physiques) : 512B/512B
Table de partitions : gpt
Drapeaux de disque : 

Numéro  Début   Fin     Taille  Système de fichiers  Nom                   Drapeaux
 1      1049kB  525MB   524MB   fat16                EFI System Partition  démarrage, esp
 2      525MB   5894MB  5369MB  ext4                 alpine
 3      5894MB  57.4GB  51.5GB  ext4                 ferenOS
 4      57.4GB  74.6GB  17.2GB  ext4                 mint
 5      74.6GB  178GB   103GB   ntfs                 win                   msftres
 6      178GB   195GB   17.2GB  ext4                 fedora
 7      195GB   214GB   19.3GB  ext4                 popOS
 8      214GB   240GB   25.9GB  ext4                 endeavour


root@Z440-powerhost:/home/mint# 

2)
it is done from linux mint, I made a screen.

3)
Let's not worry about the bloody windows. I have got a second machine with the same system running, so no need to fix the legacy install into a uefi and spend lots of time,
BTW, if you guys don't know this, I kind of like the idea of windows AME https://ameliorated.info/. Here is a video https://www.youtube.com/watch?v=YTL0i5XzS7k.

[BiB]

additionally cleaner to read here:

Code: Select all

root@Z440-powerhost:/home/mint/local-backup# rsync -aAXv /boot/efi/ boot-efi-clean1
sending incremental file list
created directory boot-efi-clean1
./
EFI/
EFI/BOOT/
EFI/BOOT/BOOTX64.EFI
EFI/BOOT/fbx64.efi
EFI/endeavouros-3613/
EFI/endeavouros-3613/grubx64.efi
EFI/fedora/
EFI/fedora/BOOTX64.CSV
EFI/fedora/grub.cfg
EFI/fedora/grub.cfg.rpmsave
EFI/fedora/grubx64.efi
EFI/fedora/mmx64.efi
EFI/fedora/shim.efi
EFI/fedora/shimx64.efi

sent 5,764,464 bytes  received 275 bytes  11,529,478.00 bytes/sec
total size is 5,762,272  speedup is 1.00
root@Z440-powerhost:/home/mint/local-backup# blkid 
/dev/sdc4: UUID="71e0d363-a39d-463f-a648-389075599073" TYPE="ext4" PARTLABEL="mint" PARTUUID="0a51517d-6159-6846-abcd-5cbdc172c36b"
/dev/sdb1: LABEL="VIRTUAL" UUID="283AC72E3AC6F7B8" TYPE="ntfs" PARTUUID="a7d8a7db-01"
/dev/sdb3: LABEL="SHARE" UUID="621B-AF24" TYPE="exfat" PTTYPE="dos" PARTUUID="a7d8a7db-03"
/dev/sdb4: LABEL="LBRY" UUID="31466795-73f2-4d52-88d5-1fa83f8e5526" UUID_SUB="0ea2c1ff-ddb1-4507-9cc6-b1e8f7d7cc29" TYPE="btrfs" PARTUUID="a7d8a7db-04"
/dev/sdc1: SEC_TYPE="msdos" LABEL_FATBOOT="EFI" LABEL="EFI" UUID="524C-12E9" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="76816e74-240e-db42-855f-b200c8ea74ae"
/dev/sdc2: LABEL="alpine" UUID="d4e2923b-72ab-4e50-b097-dd0becd80117" TYPE="ext4" PARTLABEL="alpine" PARTUUID="1adb8658-f01e-074a-bc41-c23e332ed261"
/dev/sdc3: UUID="a77760e8-b173-4ac1-bc01-6971df17e8ea" TYPE="ext4" PARTLABEL="ferenOS" PARTUUID="4aa1c1f5-d26c-7f4e-a10f-baae15b6106b"
/dev/sdc5: UUID="434BBC686008FCEF" TYPE="ntfs" PTTYPE="dos" PARTLABEL="win" PARTUUID="1eb6819f-035d-f542-b672-71507c03ad79"
/dev/sdc6: LABEL="fedora" UUID="ece496de-7735-4455-b7f2-8ff5940dfdd0" TYPE="ext4" PARTLABEL="fedora" PARTUUID="c26db2d8-e917-0447-9bdf-81d349630f6d"
/dev/sdc7: UUID="193b08c5-d4c1-48f5-b063-99c8a0b60716" TYPE="ext4" PARTLABEL="popOS" PARTUUID="53e31627-2088-8d45-9772-0c54ce502ac2"
/dev/sdc8: UUID="e18e34a4-613b-4504-a4ac-5f8a227a6f5e" TYPE="ext4" PARTLABEL="endeavour" PARTUUID="6d950920-2517-b343-97d7-21b3ffd1d45f"
/dev/sda1: SEC_TYPE="msdos" UUID="5246-58FF" TYPE="vfat" PARTUUID="f25d70b0-5723-6c47-abce-9c0f7e276bc2"
/dev/sda2: LABEL="swap" UUID="8fae221f-817d-493d-a8ec-d7688a29cc96" TYPE="swap" PARTLABEL="swap" PARTUUID="9aa6f258-c75a-8044-aaac-2514c4dc5ca6"
/dev/sda3: LABEL="server" UUID="b48c40ee-02b0-4368-bc6d-ddebabafa389" TYPE="ext4" PARTUUID="4b284eca-bdd0-8a45-bce6-b4c5839705af"
/dev/sda4: UUID="63fa539e-344a-4e26-bbcc-a6ea6d7d2d53" TYPE="ext4" PARTLABEL="matrix" PARTUUID="6d1213bf-08ef-4cb8-834b-f54bb73d9cc9"
/dev/sda5: UUID="48caee49-7912-4601-8fa8-3ef35f53ad1f" TYPE="ext4" PARTLABEL="home" PARTUUID="78aa6785-31b2-417e-973d-1b176e6b7ac1"
root@Z440-powerhost:/home/mint/local-backup# 

I don't understand however, why fedora installer wrote its grub.cfg into the EFI folder and endeavour somehow not. If you can get any important info out of this, please let me know.

[BiB]

And sorry to ask one more thing (I figure some of you are getting paid somehow ?):

where is the grub.cfg file that is actually being used?
I believe it is (relative from Linux Mint) this one here: /mnt# cat endeavour/boot/grub/grub.cfg

How could I backup my status quo, in case my boot manager gets destroyed by some automated install or a kernel update?
So thanks a lot again for that help.

output:

Code: Select all

root@Z440-powerhost:/mnt# cat endeavour/etc/default/grub
# GRUB boot loader configuration

GRUB_DEFAULT=saved
GRUB_TIMEOUT=6
GRUB_DISTRIBUTOR="EndeavourOS"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 nowatchdog nvme_load=YES"
GRUB_CMDLINE_LINUX_DEFAULT="verbose loglevel=3 nowatchdog nvme_load=YES"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=false
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=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=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

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

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME=/boot/grub/themes/EndeavourOS/theme.txt

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

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
GRUB_DISABLE_SUBMENU=y
root@Z440-powerhost:/mnt# cat endeavour/boot/
efi/                          grub/                         initramfs-linux-fallback.img  initramfs-linux.img           vmlinuz-linux                 
root@Z440-powerhost:/mnt# cat endeavour/boot/grub/grub.cfg
grub.cfg           grub.cfg.new       grub.cfg.original  
root@Z440-powerhost:/mnt# cat endeavour/boot/grub/grub.cfg
#
# 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 ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  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="${saved_entry}"
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
set root='hd2,gpt8'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt8 --hint-efi=hd2,gpt8 --hint-baremetal=ahci2,gpt8  e18e34a4-613b-4504-a4ac-5f8a227a6f5e
else
  search --no-floppy --fs-uuid --set=root e18e34a4-613b-4504-a4ac-5f8a227a6f5e
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_gpt
insmod ext2
set root='hd2,gpt8'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt8 --hint-efi=hd2,gpt8 --hint-baremetal=ahci2,gpt8  e18e34a4-613b-4504-a4ac-5f8a227a6f5e
else
  search --no-floppy --fs-uuid --set=root e18e34a4-613b-4504-a4ac-5f8a227a6f5e
fi
insmod gfxmenu
loadfont ($root)/boot/grub/themes/EndeavourOS/unifont-regular-16.pf2
insmod png
set theme=($root)/boot/grub/themes/EndeavourOS/theme.txt
export theme
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=6
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=6
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'EndeavourOS, on linux' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-e18e34a4-613b-4504-a4ac-5f8a227a6f5e' {
	savedefault
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd2,gpt8'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt8 --hint-efi=hd2,gpt8 --hint-baremetal=ahci2,gpt8  e18e34a4-613b-4504-a4ac-5f8a227a6f5e
	else
	  search --no-floppy --fs-uuid --set=root e18e34a4-613b-4504-a4ac-5f8a227a6f5e
	fi
	echo	'Loading kernel linux ...'
	linux	/boot/vmlinuz-linux root=UUID=e18e34a4-613b-4504-a4ac-5f8a227a6f5e rw  quiet loglevel=3 nowatchdog nvme_load=YES
	echo	'Initiale Ramdisk wird geladen …'
	initrd	/boot/initramfs-linux.img
}
menuentry 'EndeavourOS, on linux (fallback initramfs)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-e18e34a4-613b-4504-a4ac-5f8a227a6f5e' {
	savedefault
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod ext2
	set root='hd2,gpt8'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt8 --hint-efi=hd2,gpt8 --hint-baremetal=ahci2,gpt8  e18e34a4-613b-4504-a4ac-5f8a227a6f5e
	else
	  search --no-floppy --fs-uuid --set=root e18e34a4-613b-4504-a4ac-5f8a227a6f5e
	fi
	echo	'Loading kernel linux ...'
	linux	/boot/vmlinuz-linux root=UUID=e18e34a4-613b-4504-a4ac-5f8a227a6f5e rw  quiet loglevel=3 nowatchdog nvme_load=YES
	echo	'Initiale Ramdisk wird geladen …'
	initrd	/boot/initramfs-linux-fallback.img
}

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

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

### BEGIN /etc/grub.d/30_os-prober ###
	menuentry 'Alpine Linux v3.13 (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/vmlinuz-lts--d4e2923b-72ab-4e50-b097-dd0becd80117' {
		savedefault
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  5246-58FF
		else
		  search --no-floppy --fs-uuid --set=root 5246-58FF
		fi
		linux /vmlinuz-lts root=/dev/sdc2
	}
	menuentry 'Alpine Linux v3.13 (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/kernel-debian-sources-x86_64-5.9.6_p1--d4e2923b-72ab-4e50-b097-dd0becd80117' {
		savedefault
		insmod part_gpt
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  5246-58FF
		else
		  search --no-floppy --fs-uuid --set=root 5246-58FF
		fi
		linux /kernel-debian-sources-x86_64-5.9.6_p1 root=/dev/sdc2
		initrd /initramfs-debian-sources-x86_64-5.9.6_p1
	}

	menuentry 'Linux Mint 20.3 Xfce (auf /dev/sdc4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.4.0-91-generic--71e0d363-a39d-463f-a648-389075599073' {
		savedefault
		insmod part_gpt
		insmod ext2
		set root='hd2,gpt4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  71e0d363-a39d-463f-a648-389075599073
		else
		  search --no-floppy --fs-uuid --set=root 71e0d363-a39d-463f-a648-389075599073
		fi
		linux /boot/vmlinuz-5.4.0-91-generic root=UUID=71e0d363-a39d-463f-a648-389075599073 ro quiet splash
		initrd /boot/initrd.img-5.4.0-91-generic
	}
	menuentry 'Linux Mint 20.3 Xfce, avec Linux 5.4.0-91-generic (auf /dev/sdc4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.4.0-91-generic--71e0d363-a39d-463f-a648-389075599073' {
		savedefault
		insmod part_gpt
		insmod ext2
		set root='hd2,gpt4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  71e0d363-a39d-463f-a648-389075599073
		else
		  search --no-floppy --fs-uuid --set=root 71e0d363-a39d-463f-a648-389075599073
		fi
		linux /boot/vmlinuz-5.4.0-91-generic root=UUID=71e0d363-a39d-463f-a648-389075599073 ro quiet splash
		initrd /boot/initrd.img-5.4.0-91-generic
	}
	menuentry 'Linux Mint 20.3 Xfce, avec Linux 5.4.0-91-generic (recovery mode) (auf /dev/sdc4)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.4.0-91-generic--71e0d363-a39d-463f-a648-389075599073' {
		savedefault
		insmod part_gpt
		insmod ext2
		set root='hd2,gpt4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt4 --hint-efi=hd2,gpt4 --hint-baremetal=ahci2,gpt4  71e0d363-a39d-463f-a648-389075599073
		else
		  search --no-floppy --fs-uuid --set=root 71e0d363-a39d-463f-a648-389075599073
		fi
		linux /boot/vmlinuz-5.4.0-91-generic root=UUID=71e0d363-a39d-463f-a648-389075599073 ro recovery nomodeset dis_ucode_ldr
		initrd /boot/initrd.img-5.4.0-91-generic
	}

	menuentry 'Fedora Linux 36 (Server Edition) (auf /dev/sdc6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-0-rescue-e621dc78d87a4a299dce50434514a7fa--ece496de-7735-4455-b7f2-8ff5940dfdd0' {
		savedefault
		insmod part_gpt
		insmod ext2
		set root='hd2,gpt6'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt6 --hint-efi=hd2,gpt6 --hint-baremetal=ahci2,gpt6  ece496de-7735-4455-b7f2-8ff5940dfdd0
		else
		  search --no-floppy --fs-uuid --set=root ece496de-7735-4455-b7f2-8ff5940dfdd0
		fi
		linux /boot/vmlinuz-0-rescue-e621dc78d87a4a299dce50434514a7fa root=/dev/sdc6
		initrd /boot/initramfs-0-rescue-e621dc78d87a4a299dce50434514a7fa.img
	}
	menuentry 'Fedora Linux 36 (Server Edition) (auf /dev/sdc6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.17.5-300.fc36.x86_64--ece496de-7735-4455-b7f2-8ff5940dfdd0' {
		savedefault
		insmod part_gpt
		insmod ext2
		set root='hd2,gpt6'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt6 --hint-efi=hd2,gpt6 --hint-baremetal=ahci2,gpt6  ece496de-7735-4455-b7f2-8ff5940dfdd0
		else
		  search --no-floppy --fs-uuid --set=root ece496de-7735-4455-b7f2-8ff5940dfdd0
		fi
		linux /boot/vmlinuz-5.17.5-300.fc36.x86_64 root=/dev/sdc6
		initrd /boot/initramfs-5.17.5-300.fc36.x86_64.img
	}
	menuentry 'Fedora Linux 36 (Server Edition) (auf /dev/sdc6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.18.6-200.fc36.x86_64--ece496de-7735-4455-b7f2-8ff5940dfdd0' {
		savedefault
		insmod part_gpt
		insmod ext2
		set root='hd2,gpt6'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt6 --hint-efi=hd2,gpt6 --hint-baremetal=ahci2,gpt6  ece496de-7735-4455-b7f2-8ff5940dfdd0
		else
		  search --no-floppy --fs-uuid --set=root ece496de-7735-4455-b7f2-8ff5940dfdd0
		fi
		linux /boot/vmlinuz-5.18.6-200.fc36.x86_64 root=/dev/sdc6
		initrd /boot/initramfs-5.18.6-200.fc36.x86_64.img
	}

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

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

[pbear]

I figure some of you are getting paid somehow ?

Not correct.

[pbear]

... Mint is based on Ubuntu and the os-prober has been disabled by default ...

Bear in mind, this isn't true of LM20, but presumably will be for LM21.

Seems like a silly change to me. Mounting my own partitions is a security risk now? Will cause lots of confusion for newbies. And it's puzzling the Grub Manual says to edit grub.cfg. configfile entries belong in 40-custom or a custom.cfg file. grub.cfg is regenerated every time update-grub is run.

ETA: Rereading the Grub manual, I realize they intend multi-boot users now to disable update-grub and compile grub.cfg manually. Seriously?

I'm beginning to wonder whether it's time to switch to the rEFInd boot manager.

[Jo-con-Ël]

Now it is almost clear what you did when intalling Mint and afterwords but I don´t know why. As per Mint /etc/fstab, you have installed Mint on UEFI mode using sda1 as EFI partition, sda5 as /home and sdc4 as root. Then you have changed EFI partition UUID on fstab and now it is mounting EFI partiton on sdc (sdc1).

Code: Select all

# / was on /dev/sdc4 during installation
UUID=71e0d363-a39d-463f-a648-389075599073 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda1 during installation
UUID=524C-12E9  /boot/efi       vfat    umask=0077      0       1

# /home was on /dev/sda5 during installation
UUID=48caee49-7912-4601-8fa8-3ef35f53ad1f /home           ext4    defaults        0       2

Also you have remove sda1 flags, it is not flagged as boot, esp. It look like an unused partition and sure it is not a valid EFI partition.

If it was before you can be sure mounting that partition from file browser or from terminal sudo mount /dev/sda1 /mnt and looking inside (ls /mnt/EFI/ubuntu). Also related with you next question see grub.cfg file contents (cat /mnt/EFI/ubuntu/grub.cfg). Then unmount (sudo umount /mnt).

If there is such ubuntu folder, it is not empty (there are .efi files, grub.cfg,..) it can be re-flagged from live media as boot,esp in order firmware can detect it and get Mint (Ubuntu) UEFI Boot Option on computer setup, boot menu and/or efibootmgr and then modify Mint´ s fstab to change EFI partition UUID again (sda1 UUID is 5246-58FF).

As you can see there is no need to get separated EFI partitions on every disk if internals. Also there is no need to install other systems efi-loader nor GRUB as you can boot a Linux system from another system GRUB if they are installed in the same mode. Just remember to run sudo update-grub on that system directing boot process. Even on multi-booting some users prefer installing a pre-loader as Refind and do not intall grub at all.

I don't understand however, why fedora installer wrote its grub.cfg into the EFI folder and endeavour somehow not. If you can get any important info out of this, please let me know.

I know what Ubuntu and derivates as Mint, also Fedora, do. They create a grub.cfg files inside their EFI folder. That file only tell GRUB where is the /boot/grub folder, in order to charge modules GRUB needs,... and another grub.cfg file (i.e. Fedora/boot/grub/grub.cfg) to create GRUB menu you can see on booting.

Sure you can find how endeavour boots on it own forums. It is Arch based and it has several options including hardcode boot partition into the grubx64.efi file so there would no need tell GRUB where to find (i.e. no need for a grub.cfg file on its dedicated folder on EFI partition).

where is the grub.cfg file that is actually being used?
I believe it is (relative from Linux Mint) this one here: /mnt# cat endeavour/boot/grub/grub.cfg

You are right. You can see (and change) default (first) UEFI boot option on Computer setup boot order. Last efibootmgr result shows it is booting endeavouros by default

BootCurrent: 0014
Timeout: 0 seconds
BootOrder: 0014,0011...
(...)
Boot0014* endeavouros-3613

So, yes, it is using that /boot/grub/grub.cfg file from inside endeavouros root partition.

Notice if you place Fedora UEFI boot option first(by default) on Computer setup or using efibootmngr codes, then it will be directing boot process, as it was before installing endeavouros (you will see Fedora GRUB menu, Fedora menu entry default one,....) Maybe you will need to run sudo apdate-grub in order to detect new/other systems installed or new kernels for systems already installed, and that is all.

You can do in the same way if decide to recue Ubuntu uefi option as indicated on sda1 or install it on sdc1 EFI partition (just runing sudo grub-install /dev/sdc from a Mint working session ubuntu option will direct boot process).

The system directing boot must be the one you use more frequently not the newest/last installed one.

How could I backup my status quo, in case my boot manager gets destroyed by some automated install or a kernel update?

It is not probable on Linux, it doesn't happen spontaneously and you would be able to repair boot when happens w/o a backup copy booting another system or a live media.

[BiB]

Now it is almost clear what you did when intalling Mint and afterwords but I don´t know why. As per Mint /etc/fstab, you have installed Mint on UEFI mode using sda1 as EFI partition, sda5 as /home and sdc4 as root. Then you have changed EFI partition UUID on fstab and now it is mounting EFI partiton on sdc (sdc1).

Code: Select all

# / was on /dev/sdc4 during installation
UUID=71e0d363-a39d-463f-a648-389075599073 /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/sda1 during installation
UUID=524C-12E9  /boot/efi       vfat    umask=0077      0       1

# /home was on /dev/sda5 during installation
UUID=48caee49-7912-4601-8fa8-3ef35f53ad1f /home           ext4    defaults        0       2

Thanks 4 your answers.
Uh! - that may be true and was a mistake.
However, that "spare" EFI partition, which I put there in precausion for the future, is empty [but mint works and let's not worry about it!]:

Code: Select all

mint@Z440-powerhost:/mnt$ sudo mkdir efi2
[sudo] Mot de passe de mint :      
mint@Z440-powerhost:/mnt$ su
Mot de passe : 
root@Z440-powerhost:/mnt# mount /dev/sda1 efi2/
root@Z440-powerhost:/mnt# ls efi2/
root@Z440-powerhost:/mnt# 

Also you have remove sda1 flags, it is not flagged as boot, esp. It look like an unused partition and sure it is not a valid EFI partition.

If it was before you can be sure mounting that partition from file browser or from terminal sudo mount /dev/sda1 /mnt and looking inside (ls /mnt/EFI/ubuntu). Also related with you next question see grub.cfg file contents (cat /mnt/EFI/ubuntu/grub.cfg). Then unmount (sudo umount /mnt).

If there is such ubuntu folder, it is not empty (there are .efi files, grub.cfg,..) it can be re-flagged from live media as boot,esp in order firmware can detect it and get Mint (Ubuntu) UEFI Boot Option on computer setup, boot menu and/or efibootmgr and then modify Mint´ s fstab to change EFI partition UUID again (sda1 UUID is 5246-58FF).

Hm.. it looks right to me, that sdc1 EFI partition:

Code: Select all

root@Z440-powerhost:/mnt# parted /dev/sdc print
Modèle : ATA SanDisk SSD PLUS (scsi)
Disque /dev/sdc : 240GB
Taille des secteurs (logiques/physiques) : 512B/512B
Table de partitions : gpt
Drapeaux de disque : 

Numéro  Début   Fin     Taille  Système de fichiers  Nom                   Drapeaux
 1      1049kB  525MB   524MB   fat16                EFI System Partition  démarrage, esp
 2      525MB   5894MB  5369MB  ext4                 alpine
 3      5894MB  57.4GB  51.5GB  ext4                 ferenOS
 4      57.4GB  74.6GB  17.2GB  ext4                 mint
 5      74.6GB  178GB   103GB   ntfs                 win                   msftres
 6      178GB   195GB   17.2GB  ext4                 fedora
 7      195GB   214GB   19.3GB  ext4                 popOS
 8      214GB   240GB   25.9GB  ext4                 endeavour

Demarrage means "start" "or "boot".
So I looked up how to create an EFI partition. https://wiki.gentoo.org/wiki/Handbook:A ... _.28ESP.29
What is the esp flag, though? Does it come naturally when I type it 'EFI System' partition (type 1 in gdisk)?
And it needs to be toggled to boot?

As you can see there is no need to get separated EFI partitions on every disk if internals.

Sure enough.

Also there is no need to install other systems efi-loader nor GRUB as you can boot a Linux system from another system GRUB if they are installed in the same mode.

Yes However, nowadays it is not possible to install linux without a bootloader. except for gentoo and alpine linux and a few others. (which is awesome!)
Am I correct...?
You might install it to /dev/null

[BiB]

I figure some of you are getting paid somehow ?

Not correct.

OK. too bad. me neither.
Might have sent you some LTC or XMR, if I just had enough, yet.

Still an important question:

So I still install grub2 to /dev/sda [in general]? Meaning the master boot record?
What, if I have three hdd? Either one?
Where do you have it?
Or to the EFI partition /dev/sda1 [generally]?

Thanks again!
I learned a lot and hopefully some other dudes as wel...

[BiB]

Linux Mint XFCE lacks a command, btw:

Code: Select all

root@Z440-powerhost:/boot# cd ..
root@Z440-powerhost:/# tree boot/

La commande « tree » n'a pas été trouvée, mais peut être installée avec :

apt install tree

root@Z440-powerhost:/# apt-get install tree
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Les NOUVEAUX paquets suivants seront installés :
  tree
0 mis à jour, 1 nouvellement installés, 0 à enlever et 3 non mis à jour.
Il est nécessaire de prendre 43.0 ko dans les archives.
Après cette opération, 115 ko d'espace disque supplémentaires seront utilisés.
Réception de :1 http://ftp***/ubuntu focal/universe amd64 tree amd64 1.8.0-1 [43.0 kB]
43.0 ko réceptionnés en 0s (168 ko/s)
Sélection du paquet tree précédemment désélectionné.
(Lecture de la base de données... 313668 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../tree_1.8.0-1_amd64.deb ...
Dépaquetage de tree (1.8.0-1) ...
Paramétrage de tree (1.8.0-1) ...
Traitement des actions différées (« triggers ») pour man-db (2.9.1-1) ...
root@Z440-powerhost:/# tree boot/
boot/
├── config-5.4.0-121-generic
├── config-5.4.0-91-generic
├── efi
│   └── EFI
│       ├── BOOT
│       │   ├── BOOTX64.EFI
│       │   └── fbx64.efi
│       ├── endeavouros-3613
│       │   └── grubx64.efi
│       └── fedora
│           ├── BOOTX64.CSV
│           ├── grub.cfg
│           ├── grub.cfg.rpmsave
│           ├── grubx64.efi
│           ├── mmx64.efi
│           ├── shim.efi
│           └── shimx64.efi
├── grub
│   ├── fonts
│   │   └── unicode.pf2
│   ├── gfxblacklist.txt
│   ├── grub.cfg
│   ├── grubenv
│   ├── unicode.pf2
│   └── x86_64-efi
│       ├── acpi.mod
│       ├── adler32.mod
│       ├── affs.mod
│       [...]
├── initrd.img -> initrd.img-5.4.0-121-generic
├── initrd.img-5.4.0-121-generic
├── initrd.img-5.4.0-91-generic
├── initrd.img.old -> initrd.img-5.4.0-91-generic
├── System.map-5.4.0-121-generic
├── System.map-5.4.0-91-generic
├── vmlinuz -> vmlinuz-5.4.0-121-generic
├── vmlinuz-5.4.0-121-generic
├── vmlinuz-5.4.0-91-generic
└── vmlinuz.old -> vmlinuz-5.4.0-91-generic

8 directories, 304 files
root@Z440-powerhost:/#