I am doing a clean installation of Tumbleweed using a flash drive with the full DVD installation media. Everything goes fine until the “saving the bootloader configuration” step. At the 50% point, I get:
Error
Execution of command “/usr/sbin/shim-install”, “–config-file==/boot/grub2/grub.cfg”]] failed.
Exit code: 37
Error output: Installing for x86_64-efi platform.
Installation finished. No error reported.
invalid numeric value
Hardware:
AMD Ryzen 3 2200G CPU
MSI B450M Pro-VDH Plus motherboard
2 * 4 GiB DDR4 3000 RAM
2 * 2 TB SATA hard drive
Using CPU’s built in graphics
My partitioning:
Created RAID1 array md0 using /dev/sda and /dev/sdb
Partitioned md0 as follows:
[INDENT=2]500 MiB efi
60 GiB BtrFS mounted /
8.1 GiB swap
1.8 TiB ext4 mounted /home
(automatic subvolumes were added under /)[/INDENT]
KDE desktop selected.
In addition to the default software selection, I added file server, web server, base development, C/C+ development and kernel development.
I had this identical problem from a month old snapshot as well as the latest one.
Is there something wrong with the installer? Or is there a problem with how I’ve partitioned? E.g., can I have my efi partition in a RAID1 array? Or boot from one?
My goal, if possible, is to have everything mirrored. That way, if a drive fails, not only will all my data be safe, but the system will still be able to boot and operate normally until the failed drive is replaced and the RAID1 array is rebuilt. I will be remotely administering this Australian machine from America, and the users are completely non-technical. Hence the need for foolproof operation and recovery from failure.
Any help will be greatly appreciated.
What FS is used for the EFI partition?
Scratch what I wrote. I was thinking 15.0, not TW. :\
The efi partition is the default FAT.
FWIW - further experimentation shows that keeping the EFI partition out of the RAID gives a good install.
The problem is that, if at all possible, I want the EFI partition to be mirrored in the array so that if the first drive goes bad, I can still boot from the second drive until the first is replaced and rebuilt.
So either it’s possible to mirror the EFI partition and I’m doing it wrong, or it isn’t and Yast shouldn’t let me place the EFI partition in a RAID array.
Again, any and all help is greatly appreciated.
I keep my /boots and swaps out of my RAIDs. I find it easy enough to “mirror” Grub’s home manually. The ESP partition doesn’t need to be written to very often, much less often than /boot/, which needs writing to infrequently itself.
Well, at least shim-install has some code to deal with MD RAID. So you may want to open bug report.
Note that having single RAID with partitions on top means you have two identical physical disks (same disk and partitions GUIDs). This is very questionable configuration, firmware will address specific partition using its GUID and will not know which one it refers to - so may simply fail to access any. The only configuration where it is safe is when firmware has driver for your MD RAID, which in practice means having firmware assisted RAID (DDF or IMSM metadata in terms of mdadm).
It should be possible to have ESP on MD RAID1 over individual partitions though. I do not like this configuration (it is unsafe), but apparently people insist on having it.
or it isn’t and Yast shouldn’t let me place the EFI partition in a RAID array.
You were in expert mode at which point you were presumed to know what you were doing.