Bug#962844: marked as done (mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs)

[Debian Bug Tracking System]

Your message dated Sun, 29 Jan 2023 10:26:47 +0100
with message-id <1674983...@msgid.manchmal.in-ulm.de>
and subject line Re: Bug#962844: mdadm: Assembling RAID using IMSM in initrd 
fails due to lack of module efivarfs
has caused the Debian Bug report #962844,
regarding mdadm: Assembling RAID using IMSM in initrd fails due to lack of  
module efivarfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
962844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

--- Begin Message ---

Package: mdadm
Version: 4.1-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I created a RAID 5 volume over 4 disks using the BIOS support for Intel
RST. Install proceeded correctly, however after a reboot in to the
installed system, the root device was not found. Investigation in the
init shell found that the mdamd device had not been assembled correctly

The following error was encountered when looking for imsm capabilies on
the controller. 

        mdadm --detail-platform
        mdadm: imsm capabilities not found for controller: 
/sys/devices/pci0000:00/0000:00:1f.2 (type SATA)

I found that this occurred when mdadm could not read from 
/sys/firmware/efi/efivars/ due to it not being mounted. The efivarfs module was 
not found in the initrd

To resolve this, I booted in to a rescue CD and added efivarfs and
efivars to /etc/initramfs.conf/modules and ran an update-initramfs

This allowed the system to boot correctly

I suggest that mdadm ensures that these modules are added to the initrd
when the RAID array is using IMSM.


-- Package-specific info:
--- mdadm.conf
ARRAY metadata=imsm UUID=56bed0cd:2b07c313:c4651474:3a6b990c
ARRAY /dev/md/Volume0 container=56bed0cd:2b07c313:c4651474:3a6b990c member=0 
UUID=d0f942e0:fb69f9d0:bca65978:774a6c88
MAILADDR root

--- /etc/default/mdadm
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] 
[raid10] 
md126 : active raid5 sda[3] sdb[2] sdc[1] sdd[0]
      5567516672 blocks super external:/md127/0 level 5, 64k chunk, algorithm 0 
[4/4] [UUUU]
      
md127 : inactive sdb[3](S) sdd[2](S) sdc[1](S) sda[0](S)
      20804 blocks super external:imsm
       
unused devices: <none>

--- /proc/partitions:
major minor  #blocks  name

   8       48 1953514584 sdd
   8       32 1953514584 sdc
   8       16 1953514584 sdb
   8        0 1953514584 sda
   9      126 5567516672 md126
 259        0     525391 md126p1
 259        1 5533714844 md126p2
 259        2   33276403 md126p3

