since last update system does not boot any more

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/31/2011 12:14 PM, Michał Piotrowski wrote:
> W dniu 31 marca 2011 18:09 użytkownik Joachim Backes
> <joachim.backes at rhrk.uni-kl.de> napisał:
>> On 03/31/2011 05:50 PM, Michał Piotrowski wrote:
>>>
>>> W dniu 31 marca 2011 17:39 użytkownik Joachim Backes
>>> <joachim.backes at rhrk.uni-kl.de>  napisał:
>>>>
>>>> On 03/31/2011 05:32 PM, Michał Piotrowski wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> 2011/3/31 Matthias Runge<mrunge at matthias-runge.de>:
>>>>>>
>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> Hash: SHA1
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> the subject says all:
>>>>>> Since systemd(?) update an hour ago, my test system does not boot any
>>>>>> more. removing "rhgb quiet" from kernel command line shows
>>>>>> Failed to load SELINUX policy
>>>>>> Failed to set security context... for /run: invalid argument
>>>>>> Failed to set ... for /sys: Invalid argument
>>>>>> Failed to set ... for /sys: Invalid argument
>>>>>> Failed to mount /sys/fs/cgroup/systemd: No sich file or directory
>>>>>>
>>>>>> Did someone else see this? How to repair such a broken system?
>>>>>
>>>>> Problem of the same category here
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=692573
>>>>>
>>>>> I need to find out how to boot into emergency... solution should be
>>>>> simple - systemd downgrade
>>>>
>>>> Or boot with "selinux=0"
>>>
>>> I have not tried this, because I don't have SELinux installed - I
>>> disabled it after installation and later I removed selinux-policy
>>> package. It appears however that SELinux works without selinux-policy
>>> package and /etc/sysconfig/selinux file disappeared... wtf?
>>> Thanks for the hint. You've saved me several hours searching to solve
>>> this problem. I never imagined that something that is not installed
>>> can be the source of the problem :)
>>
>> I had the same problem : selinux=disabled in /etc/selinux/config,
>> nevertheless SElinux problems during boot.
>>
>> But selinux=0 helped!
> 
> Good to know that it works this way not only on my system. I think
> that Daniel Walsh might want to know about this phenomen.
> 
>>
>>>
>>>>
>>>> --
>>>> Joachim Backes<joachim.backes at rhrk.uni-kl.de>
>>>>
>>>> http://www.rhrk.uni-kl.de/~backes
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> --
>> Joachim Backes <joachim.backes at rhrk.uni-kl.de>
>>
>> http://www.rhrk.uni-kl.de/~backes
>>
>>
> 
> 
> 
Well if you don't have /etc/selinux/config then booting without
selinux=0 will cause the system to crash.  If you want to disable
SELinux you need to tell the system by settingup /etc/selinux/config.

If the system is blowing up with /etc/selinux/config and the line

SELINUX=disabled

Then that would be a new bug.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk2UqU8ACgkQrlYvE4MpobMiWQCgi1lHpSbBwzybYVzS5TGyNbEP
mbkAoOEH8CLmNb/nG0JcAYO12mxB50dc
=r+Si
-----END PGP SIGNATURE-----