First I want to say Welcome and that we appreciate your trying OMLx and we are very sorry you are having this problem. Apologies for not saying so sooner.
At this point I don’t know. I would suggest to talk to OM developers. OM-Chat is often the quickest way to do that.
Your boot order shows MX Linux as where you are booting from, have you run their update grub2 command and see if it picks up the OM partition.
Boot0003* OpenMandriva_Lx_[GRUB]
I am not sure what that is, if it is a system partition or not. The original error suggests that either your partition setup or how you are partitioning in the OM Calamares partitioner has presented it with a circumstance that the current grub2 script can not handle. We need to find out why that is so.
Output of fdisk -l and screen-shot of the partitioning set-up in the Calamares installer. But I still think this is over my head knowledge wise.
If you wish to continue working with us on this a bug report would be a good idea.
MX’s grub does indeed pick up on it (as does Manjaro’s), however loading fails with the error [FAILED] Failed to start initrd-switch-root.service - Switch Root (see pictures). Also,
fdisk -l
Disk /dev/loop0: 2.84 GiB, 3051421696 bytes, 5959808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 1048576 bytes
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 860
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 1048576 bytes
Disklabel type: gpt
Disk identifier: 77D26F28-8DF3-5541-949D-8475660A6DA9
Device Start End Sectors Size Type
/dev/sda1 2048 1085440 1083393 529M Microsoft basic data
/dev/sda2 1323008 1758173183 1756850176 837.7G Microsoft basic data
/dev/sda3 1919184896 1953523711 34338816 16.4G Microsoft basic data
Disk /dev/sdb: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk model: WDC WD102KFBX-68
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes
Disklabel type: gpt
Disk identifier: 09D1C4AC-BF03-4E85-8015-B6C30907A491
Device Start End Sectors Size Type
/dev/sdb1 2048 17179871231 17179869184 8T Microsoft basic data
Disk /dev/sdc: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 1048576 bytes
Disklabel type: gpt
Disk identifier: 1CED5C95-A7D4-4353-99A1-A444B3B28D35
Device Start End Sectors Size Type
/dev/sdc1 2048 488331591 488329544 232.9G Microsoft basic data
/dev/sdc2 488331592 488397127 65536 32M Microsoft basic data
Disk /dev/sdd: 9.1 TiB, 10000831348736 bytes, 19532873728 sectors
Disk model: WDC WD102KFBX-68
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes
Disklabel type: gpt
Disk identifier: 2538B0CF-E282-4449-8085-1D97E349BE68
Device Start End Sectors Size Type
/dev/sdd1 2048 8589936639 8589934592 4T Microsoft basic data
/dev/sdd2 17385390080 19532871679 2147481600 1024G Linux filesystem
/dev/sdd3 16311648256 17385390079 1073741824 512G Linux filesystem
Partition table entries are not in disk order.
Disk /dev/sde: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 1048576 bytes
Disklabel type: gpt
Disk identifier: 1597041C-221B-46D4-A6D9-7F8395010CFF
Device Start End Sectors Size Type
/dev/sde1 2048 1083391 1081344 528M EFI System
/dev/sde2 3894050816 4313481215 419430400 200G Linux filesystem
/dev/sde3 1083392 420513791 419430400 200G Linux filesystem
/dev/sde4 1729136640 2148567039 419430400 200G Linux filesystem
/dev/sde6 7679819776 7713636351 33816576 16.1G Linux swap
/dev/sde7 2148567040 2216329215 67762176 32.3G Linux filesystem
Partition table entries are not in disk order.
Disk /dev/sdf: 3.76 GiB, 4040748544 bytes, 7892087 sectors
Disk model: USB Flash Drive
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 1048576 bytes
Disklabel type: dos
Disk identifier: 0xc771e703
Device Boot Start End Sectors Size Id Type
/dev/sdf1 * 1 6296743 6296743 3G cd unknown
/dev/sdf2 6296744 6309907 13164 6.4M ef EFI (FAT-12/16/32)
Disk /dev/zram0: 7.79 GiB, 8369733632 bytes, 2043392 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
[live@omv-3523 ~]$
Does anyone know if there’s a way to make the bootloader python script output what it’s doing and where it throws the error? I think I managed to snag the script but I’m not sure where it’s having the issue. main.py.txt (34.1 KB)