Cannot get Fedora 16 to boot past a screen with the following information on it.

[UncleTed420]

Fedora will act like it is booting normally, then it will go to a black screen with a multi blue and white animated stripe across the bottom with Fedora 16 on the right side, then before the stripe moves all the way across the screen it will popup to a black screen with the following message:

"Please enter passphrase for disk Hitachi_HTS545032B9A300 (luks-76aec453-d13d-4be1-b328-7595dce3e8a4) on /home!:

If I enter my password, this is what loads:

Started LSB: Starts and Stops login iSCSI daemon.
Started Open-FCoe Inititator.
Starting LSB: Start and stops login and scanning of iSCSI devices....
Started Permit User Sessions
Starting Forward Password Requests to Wall...
Stopped Dispatch Password Requests to Console
Stopping Forward Password Requests to Plymouth...
Stopped Forward Password Requests to Plymouth
Started Forward Password Requests to Wall
Started LSB: VirtualBox Linux kernel module
Starting LSB: VirtualBox web service API...
Starting LSB: VirtualBox balloon control daemon...
Started The Apache HTTP Server (prefork MPM)
Started LSB: VirtualBox web service API
Started LSB: VirtualBox Balloon control daemon
Failed to start LSB: Builds and install new kmods from akmod packages.
See 'systemctl status akmods.service' for details
Started LSB: Starts and stops login and scanning of iSCSI devices.
Starting SYSV: Late init script for live image....
Started SYSV: Late init script for live image.
Starting Display Manager...
Started Display Manager
Starting Sendmail Mail Transport Client...
Starting Sendmail Mail Transport Agent...


All have [ OK ] next to them, except for "Failed to start SLB: Builds and install new kmods from akmod packages" and next to it it has [ FAILED ].

If I don't enter a passphrase, the following pops up:

"Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode. Give root password for maintenance (or type Control-D to continue)


This is as far as Fedora 16 will boot for me. From a powered off state, it will start booting up and it will get to a black screen with this info on it and thats as far as it will boot.

I am fairly new to Linux and this is my first time using / installing Fedora, but so far other than this little mishap I am loving it.

So any help that you can give a Noob on how to fix this will be greatly appreciated.

Thank You,
UncleTed420

[glennzo]

More to bump the post than anything else ... Just thinking out loud.
Is this an existing install or an install in progress?
Why are the VirtualBox modules being loaded?
The akmods. Are they there for your graphics drivers?
Could this be a graphics issue?
Did these problems occur after a kernel update?

[UncleTed420]

More to bump the post than anything else ... Just thinking out loud.
Is this an existing install or an install in progress?
Why are the VirtualBox modules being loaded?
The akmods. Are they there for your graphics drivers?
Could this be a graphics issue?
Did these problems occur after a kernel update?

More to bump the post than anything else ... Just thinking out loud.

Not sure what that means, sorry I am a noob with Linux


Is this an existing install or an install in progress?

Existing Install


Why are the VirtualBox modules being loaded?

