So the reason this doesn't work is that the udev data for the container,
/dev/md/imsm0, does not contain the keys we look for to work out which
devices are part of it. We expect to find keys called things like
MD_DEVICE_dev_sda_DEV but they are not there. There is
UDISKS_MD_DEVICE_dev_sda_DEV though and this is very strange because the
code to produce the MD_DEVICE and UDISKS_MD_DEVICE keys is essentially
the same:
IMPORT{program}="BINDIR/mdadm --detail --export $devnode"
SUBSYSTEM=="block", KERNEL=="md*", ENV{DEVTYPE}!="partition",
IMPORT{program}="/bin/sh -c '/sbin/mdadm --detail --export $tempnode |
/bin/sed s/^MD_/UDISKS_MD_/g'"
I don't know why one use tempnode and one devnode -- maybe that's
significant? Or maybe it's a race where the mdadm rules run before the
devices is really ready or something. Does this happen every time?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960392
Title:
Ubuntu server 22.04 installation crash with intel VROC sata raid
Status in subiquity:
New
Status in linux package in Ubuntu:
Invalid
Bug description:
Reproduce steps:
1.Setup raid 0 with 2 sata disks and intel VROC SATA controller.
2.Install Ubuntu server 22.04 with the latest image.
3.It crash with error "devices or container for raid must be specified"
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1960392/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
