Fedora 16 x64 won't get to login - Failed to start LSB

[T3STY]

Hello everybody!

I am new here, and the problem I'm going to ask help for I have already posted it some hours ago in linuxforums.org forum, unfortunately without any answer - even if it had more than 150 views... I'm going to copy-paste it here explaining the situation I am runned into and I hope you can help me.

---START---
I have a very big problem with my Fedora 16 installation (x64, Gnome 3, updated to 3.2 kernel). I think I know where the problem is, but I'm not sure. Now I'm sticking with a Fedora 16 x86 installation on my USB pendrive. Anyway, yesterday I have installed the lastest version of VirtualBox ( 4.1.8 ) using the RPM from the official website. When I wanted to start a new virtual machine it gave me an error massage saying to run this:
/etc/init.d/vboxdrv setup
Ran it in a terminal and it showed that DKMS was not installed. Then I installed it with yum install dkms and all gone fine, the virtual machine was working.
Until here, you could see nothing wrong, right? well, to me it's DKMS that is causing me troubles. It needs the kernel source to get compiled right, and it probably took a wrong kernel version. But let's get a little further... after this I was looking for a way to swap the Super keys (the keys with the Win logo) because I needed the right super key to work as the left one - on my keyboard I have an Fn key instead of the left super and I can't start activities (Gnome 3 feature) with the right super key. I've done this:
xmodmap -pke (showing the actual keymap configuration)
xmodmap -e "keysym Super_R = Super_L" (setting the Win_R to be Win_L)
xmodmap -pke (checking the new keymap configuration)
The checking said that the 134th key (Super_R) was now acting as Super_L (133rd key). But when pressing it did nothing. So I thought I had to restart to apply changes... I've never seen the login window since then. It is always hanging at the boot with the message:
Failed to start LSB: starts and stops login and scanning of iSCSI devices...
See 'systemctl status iscsi.service' for details
I've switched to another tty with CTRL+ALT+F2, logged in with root and executed systemctl, but it only said that it failed to start LSB, nothing more.

I'm not really experinced in using Linux (I was using Ubuntu 9.04/10, then switched back to Windows) and I really don't know how to get rid of this problem.
Could you help me, please?

p.s. Sorry for writing so much but I thought you may need to know exactly how things gone.

UPDATE:
I've found on some posts on the web that I must execute the exact command systemctl status iscsi.service. This is the output:

Loaded: loaded (/etc/rc.d/init.d/iscsi)
Active: failed since Wed, 29 Feb 2012 15:53:50 +0100; 19s ago
Process: 1264 ExecStart=/etc/rc.d/init.d/iscsi start (code=exited, status=3/NOT IMPLEMENTED)
CGroup: name=system: /system/iscsi.service

---END---

If you have any hint that could help, please tell it to me. I don't want to run out of the trubles using the windows way (reinstalling the OS...). Thank you!

[PabloTwo]

The error you're seeing here,
Failed to start LSB: starts and stops login and scanning of iSCSI devices...
See 'systemctl status iscsi.service' for details
is almost certainly not the cause of the hangup. Almost every user that has installed F16 gets/got that same error message. It is just the iscsi.service "failing" to find any iscsi devices. Both the iscsi.service and iscsid.service are enabled by default.

To eliminate that error message (once you're finally able to boot) do:
systemctl disable iscsi
systemctl disable iscsid
Whatever is causing the "hang" is whatever is coming after the error message you're seeing about iscsi.
Have you tried booting into runlevel 1 from the grub2 menu, or using CTRL-ALT_F2 when it hangs to get a login prompt?

[T3STY]

yes, I have already tried loggin in with CTRL+ALT+F2 and I can successfully login. Although, when I try to do startx it tells me it can't find any display. Also, I have looked in the log in /var7log/X11.0.log (can't well remember the log path) and it said something about the VirtualBox video service. I'm at school now and there's no way I can't remember the errors it gave me. Although, I am now sure that it has to do with the VirtualBox kernel drivers because, from what I could read from the log, the xserver won't start its display driver, it tries to use the virtualbox video driver which fails to get any display.

When I get home I'll disable those services you told me, I hope it's enough to get started the x session. Any way I can disable the virtualbox kernel drivers?

[PabloTwo]

Disabling the iscsi and iscsid services won't do anything to resolve your "X won't start" issue. That will only make the error message you see about iscsi go away. I don't use any VM's, so I can't help you any VB issue.

[T3STY]

I have run the two commands above, but none worked.When I run systemctl disable iscsi it gives me this output:
Failed to issue method call: Unit name iscsi is not valid
When I run systemctl disable iscsid it gives me this other output:
Failed to issue method call: Invalid argument
Any idea why I get these outputs?

[PabloTwo]

OK, then try these:
chkconfig iscsi off
chkconfig iscsid off
I had forgotten that the iscsi stuff was still configured in /etc/init.d/
BASH:~/-> sudo chkconfig --list

Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.

iscsi 0:off 1:off 2:off 3:off 4:off 5:off 6:off
iscsid 0:off 1:off 2:off 3:off 4:off 5:off 6:off
jexec 0:on 1:on 2:on 3:on 4:on 5:on 6:on
livesys 0:off 1:off 2:on 3:on 4:on 5:on 6:off
livesys-late 0:off 1:off 2:on 3:on 4:on 5:on 6:off
netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off
netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
network 0:off 1:off 2:off 3:off 4:off 5:off 6:off
postfix 0:off 1:off 2:off 3:off 4:off 5:off 6:off
sandbox 0:off 1:off 2:off 3:off 4:off 5:on 6:off
svnserve 0:off 1:off 2:off 3:off 4:off 5:off 6:off

---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------

Oh, my mistake... I should have written:
systemctl disable iscsi.service
systemctl disable iscsid.service

[T3STY]

I have run the chkconfig commands and I have disabled the services. Thn I thought to get a look inside to see what was starting up from virtualbox and I found that there were 4 related services, 1 of dkms auto installer and 3 of virtualbox. I disabled them too as I don't really care if VB won't work anymore. But unfortunately it didn't help; now there's no more the fail message, but I still can't get to the login screen nor start the xserver.
I haven't thought of this before, but, could it be useful for you to have the boot and xorg log? I'm attaching them here maybe you can understand more than I do.

/var/log/boot.log
At this point it should start the xserver with the login window, but it hangs just like this. Here I can do CTRL+ALT+F2 to go to another tty. Logged in as root I run startx but it fails to start because it can't find any display. This is the log referenced in the error message:
/var/log/Xorg.0.log
From what I could understand, the xserver wants to use the virtualbox driver, but it fails, obviously... the virtualbox video driver depends on system's real video driver. So why on Earth would X want to start with virtualbox's video driver?

[T3STY]

I looked all over the network but seems like there's no way to remove the virtual box kernel drivers.
So, because I couldn't get helped for good here and elsewhere (I'm not blaming you for this) and I'm not able to get rid of this problem, it seems quite obvious to me that I should reinstall Fedora... although it's the way I'd never choose...
Thanks to Pablo Two for the help, next time I hope someone will know more about this issue.

[jay2933]

I am new here and this is my first post so I'm sorry if I am not following the proper etiquette. I came across this thread this morning while trying to find a fix for this very problem after installing VirtualBox, and as you had stated in one of your earlier posts the display was trying to use the VirtualBox drivers. I was able to resolve this problem by using ctrl+alt+f2 and logging in as su. Then I was able to list the VirtualBox packages with "yum list "*VirtualBox"" and removed those files with "yum remove (package name)" Then to get rid of the "guest" addons it typed "yum list "*guest"" I found the one that corresponded with VirtualBox and did the yum remove command again for this package and it also recognized the kernel package as no longer needed and removed it with it. I'm not sure if you have already done a fresh install or not but I hope this helps. My laptop booted up like normal as soon as I did this.

[jhiii]

I have the exact same problem i will try your fix and post results back
:)

---------- Post added at 10:13 AM ---------- Previous post was at 09:37 AM ----------

thankyou worked great had a little trouble finding the packages but it worked
:dance:

[T3STY]

I have already done a fresh install, I needed the PC working normal, not from a USB drive, and I couldn't wait more. Anyway, thank you for the solution jay2933. BTW, were you able to install and use VirtualBox on Fedora 16 without the virtualbox video driver to give these troubles? I'd need Windows in a virtual machine for some tasks and I'm not sure I want to reinstall VirtualBox after what happened...

[jay2933]

I was able to get VirtualBox back on and working (using it to test out Windows 8). I know in my case that the problem with the first install was that I also installed the Guest Additions which had an additional dependency which was a kernel module package. The kernel module package was what caused my problem so when I re-installed VirtualBox I just made sure not to install the Guest Additions or the kernel module package. Not sure if that was the same problem you were having but that was mine. Hope you are able to get VirtualBox running :)

[T3STY]

Oh, ok! Such a simple solution :D
I had installed guest additions too, and I remember VirtualBox was saying something about kernel modules (which I obviously ignored because I was used to Windows's VirtualBox). Tomorrow I'll install again VirtualBox so I may confirm that guest additions can cause this issue.

[T3STY]

I have installed again virtualbox and dkms. I confirm that installing guest additions in virtualbox can cause the issue described in my first post BUT, it only breaks the system if you choose to install and enable the OpenGL hardware 3D acceleration. Virtualbox will ask you during the installation of the guest-additions if you want to enable the HW 3D acceleration support. This support though needs VirtualBox to modify the host OS to enable VirtualBox to share the hardware resources, so it needs to modify X11 (I don't know how, this is just the very lite version of what I found on various websites and what I could understand from all of this story). Though, if you install the guest-additions but don't enable the hardware 3D acceleration virtualbox will work just fine.

Keep in mind that it may not work on some systems (like jay2933's and mine) like it may work on your system, so please don't take this warning as a "guest-additions will break my system for sure".

If you want to know more about 3D acceleration in virtualbox here you can find some more info:
http://www.virtualbox.org/manual/ch04.html#guestadd-video