On Sun, Jan 27, 2013 at 11:07 AM, Paul Smith <phhs80@xxxxxxxxx> wrote: >>> Welcome to emergency mode. Use "systemctl default" or ^D to enter default >>> mode. >>> Give root password for maintenance >>> (or type Control-D to continue) >>> sulogin: /root: change directory failed: Permission denied >> >> Thank you. Whenever I see a question like that with no explanation I get >> suspicious that somebody's trying to be a cargo cult sysadmin, trying a >> drastic "solution" that they don't understand because "it worked ten years >> ago." >> >> You might try booting from a LiveCD, chrooting and running restorecon on >> /root. And, while I'm thinking about it, why does your boot process need to >> log in as root? Is this something normal that I've never noticed, or >> something odd? > > Thanks, Joe. I do not know why it tries to login as root -- my > installation is merely a F18 clean installation. I strongly believe > that the problem I am experiencing is being caused by the new selinux > update. > > Is there some way of disabling selinux in the emergency mode and > getting the machine booting without selinux active? By running journalctl, I got the following: kernel: ata1.00 exception emask 0x0 SAct 0x0 action 0x0 kernel: ata1.00: BMDMA stat 0x24 kernel: ata1.00: failed command: READ DMA EXT Any ideas? Paul -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
