Run clear linux after multi distributions installation

Hi
I installed Clear Linux on /dev/sdb2 while there is a Debian and a Ubuntu distribution on sdba.
sudo update-grub confirms the installation with a message saying ‘Clear Linux OS found on /dev/sdb2’.
I can also mount sdb2 and see files showing an installed distribution (I think).
The grub menu I get after sudo update-grub and rebooting continues to offer Debian and Ubuntu but there is no menu item for Clear Linux.
Using grub-customizer, I can see entries for Debian or Ubuntu and then a few more mysterious items … in French. :slight_smile:

(Entrées entrantes)
espace réservé / script linux

code de script
entrée de menu / script linux

(Entrées entrantes )
espace réservé /script :linux_xen

(code de script )
espace réservé /script :linux_xen

(Entrées entrantes )
espace réservé / script os-prober

(code de script )
espace réservé / script os-prober

I suppose I can use grub-customizer and enter one of those items as a new menu item for a booting Clear Linux option along side the other distributions. I also think I might transform my computer into a brick if my assumptions are wrong.

grub-customizer offers 6 type options for a new item, I suppose it means a new menu entrie. Here are these choices :
linux, iso-linux, chargeur en chaine, memtest, autre, code de script.

Please help me by indicating if my assumptions are right so far and by suggesting next (safe) moves.

Merci !

Have you tried this
https://docs.01.org/clearlinux/latest/tutorials/multi-boot/dual-boot-linux.html

Hi docOrHu
Thanks for your answer to my request.
Indeed the link you suggest is pertinent.

Method 2: Use GRUB to Boot Clear Linux OS

is quite close to what I am trying. At step 4, Create a menu entry for systemd-boot bootloader, it suggests to use sudo blkid to Identify the UUID for EFI system partition that systemd-boot resides on. In my case, I get

LABEL=“root” UUID=“d7d16461-dc9e-4b5c-b5de-8b86e6be2262” TYPE=“ext4” PARTLABEL="/" PARTUUID=“8e810e4b-cdcb-464e-b3b8-1de594fe822f”

for /dev/sdb2, where update-grub found Clear Linux. Although there is no mention of a PARTLABEL="CLR_BOOT like in the example you suggest, I suppose I can use that UUID.
Entering those parameter in Grub-Customizer, it generates the following sequence : set root=’(hd2,2)’
search --no-floppy --fs-uuid --set d7d16461-dc9e-4b5c-b5de-8b86e6be2262
drivemap -s (hd0) ${root}
chainloader +1

So far so good, I try a reboot.
I must say I am a bit nervous … will keep you posted
JP

Test done.
Did not work.
But the good news is that my computer did not turn into a brick.
The Grub menu is still showing, Debian and Ubuntu menu items work as before.
There is even a new Clear Linux menu item !
but the new menu item leads to 2 error lines :
no such device d7d16461-dc9e-4b5c-b5de-8b86e6be2262
hd2 cannot get C/M/S values
Any idea ?

bootup Cleae Linux installer image.
what’s the output of sudo fdisk -l

BTW you need to read method 1 even though you use method 2…

Merci encore, thanks for your patience.
I am sure you are right, doctOrHu, and not only I need to read method 1 I also have to make sens of what I read. Still working on that.

Also still can not identify the Clear Linux installer image you refer to in the entries available via Grub Customizer. If possible I would prefer to continue with that interface to have a little more understanding of what I am doing and to lower the chances of breaking everything. I tried a few more manipulations with no success, getting the same error message from previous post.

Here is what I get from fdisk -l :

neb@debian:~$ sudo fdisk -l
[sudo] Mot de passe de neb :
Disque /dev/sda : 447,1 GiB, 480103981056 octets, 937703088 secteurs
Modèle de disque : KINGSTON SA400S3
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 512 octets / 512 octets
Type d’étiquette de disque : dos
Identifiant de disque : 0xf94048ce

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sda1 2048 193169407 193167360 92,1G fd RAID Linux autodét
/dev/sda2 * 193169408 232479954 39310547 18,8G ef EFI (FAT-12/16/32)
/dev/sda3 389726208 511377407 121651200 58G 83 Linux
/dev/sda4 511377408 937701375 426323968 203,3G 83 Linux

Disque /dev/sdb : 465,8 GiB, 500107862016 octets, 976773168 secteurs
Modèle de disque : WDC WD5000AAKX-0
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 512 octets / 512 octets
Type d’étiquette de disque : gpt
Identifiant de disque : EA3209C3-7581-4518-B599-05072A398B2E

Périphérique Début Fin Secteurs Taille Type
/dev/sdb1 2048 307199 305152 149M Système EFI
/dev/sdb2 307200 976771071 976463872 465,6G Racine Linux (x86-64)

Disque /dev/md0 : 92 GiB, 98834579456 octets, 193036288 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 524288 octets / 524288 octets
Type d’étiquette de disque : dos
Identifiant de disque : 0x9d7fbfc9

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/md0p1 63 498014 497952 243,1M 83 Linux
/dev/md0p2 498076 193020974 192522899 91,8G 5 Étendue
/dev/md0p5 498078 193020974 192522897 91,8G 8e LVM Linux

La partition 1 ne commence pas sur une frontière de cylindre physique.
La partition 2 ne commence pas sur une frontière de cylindre physique.
La partition 5 ne commence pas sur une frontière de cylindre physique.

Disque /dev/mapper/debian–vg-root : 75,9 GiB, 81465966592 octets, 159113216 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 524288 octets / 524288 octets

Disque /dev/mapper/debian–vg-swap_1 : 16 GiB, 17104371712 octets, 33406976 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 524288 octets / 524288 octets
neb@debian:~ ^C neb@debian:~

what you should expect to see, according to the tutorial I linked above, is something like this:

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 498481151 497430528 237.2G Linux filesystem
/dev/sda3 498481152 498993151 512000 250M Linux swap
/dev/sda4 498993152 703281151 204288000 97.4G Linux root (x86-64)

what you posted shows

/dev/sdb1 2048 307199 305152 149M Système EFI
/dev/sdb2 307200 976771071 976463872 465,6G Racine Linux (x86-64)

the uuid you need should be the one for sdb1