Hi Mitchell, I have made a big discovery. On 20.04 I believe `kpartx` is being
called by "/usr/lib/udev/rules.d/97-dmraid.rules", the line we care about being:
```
ENV{DM_STATE}=="ACTIVE", ENV{DM_UUID}=="DMRAID-*", \
RUN+="/sbin/kpartx -a /dev/$kernel"
```
This requires there to be "DM_STATE" set to "ACTIVE", which is true on my 20.04
setup. However, the "DM_STATE" is notably absent on 24.04.
I figured this out by adding `RUN+="/my_udev_logger.sh` just above the line on
both systems. The script essentially just prints the env and appends it to a
log file.
Now just to figure out why it is absent.
My first theory is "95-kpartx.rules" which diffed from 20.04 to 24.04 has this
change:
```
-# This is a temporary hack until Debian's dmsetup properly supports "dmsetup
-# export". For more information see: #434241, #487881, #493078
-IMPORT{program}="dmsetup_env %M %m"
+ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", GOTO="kpartx_end"
```
Could it have been from `dmsetup_env` and when removing the bodge no one added
a replacement?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075442
Title:
RAID partitions not auto detected at boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/2075442/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
