Hey everyone, For reference, a bug report has been filed at https://bugzilla.redhat.com/show_bug.cgi?id=1941335 I just wanted to give a heads up that I came across a bug today that renders Fedora 33 systems unbootable, even after a clean install. If systemd starts raid-check.timer, it gets stuck in what looks like a busy loop, is unable to start new services, systemctl stops responding to commands, and we end up with a lot of zombie processes. The problem is that raid-check.timer (a part of mdadm) is part of the default boot process in Fedora Workstation, and the bug also exists on the version of systemd installed with F33 GA. I've tested on four different systems, each running F33 installed in different ways (some upgrades, some fresh F33 installs), and on each of them, starting raid-check.timer makes the system unusable. There is a workaround: disabling raid-check.timer, but, if you can't boot due to this bug, you have to boot into single-user mode (which requires a root password to have been set). Manually experimenting with dates seems to indicate that this bug is triggered if the current date is after March 3rd, 2021 at 1:00AM, which is why we haven't seen this bug before today. I'm really hoping that I'm missing something obvious here, but I fear that a good chunk of our Fedora systems will be unbootable if they're rebooted without disabling raid-check.timer. Jonathan _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