--- LVM physical volumes:
LVM does not seem to be used.
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs 
(rw,nosuid,relatime,size=16317648k,nr_inodes=4079412,mode=755)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3266568k,mode=755)
/dev/md126p2 on / type ext4 (rw,relatime,errors=remount-ro,stripe=48)
securityfs on /sys/kernel/security type securityfs 
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 
(rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs 
(rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup 
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/perf_event type cgroup 
(rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12482)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
/dev/md126p1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=3266564k,mode=700,uid=1000,gid=1000)

--- initrd.img-4.19.0-9-amd64:
178049 blocks
192ccafcfe38eabf0f5184786764c4a9  ./scripts/local-bottom/mdadm
f3b648ca1c912da30940f0b821b7e9e6  ./scripts/local-block/mdadm
371839b6f84393a2c8d2988933b99f80  ./etc/mdadm/mdadm.conf
d3be82c0f275d6c25b04d388baf9e836  ./etc/modprobe.d/mdadm.conf
5161458238d5de132cad1b31dc0c5309  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/raid0.ko
883f22eb89aff84ff7a1b5b9f60df68b  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/dm-mod.ko
70c94cac4f7843774973587255dd5c16  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/multipath.ko
052d49884d8639a620589f73c7add29c  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/md-mod.ko
6bdc618758cff3b774d4b15cdf57b1ec  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/raid1.ko
3bb445a856077158162f5ce7eb271382  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/raid10.ko
0c6fcac6637faf87f526c2c1b841fa15  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/linear.ko
9291d84f2f243dce6ffe1d8d5c0fab55  
./usr/lib/modules/4.19.0-9-amd64/kernel/drivers/md/raid456.ko
d325a636dd5d9c95289b6653eb1fb070  ./usr/sbin/mdadm

--- initrd's /conf/conf.d/md:
no conf/md file.

--- /proc/modules:
raid10 57344 0 - Live 0xffffffffc0526000
raid1 45056 0 - Live 0xffffffffc0515000
raid0 20480 0 - Live 0xffffffffc043a000
multipath 16384 0 - Live 0xffffffffc0362000
linear 16384 0 - Live 0xffffffffc034b000
raid456 172032 1 - Live 0xffffffffc04e1000
async_raid6_recov 20480 1 raid456, Live 0xffffffffc042a000
async_memcpy 16384 2 raid456,async_raid6_recov, Live 0xffffffffc0425000
async_pq 16384 2 raid456,async_raid6_recov, Live 0xffffffffc0409000
async_xor 16384 3 raid456,async_raid6_recov,async_pq, Live 0xffffffffc03aa000
async_tx 16384 5 raid456,async_raid6_recov,async_memcpy,async_pq,async_xor, 
Live 0xffffffffc03a5000
raid6_pq 122880 3 raid456,async_raid6_recov,async_pq, Live 0xffffffffc0484000
libcrc32c 16384 1 raid456, Live 0xffffffffc02d2000
md_mod 167936 10 raid10,raid1,raid0,multipath,linear,raid456, Live 
0xffffffffc04b7000

--- /var/log/syslog:

--- volume detail:
/dev/sda:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.3.00
    Orig Family : f56adaf5
         Family : f56adaf5
     Generation : 00000024
     Attributes : All supported
           UUID : 56bed0cd:2b07c313:c4651474:3a6b990c
       Checksum : d54cdbbc correct
    MPB Sectors : 2
          Disks : 4
   RAID Devices : 1

  Disk00 Serial : PN2134P6JBEJ5P
          State : active
             Id : 00000000
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

[Volume0]:
           UUID : d0f942e0:fb69f9d0:bca65978:774a6c88
     RAID Level : 5
        Members : 4
          Slots : [UUUU]
    Failed disk : none
      This Slot : 0
    Sector Size : 512
     Array Size : 11135033344 (5309.60 GiB 5701.14 GB)
   Per Dev Size : 3711678216 (1769.87 GiB 1900.38 GB)
  Sector Offset : 0
    Num Stripes : 28997484
     Chunk Size : 64 KiB
       Reserved : 0
  Migrate State : idle
      Map State : normal
    Dirty State : dirty
     RWH Policy : off

  Disk01 Serial : PN2134P6KVEM8X
          State : active
             Id : 00000001
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk02 Serial : PN1134P6K18XEW
          State : active
             Id : 00000002
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk03 Serial : PN2134P6H4X1LP
          State : active
             Id : 00000003
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)
--
/dev/sdb:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.3.00
    Orig Family : f56adaf5
         Family : f56adaf5
     Generation : 00000024
     Attributes : All supported
           UUID : 56bed0cd:2b07c313:c4651474:3a6b990c
       Checksum : d54cdbbc correct
    MPB Sectors : 2
          Disks : 4
   RAID Devices : 1

  Disk01 Serial : PN2134P6KVEM8X
          State : active
             Id : 00000001
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

[Volume0]:
           UUID : d0f942e0:fb69f9d0:bca65978:774a6c88
     RAID Level : 5
        Members : 4
          Slots : [UUUU]
    Failed disk : none
      This Slot : 1
    Sector Size : 512
     Array Size : 11135033344 (5309.60 GiB 5701.14 GB)
   Per Dev Size : 3711678216 (1769.87 GiB 1900.38 GB)
  Sector Offset : 0
    Num Stripes : 28997484
     Chunk Size : 64 KiB
       Reserved : 0
  Migrate State : idle
      Map State : normal
    Dirty State : dirty
     RWH Policy : off

  Disk00 Serial : PN2134P6JBEJ5P
          State : active
             Id : 00000000
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk02 Serial : PN1134P6K18XEW
          State : active
             Id : 00000002
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk03 Serial : PN2134P6H4X1LP
          State : active
             Id : 00000003
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)
--
/dev/sdc:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.3.00
    Orig Family : f56adaf5
         Family : f56adaf5
     Generation : 00000024
     Attributes : All supported
           UUID : 56bed0cd:2b07c313:c4651474:3a6b990c
       Checksum : d54cdbbc correct
    MPB Sectors : 2
          Disks : 4
   RAID Devices : 1

  Disk02 Serial : PN1134P6K18XEW
          State : active
             Id : 00000002
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

