Fedora 17 stuck on logo

efid845 · #1 12th June 2012, 06:01 AM

I have fedora 17.
I have just boot up my PC, and from some reason, Fedora just stucks on the logo
** its getting "filled up", the full logo showed up, and thats it**

What can I do?

weitjong · #2 12th June 2012, 08:25 AM

You can try to press the ESC key while Plymouth is in progress (the Fedora logo splash in your case) to see the boot process behind the scene. Alternatively, you may also try to boot in text mode by intercepting grub2 and change the boot option to exclude the 'rhgb' and 'quite'.

If you still cannot figure out what is the offending process that stop your boot, see if you can switch to virtual terminal by pressing CTRL+ALT+2 combo after Plymouth stops. And check the logs in /var/log/ after you login as root in the terminal.

efid845 · #3 12th June 2012, 10:36 AM

Quote:

Originally Posted by weitjong

You can try to press the ESC key while Plymouth is in progress (the Fedora logo splash in your case) to see the boot process behind the scene. Alternatively, you may also try to boot in text mode by intercepting grub2 and change the boot option to exclude the 'rhgb' and 'quite'.

If you still cannot figure out what is the offending process that stop your boot, see if you can switch to virtual terminal by pressing CTRL+ALT+2 combo after Plymouth stops. And check the logs in /var/log/ after you login as root in the terminal.

OK, I have gave him about 15min to run,
and it stuck on this line:
Stopping Sendmail Mail Transport Client.

BTW, all the processes ware signed as OK...

What should I do?

nonamedotc · #4 12th June 2012, 02:23 PM

Did you try logging in as root using the virtual terminal as weitjong suggested? CTRL+ALT+F2 *might* get you to VT ...

Also, try [removing] the boot options - 'rhgb', 'quiet'

droidhacker · #5 12th June 2012, 03:50 PM

Quote:

Originally Posted by nonamedotc

Did you try logging in as root using the virtual terminal as weitjong suggested? CTRL+ALT+F2 *might* get you to VT ...

Also, try the boot options - 'rhgb', 'quiet'

I think you mean to REMOVE those boot options....

nonamedotc · #6 12th June 2012, 04:03 PM

Apologies! yes - that's what I meant.

efid845 · #7 12th June 2012, 05:51 PM

Quote:

Originally Posted by nonamedotc

Did you try logging in as root using the virtual terminal as weitjong suggested? CTRL+ALT+F2 *might* get you to VT ...

Also, try [removing] the boot options - 'rhgb', 'quiet'

Quote:

Originally Posted by droidhacker

I think you mean to REMOVE those boot options....

Quote:

Originally Posted by nonamedotc

Apologies! yes - that's what I meant.

OK, but how exactly can i remove them?
Isn't it make any problems?

secipolla · #8 12th June 2012, 06:48 PM

Open an editor as root and edit /etc/default/grub
Then remove rghb and quiet and save.
Then run, as root
grub2-mkconfig -o /boot/grub2/grub.cfg

This will make the boot process show a lot of messages next time you boot.

efid845 · #9 12th June 2012, 07:13 PM

Quote:

Originally Posted by secipolla

Open an editor as root and edit /etc/default/grub
Then remove rghb and quiet and save.
Then run, as root
grub2-mkconfig -o /boot/grub2/grub.cfg

This will make the boot process show a lot of messages next time you boot.

OK, But where can i run it?
Fedora wont boot up

weitjong · #10 12th June 2012, 07:23 PM

You don't have to use grub2-mkconfig unless you want to make the changes permanent. For your case, you just want to change the option adhocly. When your PC just power on, press the "e" key the first instance you see Grub2 showing the boot menu. In the editor mode, you can remove the "rhgb" and "quite" options before continuing booting.

You may want to disable or mask the sendmail service first to see if that solve your boot problem. Unfortunately, to do that you must either reach the virtual terminal to login as root. The other way is to boot using Fedora LiveCD or DVD into rescue mode. That is, if you are really suspect sendmail is the culprit.

droidhacker · #11 12th June 2012, 09:01 PM

You can also set the runlevel at the kernel command line. Where you take out "rhgb quiet", you can ADD "1". This is single user mode and many services don't start in this mode, so it is more likely to work for you.

efid845 · #12 13th June 2012, 04:55 AM

Quote:

Originally Posted by weitjong

You don't have to use grub2-mkconfig unless you want to make the changes permanent. For your case, you just want to change the option adhocly. When your PC just power on, press the "e" key the first instance you see Grub2 showing the boot menu. In the editor mode, you can remove the "rhgb" and "quite" options before continuing booting.

You may want to disable or mask the sendmail service first to see if that solve your boot problem. Unfortunately, to do that you must either reach the virtual terminal to login as root. The other way is to boot using Fedora LiveCD or DVD into rescue mode. That is, if you are really suspect sendmail is the culprit.

Didn't work.
It stuck on Starting Display Manger.

Quote:

Originally Posted by droidhacker

You can also set the runlevel at the kernel command line. Where you take out "rhgb quiet", you can ADD "1". This is single user mode and many services don't start in this mode, so it is more likely to work for you.

I will try it

BTW, How can i disable process?

nonamedotc · #13 13th June 2012, 05:00 AM

Once you know what process is causing problems, you can use the command below

Code:

systemctl disable name.service

efid845 · #14 13th June 2012, 05:45 AM

Quote:

Originally Posted by nonamedotc

Once you know what process is causing problems, you can use the command below

Code:

systemctl disable name.service

But where should I write this command?

weitjong · #15 13th June 2012, 08:39 AM

Quote:

Originally Posted by efid845

Didn't work.
It stuck on Starting Display Manger.

The removal of "rhgb" and "quite" from the boot option is not the fix in itself. It merely facilitates you to see more verbose output during boot. You still have to figure out from those output what went wrong.

From all the posts above, you must be aware by now that you must at least reach a console/terminal before you can do anything: gain access to the boot log for troubleshooting or disabling/masking the suspected service from running, etc.

Try to get the terminal by:
1. Ctrl+Alt+F2. It depends on where the boot process stucks, one may or may not be able to switch to virtual terminal.
2. Boot into single user mode. Press 'e' in grub2 and append '1' at the end of the kernel boot option.
3. Use the liveCD/DVD to boot into rescue mode.

Perhaps we should take a step back. Can you tell us what did you last install that cause this problem? ATI/NVIDIA drivers perhaps? Or have you tried to boot using previous known good kernel version? You can choose which kernel version to boot into from Grub2 menu.