Comment 2 for bug 2060695

The RAID is on partitions, but there is no LVM involved. The layout was set up through the 24.04 server installer with custom storage layout, selecting both disks as boot disks, and then using all of their space as a single partition for the software RAID. The software RAID itself is unpartitioned.

/proc/mdstat:
md0 : active raid1 vdb2[1] vda2[0]
      41906176 blocks super 1.2 [2/2] [UU]

/proc/partitions:
 253 0 41943040 vda
 253 1 1024 vda1
 253 2 41939968 vda2
 253 16 41943040 vdb
 253 17 1024 vdb1
 253 18 41939968 vdb2
   9 0 41906176 md0

/proc/self/mounts of the root filesystem:
/dev/md0 / ext4 rw,relatime 0 0

I get this test VM into a state with a post-install grub2 update because I typically work by going through the server installer once, snapshotting the result, and then working from the snapshot to test our post-install actions, which involve updating all packages. This grub-pc problem has happened before several times and previously I've made it go away by rebuilding the initial install using the current daily server ISO. This time I'm reporting a bug.