Bug 1573692

Summary: Unable to fix SELinux security context of /run/rootfs base: Permission Denied Fedora 28 Install
Product: [Fedora] Fedora Reporter: Jason Scalia <jscalia>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 28CC: anaconda-maint-list, jan.public, jonathan, kellin, vanmeeuwen+fedora, v.podzimek+fedora, vponcova, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-07 17:21:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of error none

Description Jason Scalia 2018-05-02 02:50:05 UTC
Created attachment 1429636 [details]
screenshot of error

Description of problem:

When booting off a flash drive created with the Fedora Media Writer on Lenovo ThinkPad T530, I receive:


Unable to fix SELinux security context of /run/rootfs base: Permission Denied

The system then ceases to boot any further. I have tried multiple times, with the Workstation release and the XFCE spin with the same results.

Version-Release number of selected component (if applicable):

Unsure

How reproducible:

Every time.

Steps to Reproduce:
1.Boot Fedora 28 installer off of a flash drive on a T530 system. 
2.Select the option to start the installation from the text menu 


Actual results:

Error appears

Expected results:

Anaconda should load up so a user can proceed with the install process

Additional info:

I will attach a screenshot of the error and preceding messages.

Comment 1 Jason Scalia 2018-05-07 17:21:40 UTC
This may be buggy EFI/hardware, closing this out

Comment 2 Jan Vlug 2018-07-02 21:50:07 UTC
I have a similar error on a brand new laptop. Did you solve this problems somehow?