[Volume0]:
           UUID : d0f942e0:fb69f9d0:bca65978:774a6c88
     RAID Level : 5
        Members : 4
          Slots : [UUUU]
    Failed disk : none
      This Slot : 2
    Sector Size : 512
     Array Size : 11135033344 (5309.60 GiB 5701.14 GB)
   Per Dev Size : 3711678216 (1769.87 GiB 1900.38 GB)
  Sector Offset : 0
    Num Stripes : 28997484
     Chunk Size : 64 KiB
       Reserved : 0
  Migrate State : idle
      Map State : normal
    Dirty State : dirty
     RWH Policy : off

  Disk00 Serial : PN2134P6JBEJ5P
          State : active
             Id : 00000000
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk01 Serial : PN2134P6KVEM8X
          State : active
             Id : 00000001
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk03 Serial : PN2134P6H4X1LP
          State : active
             Id : 00000003
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)
--
/dev/sdd:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.3.00
    Orig Family : f56adaf5
         Family : f56adaf5
     Generation : 00000024
     Attributes : All supported
           UUID : 56bed0cd:2b07c313:c4651474:3a6b990c
       Checksum : d54cdbbc correct
    MPB Sectors : 2
          Disks : 4
   RAID Devices : 1

  Disk03 Serial : PN2134P6H4X1LP
          State : active
             Id : 00000003
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

[Volume0]:
           UUID : d0f942e0:fb69f9d0:bca65978:774a6c88
     RAID Level : 5
        Members : 4
          Slots : [UUUU]
    Failed disk : none
      This Slot : 3
    Sector Size : 512
     Array Size : 11135033344 (5309.60 GiB 5701.14 GB)
   Per Dev Size : 3711678216 (1769.87 GiB 1900.38 GB)
  Sector Offset : 0
    Num Stripes : 28997484
     Chunk Size : 64 KiB
       Reserved : 0
  Migrate State : idle
      Map State : normal
    Dirty State : dirty
     RWH Policy : off

  Disk00 Serial : PN2134P6JBEJ5P
          State : active
             Id : 00000000
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk01 Serial : PN2134P6KVEM8X
          State : active
             Id : 00000001
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)

  Disk02 Serial : PN1134P6K18XEW
          State : active
             Id : 00000002
    Usable Size : 3907018766 (1863.01 GiB 2000.39 GB)
--

--- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-amd64 
root=UUID=a6808471-700e-404a-bd74-003244762d4d ro

--- grub2:
        linux   /boot/vmlinuz-4.19.0-9-amd64 
root=UUID=a6808471-700e-404a-bd74-003244762d4d ro  quiet
                linux   /boot/vmlinuz-4.19.0-9-amd64 
root=UUID=a6808471-700e-404a-bd74-003244762d4d ro  quiet
                linux   /boot/vmlinuz-4.19.0-9-amd64 
root=UUID=a6808471-700e-404a-bd74-003244762d4d ro single 

--- udev:
ii  udev           241-7~deb10u4 amd64        /dev/ and hotplug management 
daemon
9d7dfcdc58fa54941f8d28f6094a7a5b  /lib/udev/rules.d/01-md-raid-creating.rules
aa83f41de49462d05e446cfc5e14e74b  /lib/udev/rules.d/63-md-raid-arrays.rules
904bb2cce2cfd4a2c94aa957e7968e16  /lib/udev/rules.d/64-md-raid-assembly.rules
ba1d376ca9b7364576f950d06ba18207  
/lib/udev/rules.d/69-md-clustered-confirm-device.rules
745ed418fa58498790836a08c627e1ca  /lib/udev/rules.d/99-systemd.rules

--- /dev:
brw-rw---- 1 root disk   9, 126 Jun 14 18:15 /dev/md126
brw-rw---- 1 root disk 259,   0 Jun 14 18:15 /dev/md126p1
brw-rw---- 1 root disk 259,   1 Jun 14 18:15 /dev/md126p2
brw-rw---- 1 root disk 259,   2 Jun 14 18:15 /dev/md126p3
brw-rw---- 1 root disk   9, 127 Jun 14 18:15 /dev/md127

