Starting Dracut Emergency Shell -- Warning /dev/md126 does not exist.

[linuxandos2]

Describe the bug A clear and concise description of what the error is.

Distribution used Which distribution was this behaviour seen in?

Dracut version Which dracut version was this behaviour seen in?

Init system Which init system is being used?

To Reproduce Steps or code to reproduce the behavior.

Expected behavior A clear and concise description of what you expected to happen.

Additional context Add any other context you like about the problem here.

[linuxandos2]

During boot system hangs on the Dracut Emergency Shell. system: motherbord Z10-PE-D16 WS whit 2 xeon's boot from LSI (fakeroot). / and /boot on LSI raid

Starting Dracut Emergency Shell -- Warning /dev/md126 does not exist.

gentoo linux

dracut-055

systemd

boot the system

Dracut should see the raiddrive and go further.

enabled raid in bios. jumper on motherboard: LSI created and initialized a raid1 on 2 SSD's of 500 GB booted old system from nonraid SSD partition raid /dev/md125 synced successfully installed systemd gentoo on /dev/md125 copied config from old system to /usr/src/linux/.config in new system. created kernel with
genkernel --lvm --mdadm --menuconfig all --makeopts=-j40 --oldconfig

dracut with dracut.conf

hostonly="yes"use_fstab="yes"add_dracutmodules+=" dm mdraid "#omit_dracutmodules+=" systemd systemd-bootchard systemd-networkd "stdloglvl="3"logfile="/var/log/dracut.log" rdsosreport.txt cat: /proc/mdstat: No such file or directory

then do: modprobe md-mod

cat /proc/mdstat gives:

Personalties: unused devices: <none>

mdadm --assemble --scan alot of output

cat /proc/mdstat gives:

Personalties: [raid]md125 : active (auto-red-only) raid1 sde[1] sdf[0] md126 : inactve sde[1] (S) sdf[0] (S)             216478 blocks super external:ddf md127 : active raid1 sdb[0] sda[2]             9766305792 blocks super 1.2 [2/2] [UU]             bitmap 0/73 pages [0KB] , 65536KB chunk

rdosreport.txt:

[linuxandos2]

rdsosreport.txt

[linuxandos2]

RD SOS Report with rd.debug rdsosreport.txt

[linuxandos2]

after loading md-mod and assembling raid: pressing 'ctrl d' lets the system boot successfully.

cloned now my production partition on the raid drive: same behavior.