Created attachment 638533 [details] blkid Description of problem: The system hung on a normal shutdown from KDE. Eventually I ctrl+alt+del to restart and the system will not boot. (I fixed this by re-installing Fedora from scratch and now this problem has happened again). How reproducible: Always Steps to Reproduce: 1. Select any Fedora kernel from the boot loader. Actual results: Cannot open font file True Cannot find init! Please check to make sure you passed a valid root filesystem! dracut Warning: Dropping to debug shell. Expected results: System boot like normal. Additional info: Although it probably isn't related, the problem seemed to start on the first shutdown after installing PHP pecl xdebug (although I was still re-installing a lot of other things at the time). uname -a: Linux (none) 3.6.3-1.fc17.x86_64 #1 SMP Mon Oct 22 15:32:35 UTC 2012 x86_64 x86_64 x86_64 x86_64 GNU/Linux /dev/sda1 boot ext4 /dev/sda2 swap /dev/sda3 / ext4 /dev/sda5 /home ext4 I ran fsck on /dev/sda1,3,5. /dev/sda3 said it was mounted. I couldn't work out how to unmount it. I forced it with -f even though it spoke about SEVERE filesystem damage. All partitions seemed to be clean. Please let me know of any further information I could provide to help fix this.
Created attachment 638540 [details] dmesg output
The boot entry from the menu (I typed this by hand, hopefully there are no mistakes) is: linux /vmlinuz-3.6.3-1.fc17.x86_64 root=UUID=080f2a5d-<snip>93bc ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet I added rd.debug after the "ro" on that line and booted it. I am attaching the output in /run/initramfs/init.log and some basic ls -l entries of the files the /init script seems to be looking for. It seems that the files don't have execute permissions on them which could be causing problems? I haven't done anything that I would expect to affect this. The system used to boot fine.
Created attachment 639132 [details] /run/initramfs/init.log with rd.debug
Created attachment 639133 [details] Files from the dracut debug shell
After waiting for a month for expert advice I decided to try to hack the system back together. I booted in with kernel mode "rw" instead of "ro". Then I was able to make /sysroot/usr/lib/systemd/systemd executable with chmod +x. The next reboot proceeded much further, but there was a myriad of services not being executed by systemd. I decided that the best option for me would be to re-install the system. Since then I have been able to install the software that I wanted without problem. I am unsure of the exact circumstances as to why my system became unusable for me (twice), but I will close this bug now as it is unlikely to be useful for anyone. Closing as WORKSFORME because thankfully I can't reproduce it a third time.