After an update of my Rawhide system yesterday, it refused to boot. A change to /etc/selinux/config to set SELINUX=permissive avoids the problem. This may be a one-off situation due to my particular sequence of updates, unless others have similar troubles. The system log for the failing boot has the following, which may not be relevant, but is the only selinux data that apears remarkable: Jan 25 22:10:12 xps13 systemd[1]: Reached target Local File Systems (Pre). Jan 25 22:10:12 xps13 systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped. Jan 25 22:10:12 xps13 systemd[1]: Starting File System Check on /dev/disk/by-uuid/543acebd-af86-46a7-9a29-d6cef33a1c95... Jan 25 22:10:12 xps13 systemd[1]: Starting File System Check on /dev/disk/by-uuid/6A06-AE8A... Jan 25 22:10:12 xps13 systemd-fsck[912]: /dev/nvme0n1p7: recovering journal Jan 25 22:10:12 xps13 systemd-fsck[912]: /dev/nvme0n1p7: clean, 105/128016 files, 261937/512000 blocks Jan 25 22:10:12 xps13 systemd[1]: Started File System Check on /dev/disk/by-uuid/543acebd-af86-46a7-9a29-d6cef33a1c95. Jan 25 22:10:12 xps13 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-543acebd\x2daf86\x2d46a7\x2d9a29\x2dd6cef33a1c95 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 25 22:10:12 xps13 systemd[1]: Mounting /boot... Jan 25 22:10:12 xps13 kernel: EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Opts: (null) Jan 25 22:10:12 xps13 kernel: ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff) Jan 25 22:10:12 xps13 systemd[1]: Mounted /boot. Jan 25 22:10:12 xps13 systemd-fsck[913]: fsck.fat 4.1 (2017-01-24) Jan 25 22:10:12 xps13 systemd-fsck[913]: 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Jan 25 22:10:12 xps13 systemd-fsck[913]: Automatically removing dirty bit. Jan 25 22:10:12 xps13 systemd-fsck[913]: Performing changes. Jan 25 22:10:12 xps13 systemd-fsck[913]: /dev/nvme0n1p1: 430 files, 18932/126976 clusters Jan 25 22:10:12 xps13 systemd[1]: Started File System Check on /dev/disk/by-uuid/6A06-AE8A. Jan 25 22:10:12 xps13 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-6A06\x2dAE8A comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jan 25 22:10:12 xps13 systemd[1]: Mounting /boot/efi... Jan 25 22:10:12 xps13 mount[917]: mount: /boot/efi: unknown filesystem type 'vfat'. Jan 25 22:10:12 xps13 systemd[1]: boot-efi.mount: Mount process exited, code=exited, status=32/n/a Jan 25 22:10:12 xps13 systemd[1]: boot-efi.mount: Failed with result 'exit-code'. Jan 25 22:10:12 xps13 systemd[1]: Failed to mount /boot/efi. Jan 25 22:10:12 xps13 systemd[1]: Dependency failed for Local File Systems. Jan 25 22:10:12 xps13 systemd[1]: Dependency failed for Mark the need to relabel after reboot. Jan 25 22:10:12 xps13 systemd[1]: selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with result 'dependency'. Jan 25 22:10:12 xps13 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Jan 25 22:10:12 xps13 systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Jan 25 22:10:12 xps13 systemd[1]: Reached target Timers. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx
