Fedora 16 x64 Boot problem I cannot figure out how to fix
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Fedora 16 x64 Boot problem I cannot figure out how to fix
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.
Distribution: Gentoo, Ubuntu, RHEL, CentOS, BSD, Solaris
Posts: 82
Rep:
So, the pressing question is... what changed? Was the system able to booting fine earlier? Did you run any updates or install any new packages? No doubt you can recover this but I'd be able to help more if we can kind of figure out what changed.
A few more questions to answer:
1. This error you're seeing appears to be related to Oracle's Virtual Box, did you recently update this?
2. The message about being required to enter a passphrase is that new? Did you recently encrypt a volume or has it always been like this?
3. Also what is the purpose of this box? Dual boot? Server? Virtual Machine? You seem to be running a ton of sever type daemons...
4. Have you tried changing runlevels and are you able to login from there? Also, try switching to runlevel 1 by using
Code:
Ctrl + Alt + F2 -- Are you able to logging in this state?
The only change that I made before this happened was that I thought I changed the capture key for VirtualBox, but apparently the change didn't take, so it just deleted the key and at the time I was using VirtualBox and I needed to look at something in Fedora, so the only thing I could think of at the time was to force a restart via the power button.
If I'm not mistaken I set my home partiton to encrypt during the install, but the current message is new. Before it use to never pop up with the blue & white bar at the bottom of the screen with Fedora 16 in blue letters.
The purpose of VirtualBox was to setup a virtual XP Machine.
I have no idea how to change rules so I'm pretty sure I never messed with any of that.
And I don't know how to try and login using Ctrl Alt F2. But at the screen where it asks for the Hitachi Passphrase if I don't push anything for 30 - 60 seconds it will bring me to another screen where I can enter my root password and have a root command line.
Distribution: Gentoo, Ubuntu, RHEL, CentOS, BSD, Solaris
Posts: 82
Rep:
Quote:
Originally Posted by UncleTed420
@ djsoundfx:
The only change that I made before this happened was that I thought I changed the capture key for VirtualBox, but apparently the change didn't take, so it just deleted the key and at the time I was using VirtualBox and I needed to look at something in Fedora, so the only thing I could think of at the time was to force a restart via the power button.
If I'm not mistaken I set my home partiton to encrypt during the install, but the current message is new. Before it use to never pop up with the blue & white bar at the bottom of the screen with Fedora 16 in blue letters.
The purpose of VirtualBox was to setup a virtual XP Machine.
I have no idea how to change rules so I'm pretty sure I never messed with any of that.
And I don't know how to try and login using Ctrl Alt F2. But at the screen where it asks for the Hitachi Passphrase if I don't push anything for 30 - 60 seconds it will bring me to another screen where I can enter my root password and have a root command line.
While the system is booting (just after grub) your hit Ctrl Alt F2 to enter the lower run level.
Did you install guest-additions for virtual box? Or did you enable 3D acceleration on your XP VM? I found a few threads on the web about how this can cause the error you're having as the guest additions require additional kernel modules.
It sounds like you're going to need to get in to that rescue prompt (or ctrl alt f2) and either disable virtual box from starting during boot up so you can at least get back in to your system. Then from there we can tackle the issue of getting virtual box running correctly.
Distribution: Gentoo, Ubuntu, RHEL, CentOS, BSD, Solaris
Posts: 82
Rep:
Quote:
Originally Posted by djsoundfx
While the system is booting (just after grub) your hit Ctrl Alt F2 to enter the lower run level.
Did you install guest-additions for virtual box? Or did you enable 3D acceleration on your XP VM? I found a few threads on the web about how this can cause the error you're having as the guest additions require additional kernel modules.
It sounds like you're going to need to get in to that rescue prompt (or ctrl alt f2) and either disable virtual box from starting during boot up so you can at least get back in to your system. Then from there we can tackle the issue of getting virtual box running correctly.
Forgot to mention... something like:
Code:
chkconfig vboxstartup off
should do the trick, then reboot. From there you can uninstall and reinstall virtualbox (this should not change anything with your XP VM).
While the system is booting (just after grub) your hit Ctrl Alt F2 to enter the lower run level.
Did you install guest-additions for virtual box? Or did you enable 3D acceleration on your XP VM? I found a few threads on the web about how this can cause the error you're having as the guest additions require additional kernel modules.
It sounds like you're going to need to get in to that rescue prompt (or ctrl alt f2) and either disable virtual box from starting during boot up so you can at least get back in to your system. Then from there we can tackle the issue of getting virtual box running correctly.
Tried hitting Ctrl + Alt + F2 after grub and it still brings me to the same screen with the Failed to start LSB: Builds and install new kmods from akmod packages
Distribution: Gentoo, Ubuntu, RHEL, CentOS, BSD, Solaris
Posts: 82
Rep:
Quote:
Originally Posted by UncleTed420
Tried hitting Ctrl + Alt + F2 after grub and it still brings me to the same screen with the Failed to start LSB: Builds and install new kmods from akmod packages
Try this method:
Code:
1. At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu.
2. Select Fedora with the version of the kernel that you wish to boot and type a to append the line.
3. Go to the end of the line and type single as a separate word (press the Spacebar and then type single). Press Enter to exit edit mode.
Though it really doesn't matter, just get in to recovery mode as root, and disable the vboxstartup (and any other vbox related daemons) then boot normally, and uninstall/reinstall virtualbox.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
