This fix caused a regression in our Dracut-based boot setup.
Since this patch was incorporated (237-3ubuntu10.17), some of several of the (PC-type) models we provide to our customers that tend to have "slow I/O", no longer boot because Dracut times out waiting for the root file system to come online because the systemd-crypt@ service can no longer be started.
We are currently using a build of this source package that doesn't include this patch to fix this temporarily.
This fix caused a regression in our Dracut-based boot setup.
Since this patch was incorporated (237-3ubuntu10.17), some of several of the (PC-type) models we provide to our customers that tend to have "slow I/O", no longer boot because Dracut times out waiting for the root file system to come online because the systemd-crypt@ service can no longer be started.
We are currently using a build of this source package that doesn't include this patch to fix this temporarily.
I have filed a bug eport at Systemd's GitHub too, this contains more information: /github. com/systemd/ systemd/ issues/ 12371.
https:/