On 28/10/2020 15.48, DennisG wrote:
On 10/28/20 7:00 AM, Carlos E. R. wrote:
On 28/10/2020 05.54, Robin Klitscher wrote:
On 28/10/2020 17:10, Felix Miata wrote:
Robin Klitscher composed on 2020-10-28 12:58 (UTC+1300):
...
In the setup you posted, the partition pointed by the two non working did not exist, so there was something weird going on.
It seems that the hurdles here are fundamentally caused by sharing a single /boot/efi partition across 3 installations. Is that really needed???
Why not? In fact, several such partitions in the same disk can be trouble, some UEFI not reading them all and not offering to boot from some one. The hurdle is caused by YaST installation not asking what name to use for EFI section.
Just fwiw, seeing how far along you are with your current approach, but its worth considering that it might be easier to use a separate /boot/efi for each install,
no, don't do that.
using one grub as the master which chainloads the other two or alternatively using the bios boot selection feature (if the machine supports that) to choose which install to boot. I use both, i.e., chainloading ordinarily while having the bios boot as a backup in the event of a problem booting from the master.
We are trying to activate the bios part first.
Re "something weird going on": The TW and -2 fstab files point to two partitions that no longer exist, yet the partition /dev/nvme1n1p1 (which now holds swap) is not included. (A good guess would be that this first partition is where the missing UUID=0908-2851 for /boot/efi was located.)
Not probable. Swap is typically large, while EFI is typically very tiny.
In any event, two corrupted fstab's are not the result of only a "data partition" having been deleted (per the original post). Suggests that partition changes are being made from within one install that affects the other install(s), or that an outside tool is being used. Begs the question, what is OP using Parted Magic/gparted for and why?
Perhaps that missing partition EFI was also in sda, or it was reformatted as the current EFI partition by the last installation. I vote for the second. Then that Grub allowed to boot any of the three systems, so the mishap was not noticed. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)