Public bug reported:

Setting up grub-efi-amd64-signed (1.202.5+2.12-1ubuntu7.3) ...
mount: /var/lib/grub/esp: unknown filesystem type 'linux_raid_member'.
       dmesg(1) may have more information after failed mount system call.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess 
returned error exit status 32


hi,

  the package was allways ok but seems there is an incompatible change
now, on my systems the /efi partition is installed as mdadm raid:

/dev/md/ESP:
           Version : 1.0
     Creation Time : Sun Mar 16 18:23:15 2025
        Raid Level : raid1
        Array Size : 273344 (266.94 MiB 279.90 MB)
     Used Dev Size : 273344 (266.94 MiB 279.90 MB)
      Raid Devices : 4
     Total Devices : 4
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

[~]: grep efi /proc/mounts 
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
/dev/md125 /efi vfat 
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
 0 0


 this works very well to use mdadm with EFI that is incapable of
understanding raid systems.

  It seems ubuntu now refuse to simply update the files of the package
and require that the partitions are plain partition and that grub is now
in charge of updating the file on all partition i guess.

  i dont see any reason for that incompatible change.

best regards,
Ghislain.

** Affects: grub2-signed (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  grub refuse to upgrade  unknown filesystem type 'linux_raid_member'

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


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to