Hide Forgot
Description of problem: [ 21.753343] audit: type=1400 audit(1455208080.520:51): avc: denied { read } for pid=521 comm="systemd-gpt-aut" name="mmcblk0" dev="devtmpfs" ino=14122 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:removable_device_t:s0 tclass=blk_file permissive=0 [ 21.790570] audit: type=1300 audit(1455208080.520:51): arch=40000028 syscall=5 per=800000 success=no exit=-13 a0=7fec6648 a1=a0000 a2=0 a3=0 items=0 ppid=520 pid=521 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-gpt-aut" exe="/usr/lib/systemd/system-generators/systemd-gpt-auto-generator" subj=system_u:system_r:init_t:s0 key=(null) [ 21.847001] audit: type=1327 audit(1455208080.520:51): proctitle=2F7573722F6C69622F73797374656D642F73797374656D2D67656E657261746F72732F73797374656D642D6770742D6175746F2D67656E657261746F72002F72756E2F73797374656D642F67656E657261746F72002F72756E2F73797374656D642F67656E657261746F722E6561726C79002F72756E2F73797374656D642F67 [ 21.893986] systemd-gpt-auto-generator[521]: /dev/mmcblk0: failed to allocate prober: Permission denied Version-Release number of selected component (if applicable): systemd-229-5.fc24.armv7hl.rpm How reproducible: Every boot Steps to Reproduce: 1. 2. 3. Actual results: Expected results: No permission denied on /dev/mmcblk0 Additional info: Identified this bug while trying to find why /dev/sda1 would not mount at boot. After writing image Fedora-Minimal-armhfp-24-20160308.0-sda.raw.xz and prior to first boot I added uuiD=9b355acf-3437-4aef-b7f5-7a7d148cfc1f /home ext4 defaults,noatime,discard 1 1 to /etc/fstab. The system would only boot to emergency/service mode. Commenting out uuiD=9b355acf-3437-4aef-b7f5-7a7d148cfc1f /home ext4 defaults,noatime,discard 1 1 allowed the system to boot. Note my mistake uuiD instead of UUID in fstab correcting this allowed the system to boot and mount the partition. Would there be any way of error checking for lowercase on "UUID" and displaying a reason for entering emergency/service mode.
Created attachment 1134590 [details] dmesg
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.