[Bug 2013082] Re: EFI boot does not detect RAID.

[geole0]

Good morning.

Thank you for your interest in my particular problem.
Here is the initial situation that I prepared:
 - A FAT32 partition with ESP flag.
 - A Raid 10.
I run the installation media.
I add the mdadm application.
I can then launch the installation using the "something else" option.
I chose the FAT32 partition for the point of /boot/efi
then the raids for the mount point /.
The whole installation is going well.
But grub installation fails in grub installation.

No problem: To fix: I chroot and run the grub install. Maybe not exactly as it should.
But the EFI boot structure is populated and the configuration file clearly indicates  that the next step is to access a RAIDS structure.
But after the repair, the boot crashes. My analysis is that the raids is not activated.
My knowledge is too weak to know if it is shimx64.EFI which should activate it or grubx64.efi
Or ?

My correction is then to make an additional EXT4 partition intended for the boot files.
 After this correction the grub efi then points to an EXT4 boot partition and the grub menu can be displayed and I can work with the installed ubuntu in a raid.
My conclusion would be that it was the second grub that activated the raid and not the first.

So I find that there is something inconsistent.

I went one step further and transferred all the boot software from the EXT4 partition to the FAT32 partition. I made some adjustments. ( /boot/EFI not /boot/efi/EFI).
Everything boots fine. However, the choice of installation by the "something else" method does not make it possible to choose the same FAT32 partition for the mount points /boot and /boot/efi
Or there is a little trick that unfortunately I did not see.

Note 1: A standard installation in ZFS has only one boot partition in FAT32 which contains the two structures. So it may be possible.
 
Note2: Some time ago I tried the ubuntu server installer with version 22.04.1. It crashed during disk detection in the process. I tried the others versions 18.04, 20.04, and 22.10.Same punishment. I made a bug report which remains unanswered.
I just tried with the server version 22.04.2 (later tried 23.04) and same incident.
This is why I decided to use the DESKTOP computer version.

For more details, French links
For my actual installation https://forum.ubuntu-fr.org/viewtopic.php?id=2078473
For a concepts  raids with desktop computer installer https://doc.ubuntu-fr.org/tutoriel/installation_raid_efi
For  the bug https://bugs.launchpad.net/subiquity/+bug/1997473

Thank you again for looking into this context.
 (It's a google translation)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/2013082

Title:
  EFI boot does not detect RAID.

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu 22.04.2 in a raids structure.
  The grub.cfg files seem fine.

  Content of EFI grub.cfg is

  search.fs_uuid b9c1881f-a0b5-4fe3-b5ea-eb3d4567cfec root mduuid/d9442342aaf72e055793a60e5ed333e4 
  set prefix=($root)'/boot/grub'
  configfile $prefix/grub.cfg

  
  The boot crashes.
  But a can do this command
  mdadm --examine --scan
  The response is
  mdadm no device listed in /etc/mdadm/mdadm.conf

  
  I suspect that the EFI part does not know how to correctly assemble the RAID because during the 

  I don't know how to transmit the crash at this precise moment.

  The workaround found is to make a standard EXT4 partition dedicated to
  booting. However, that seems abnormal to me then the EFI part proposes
  to boot directly on the RAID if it is not possible.

  Thank you for doing what is necessary to have something coherent.
  Good day.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.3-0ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 28 14:58:24 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2013082/+subscriptions