All failed (Quadruple boot, FSL, Kali, MX, SUSE)

[Marie-Sophie]

Hello,
As the title says, I'm having a very hard time getting all four to multi-boot.
Not sure what's going wrong, as I don't have anything exotic, except for the fact that I'm (obviously) not doing full-auto install.
I'm writing from the P15, on which I have Win10 and Qubes (not fully installed yet as I need help to tweak it the exact way I want)
The question here is about my T440p, which used to have Win10 + Suse + MX and multi-boot just fine.
The problems started when I completely removed Win .. which is sad as it would me I need Win to be able to boot Lx ??
OK, so let's get the basic out of the way:
The system is UEFI, With enough CPU power, enough RAM (16Gb) and plenty space (Disk0 SSD hybrid 2To + Disk2 NVMe 512Gb)
What I wanted initially was to get all heavy R/W on the SSHD (hybrid = HDD + large flash SSD) for each distro its own 64GB swap+ 64GB /tmp + 58GB /usr + 50Gb /var and the 641 DATA ( all /home symlinked to DATA)
I often crash things, I reinstall very oftern as I'm "learning to to fix" but usually just reinstall, hence the separate everything
Like I said, everything was working more or less fine until I decided to remove Win from the T440p, and now, no matter what repartitioning I do, it just doesn't boot.
Except for MX and Suse, which boot easy from the rescue DVD (it find the kernel easy, etc ..)

Initial setup:
NVMe:

• .750 /boot/efi, with right ESP code
• 2GB /boot

# and for each distros:
- 64Gb /
# and the 300Gb Win10
SSHD:
# for each distro

• 64GB swap
• 64GB /tmp
• 58GB /usr
• 50Gb /var

Current partitionning:
NVMe:
# for each distros (x4):

• 2Gb /boot
• 128GB /

SSHD:
- 2Gb /boot/efi (with correct ESP code)

# for each distro

• 64GB swap
• 64GB /tmp
• 641 GB LXDATA #single, not for each, just each /home symlinked to it)

Doesn't matter what order I install, each time it's like the /boot/efi is not recognised and boot up in either

Grub ...
IPX (network boot)

Only Suse can be booted easy from rescue DVD and sometimes shows the Fedora kernal too, not always)

I'm out of idea, and so frustrated as I'm sure it's a stupid obvious "right in my face" answer but I just can't see it.

 

[Aristarchus]

Ok, so happen when you install only one Linux.
Can you boot? If not, did you check your system BIOS settings

 

[Marie-Sophie]

Ok, so happen when you install only one Linux.
Can you boot? If not, did you check your system BIOS settings

All system are fine, NVRAM cleaned up to the minimum, and only 1 Lx boot at the time only if auto-install
Any attempt, even if only one install, of maunal install failed and lead to

> Grub

or

> IPX4 (network boot)

There is nothing to explain it yet I'M sure there is an explanation
The only difference on this machine between when I could multiboot and now that I can't is that there were a Win system running on it, there is no longer

 

[Brickwizard]

by defeating the windows, you may have deleted the Windows boot partition [which is normally shared in a multi boot situation] you may have to install grub

https://www.baeldung.com/linux/grub-efi-reinstall

 

[Marie-Sophie]

by defeating the windows, you may have deleted the Windows boot partition [which is normally shared in a multi boot situation] you may have to install grub

https://www.baeldung.com/linux/grub-efi-reinstall

hahah, yeah, thank you for the obvious.
You may have skept all the parts where I mention installing /boot/efi and a /boot for each distros

Me mentioning window$ is only as a half-joke saying that for as long as the native Win boot partition was there, I've had no probleme dual/tripl/quadruple booting, but now that it's gone, it's AS-IF it was impossible for Lx on its own to do it

 

[Marie-Sophie]

I gave up, I won't install Kali on my SSHD, I will keep trying to install in on a USB though ...
Not the live ISO, but the full desktop !
As the live ISO can't be updated, despite the partition "persistence" with the persistent file (empty) in it