Not sure, did install VirtualBox in order to run XP Pro in a virtual machine (haven't installed XP yet in VirtualBox).


The akmods. Are they there for your graphics drivers?

Not sure what an akmod is and I honestly have no idea if they are for the graphics drivers or not.


Could this be a graphics issue?

I honestly don't know, it could be, I have heard of issues with Nvidia graphics cards and Fedora, but the first few times it did boot fine.


Did these problems occur after a kernel update?
Also not real sure about this one, I did update Fedora after install, but it worked fine the first few times I booted up.

[nonamedotc]

Just a thought - Is it possible that your root partition is corrupted. Try running fsck when you get to the emergency mode and see if that throws any error.

fsck /dev/sdan

Replace 'n' with root partition identifier.

The akmods. Are they there for your graphics drivers?

Not sure what an akmod is and I honestly have no idea if they are for the graphics drivers or not.

Could this be a graphics issue?

I honestly don't know, it could be, I have heard of issues with Nvidia graphics cards and Fedora, but the first few times it did boot fine.

The akmod could be for graphics card drivers - Did you install any drivers (Nvidia/ATI) drivers for these? These could be one of the sources - and I believe, one of the more common ones!

[UncleTed420]

Just a thought - Is it possible that your root partition is corrupted. Try running fsck when you get to the emergency mode and see if that throws any error.

fsck /dev/sdan

Replace 'n' with root partition identifier.

Tried that on sda1&2 and recieved this message "WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you really want to continue?

I chose no both times.

when I ran it on sda3 this is the info that came up:

"fshck from util-linux 2.20.1
fsck: fsck.crypto_LUKS: not found
fsck: error2 while executing fsck.crypto_LUKS for /dev/sda3

[nonamedotc]

Oh yeah! My mistake - you have to decrypt and "mount" the encrypted partition using cryptsetup first to run on that ... But, I was suspecting the root partition - sda3 is probably your home (right?) .... Let me search a little and see if I can find some information ....

[UncleTed420]

Oh yeah! My mistake - you have to decrypt and "mount" the encrypted partition using cryptsetup first to run on that ... But, I was suspecting the root partition - sda3 is probably your home (right?) .... Let me search a little and see if I can find some information ....

I had found a guide on some site that gave step by step instructions on how to install and on said site (i forgot which one, found it on google), it said set up a boot partition first, then swap space, then root partiton and finally the home partiton, so that was the way I did it.

[nonamedotc]

Yeah. That's kind of what I have (and probably many more people) and there is nothing wrong with your partitioning scheme ....

[RHamel]

Seems like a video problem to me. If you use your password, and it gets to the end of the messages do you get a command line if you do a CTL-ALT-F2?

[UncleTed420]

Seems like a video problem to me. If you use your password, and it gets to the end of the messages do you get a command line if you do a CTL-ALT-F2?

Whenever I get to the black screen with the message ""Please enter passphrase for disk Hitachi_HTS545032B9A300 (luks-76aec453-d13d-4be1-b328-7595dce3e8a4) on /home!:" if I don't push anything, after roughly 30 - 60 seconds it will change to a screen that says

"Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.
Give root password for maintenance
(or type Control-D to continue):"

At which point I type in my password and I get a root command line.

[Dan]

Kinda sounds to my like the home directory or other part of the disk is encrypted. And that leads me to wonder how and why you didn't know that, which leads me to wonder if this is a very fresh install. As in: this is the first boot after install.

When you installed, did you (on purpose) select an option to encrypt the disk or your home directory?

[UncleTed420]

Kinda sounds to my like the home directory or other part of the disk is encrypted. And that leads me to wonder how and why you didn't know that, which leads me to wonder if this is a very fresh install. As in: this is the first boot after install.

When you installed, did you (on purpose) select an option to encrypt the disk or your home directory?

Yes, I did check the box during install to encrypt my home folder. Mainly I was checking it out, just to see how it worked. Bad idea I guess.

[glennzo]

Since we're not sure if there is a corrupted partition I propose another avenue of attack. Boot the system and when you can get a command prompt log in as root. Then disable the virtualbox services so they won't start. We don't need them when trying to diagnose a system that won't fully boot.

I believe the following commands should suffice:

systemctl disable vboxdrv.service
systemctl disable vboxweb-service.service
systemctl disable vboxballoonctrl-service.service 

Then lets see what the last update brought in. I'm wondering if there was a kernel update. If there was, it may not match the latest installed akmods. To do that execute the following:

yum history list 

That will show a list of the last several yum updates. The top most listing is the last update. Lets call it "48" for the sake of arguement. Execute

yum history list 48 

That will list all packages updated / installed during the most recent update.

Could you also show the output of these three commands?

uname -r
rpm -qa | grep akmod
rpm -qa | grep kernel 

Hope this stuff is relevant to the current issue. As before, thinking out loud.

Forgot to mention that the whole idea behind disableing the VirtualBox services was so that they don't start at next boot and therefore are eliminated from the equasion.


You can also try disabling the akmods service too. I believe that the command to do that would be:

systemctl disable akmods.service 

[Dan]

Yes, I did check the box during install to encrypt my home folder. Mainly I was checking it out, just to see how it worked. Bad idea I guess.

Uhm ... not really. So long as you remember the passphrase you gave when it encrypted the thing. Just type that in when requested, and it should go through. If not ... that's the beauty of Linux. When (not if) it breaks/you break it ... you get to keep the pieces, and they don't charge you anything to start over. <....>

[UncleTed420]

after running "yum history list" here is the list I get:


ID Login User Date & Time Action(s) Altered
35 System <unset> 2012-05-12 10:27 Erase 1
34 System <unset> 2012-05-10 11:50 Install 4
33 System <unset> 2012-05-10 11:42 Erase 2
32 JohnDoeIII <johndoeiii> 2012-05-10 10:59 Install 1
31 System <unset> 2012-05-10 02:59 Install 1 EE
30 System <unset> 2012-05-10 02:57 Install 1
29 System <unset> 2012-05-10 02:56 Install 13 EE
28 System <unset> 2012-05-10 02:51 Install 7
27 System <unset> 2012-05-10 02:48 Erase 29
26 System <unset> 2012-05-10 02:47 Erase 1
25 System <unset> 2012-05-10 02:45 Install 2
24 JohnDoeIII <johndoeiii> 2012-05-10 02:34 Install 4
23 JohnDoeIII <johndoeiii> 2012-05-10 02:33 Install 3
22 System <unset> 2012-05-10 02:06 Install 58
21 System <unset> 2012-05-10 02:05 Install 2
20 System <unset> 2012-05-10 02:03 Install 114
19 System <unset> 2012-05-10 02:00 Install 1
18 System <unset> 2012-05-10 02:00 Install 8
17 System <unset> 2012-05-10 01:52 Install 10
16 System <unset> 2012-05-10 01:00 Install 3