Red Hat Bugzilla – Bug 481700
no selinux targeted policy file after fresh install of Fedora 10 x64
Last modified: 2009-06-18 14:21:04 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install from Fedora-10-x86_64-DVD.iso (downloaded 1/25/2009 from torrent)
2. Select desktop, developer & web software. Customize later.
3. Select all three repositories: media, fedora, fedora updates.
5. Type <esc> <esc> to display messages
Fedora displays "fedora 10" progress bar, then stops.
<esc> <esc> reveals:
selinux: could not open policy file <= /etc/selinux/targeted/policy/policy.23: No such file or directory
Unable to load SELinux policy (No such file or directory). Halting now."
Expected to boot
This is a brand new fresh install. Nothing in log. System responds to ^C by going down. Media passed self-test, did not check the sha1sum, assume that torrent did that. Confirmed policy file is missing.
Did you use a kickstart file to install from?
Created attachment 330450 [details]
File checksum errors resulting in packages not being installed.
No, I did not use a kickstart file; Normal interactive gui install, clicked box to accept updated packages from repository.
Seems to be related to packages that were not installed due to checksum errors on files. Which is weird since the DVD passed media test. Perhaps there were file errors during the network transfer, or the checksum compared the files to the original MD5SUM? I don't know.
Add SELINUX=0 to grub. (boot continues, X hangs.)
Login as root on console.
yum update; yum upgrade. (now SELINUX works, get the login screen)
Manually add user so that I can gui login. (login, but gnome doesn't start)
Install KDE (neither gnome nor KDE will start)
grep error /root/install.log | (manually) yum whatprovides | (manually) yum install
Now most everything except logout and user switching is working. And the Broadcom wireless is not working, but that is another issue.
error: unpacking of archive failed on file /usr/sbin/open_init_pty;497e51fa: cpi
o: MD5 sum mismatch
This caused all of the problems, I have no idea why.
Please attach /var/log/anaconda.log and /var/log/anaconda.syslog to this bug report. Random errors like this sound like I/O errors when reading the disc, possibly caused by a corrupt download or burn. I won't know fur sure until looking at those log files.