Booting gets in emergency mode

Paul Smith phhs80 at gmail.com
Sat Jan 26 13:36:18 UTC 2013


On Sat, Jan 26, 2013 at 1:25 PM, Richard Sewill <rsewill at gmail.com> wrote:
>> After doing the last F18 updates, I cannot boot my machine. I get in
>> the emergency mode and the message:
>>
>> sulogin: /root: change directory failed: Permission denied.
>>
>> Any ideas?
>
> I don't know if you and I have a similar problem.
>
> I did a format/install on / of F18 and have no problems with the /
> partition.
> The / partition is ext4.
>
> I did not format my /home partition.  It is still ext3.  I am having
> problems with it.
>
> rsewill at localhost:~ <3:14> $ df -T
> Filesystem     Type     1K-blocks     Used Available Use% Mounted on
> devtmpfs       devtmpfs    465028        0    465028   0% /dev
> tmpfs          tmpfs       476448     1436    475012   1% /dev/shm
> tmpfs          tmpfs       476448     3024    473424   1% /run
> tmpfs          tmpfs       476448        0    476448   0% /sys/fs/cgroup
> /dev/sda2      ext4      28221604  8970576  17817428  34% /
> tmpfs          tmpfs       476448        8    476440   1% /tmp
> /dev/sda6      ext3      75795940 31873248  40072436  45% /home
> rsewill at localhost:~ <3:15> $
>
> It seems my /home partition needs fsck repair every 5th or 6th time I
> reboot.
>
> I have to give the root password at the prompt and do
> fsck -y /home
>
> The problem on the /home partition seems to vary.
> Last time the problem was inodes multiply used in the chrome browser cache
> directory.
>
> I guess I would ask if any of your partitions are in need of fsck repair.
>
> Perhaps you can remove quiet mode and the Redhat banner from the grub2 boot
> options during boot (I think you have to figure out how to remove the quiet
> param and rhgb param from the line that start linux /boot/vmlinuz...--could
> someone correct me on this please and explain better how to do this please)
> and get messages indicating the nature of the boot problem.

Thanks, Richard. I believe that the cause is the new selinux update,
and it may be related to the following bug:

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=865399

Paul


More information about the users mailing list