/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root  9 Jun 14 18:15 ata-HGST_HUS724020ALA640_PN1134P6K18XEW 
-> ../../sdc
lrwxrwxrwx 1 root root  9 Jun 14 18:15 ata-HGST_HUS724020ALA640_PN2134P6H4X1LP 
-> ../../sdd
lrwxrwxrwx 1 root root  9 Jun 14 18:15 ata-HGST_HUS724020ALA640_PN2134P6JBEJ5P 
-> ../../sda
lrwxrwxrwx 1 root root  9 Jun 14 18:15 ata-HGST_HUS724020ALA640_PN2134P6KVEM8X 
-> ../../sdb
lrwxrwxrwx 1 root root 11 Jun 14 18:15 
md-uuid-56bed0cd:2b07c313:c4651474:3a6b990c -> ../../md127
lrwxrwxrwx 1 root root 11 Jun 14 18:15 
md-uuid-d0f942e0:fb69f9d0:bca65978:774a6c88 -> ../../md126
lrwxrwxrwx 1 root root 13 Jun 14 18:15 
md-uuid-d0f942e0:fb69f9d0:bca65978:774a6c88-part1 -> ../../md126p1
lrwxrwxrwx 1 root root 13 Jun 14 18:15 
md-uuid-d0f942e0:fb69f9d0:bca65978:774a6c88-part2 -> ../../md126p2
lrwxrwxrwx 1 root root 13 Jun 14 18:15 
md-uuid-d0f942e0:fb69f9d0:bca65978:774a6c88-part3 -> ../../md126p3
lrwxrwxrwx 1 root root  9 Jun 14 18:15 wwn-0x5000cca22dd0524a -> ../../sdd
lrwxrwxrwx 1 root root  9 Jun 14 18:15 wwn-0x5000cca22de161d9 -> ../../sda
lrwxrwxrwx 1 root root  9 Jun 14 18:15 wwn-0x5000cca22deadc5b -> ../../sdc
lrwxrwxrwx 1 root root  9 Jun 14 18:15 wwn-0x5000cca22df64b4b -> ../../sdb

/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 9 Jun 14 18:15 pci-0000:00:1f.2-ata-1 -> ../../sda
lrwxrwxrwx 1 root root 9 Jun 14 18:15 pci-0000:00:1f.2-ata-2 -> ../../sdb
lrwxrwxrwx 1 root root 9 Jun 14 18:15 pci-0000:00:1f.2-ata-3 -> ../../sdc
lrwxrwxrwx 1 root root 9 Jun 14 18:15 pci-0000:00:1f.2-ata-4 -> ../../sdd

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 13 Jun 14 18:15 35cae70c-d20f-4701-b9e1-de6f5de45d95 -> 
../../md126p3
lrwxrwxrwx 1 root root 13 Jun 14 18:15 FD45-8E8C -> ../../md126p1
lrwxrwxrwx 1 root root 13 Jun 14 18:15 a6808471-700e-404a-bd74-003244762d4d -> 
../../md126p2

/dev/md:
total 0
lrwxrwxrwx 1 root root  8 Jun 14 18:15 Volume0 -> ../md126
lrwxrwxrwx 1 root root 10 Jun 14 18:15 Volume0p1 -> ../md126p1
lrwxrwxrwx 1 root root 10 Jun 14 18:15 Volume0p2 -> ../md126p2
lrwxrwxrwx 1 root root 10 Jun 14 18:15 Volume0p3 -> ../md126p3
lrwxrwxrwx 1 root root  8 Jun 14 18:15 imsm0 -> ../md127

Auto-generated on Mon, 15 Jun 2020 00:06:50 +0100 by mdadm bugscript

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6                  2.28-10
ii  lsb-base               10.2019051400
ii  udev                   241-7~deb10u4

Versions of packages mdadm recommends:
pn  default-mta | mail-transport-agent  <none>
ii  kmod                                26-1

Versions of packages mdadm suggests:
pn  dracut-core  <none>

-- debconf information excluded

--- End Message ---

--- Begin Message ---

user debian-rele...@lists.debian.org
usertags -1 + bsp-2023-01-ch-stcergue
thank you

Alban Browaeys wrote...

> On Sun, 7 Feb 2021 20:32:08 -0800 Felix Lechner

> > Thanks for the reminder! I will probably include efivars in the next
> > couple of days.
>
> You probably want to include efivarfs (efivars is obsolete and removed
> in linux kernel 6). Thus the current patch has no effect on bullseye-
> backports, testing and up.

Looking into the current mdadm packaging:

67-
68:# load efivars for Intel RST IMSM, see Bug#962844
69:force_load efivarfs || true
70-
[ debian/mdadm.initramfs-hook ]

It seems efivarfs is indeed the module being probed, however using the
"efivars" word in the discussion and the descrption may cause some
confusion. That could possibly fixed in another upload, of minor
urgence.

More important, from a technical point of view, the change does the
right thing. So closing as this not a release-critical bug then.

Or I completely misunderstood, please clarify and re-open then.

    Christoph

signature.asc
Description: PGP signature

--- End Message ---