Boot screen freezes after updating RHEL 6.2 to RHEL 6.6
Yesterday in my lab I got a new system which was actually a old system and we were running it since last 5 year without any issue.
but when I got this I found that there was not even a single software was installing for e.g. teamviewer
so I downloaded rpm from official site and than tried to install it using "yum install teamviewer_version.rpm" command in terminal
but it stopped for dependency after several time of trying. so I searched for problem by googling it and get to know that dependency automatically able to download only when you have a active subscription of RHEL
so I searched for CD in my lab and got a 16 digit key xxxx-xxxx-xxxx-xxxx like this
than I activated subscription and got approx 712 update for my system I installed them and later on run command "yum install createrepo" than succefully installed software like teamviewer chrome etc.
but problem started when I restarted this system
after restarting it stopped a screen whicj having a bar in bottom of screen and also name of version of linux which says "REDHAT ENTERPRISE LINUX EDITION 6.6"
I waited for 15 minute but nothing happens so I restarted it again and this time I selected boot option with old version which was RHEL6.2 but again it stopped at same screen
so I again searched on google for this problem and figured it out that it is because when you update kernel than there are some phenomena called "SELinux" relables all file I can figure it on that very screen where it is stopping by press 'esc' so I did it for RHEL 6.2 so I found out it some thing like
"
*** Warning -- SELinux targeted policy relabel is required.
*** Relabeling could take a very long time, depending on file
*** system size and speed of hard drives.
"
where * says 1000 file labeled
I left it for labeling after 2 hour again that boot screen appeared and again it is same condition that bar and RHEL6.6 tag
so question is if I booted it for RHEL 6.2 and also labeling it for 6.2 than why RHEL6.6 appeared after completion of that labeling and why it is stopped again on that very screen
this time I am not able to press 'escape'
system size is 8TB and it is raid configured
Responses
Hello
You could set the enforcing mode to permissive to see if that will allow the system to reboot successfully. SELinux Modes
There is a section on labeling problems here Security-Enhanced Linux: Top Three Causes of Problems
Even if SELinux is in permissive mode, it still needs the labels to determine/derive AVC actions/alerts from. So, if it gives you a pass at boot on the relabel, that's probably not a Good Thing(TM) to do.
Another option is, when in the GRUB menu, edit the desired instance's kernel line and set selinux=0. That might get you past. It might also require booting into rescue mode and then nuking any .autorelabel files found on the filesystem roots.
When you say "I am able to login using remote ssh -X", are you indicating that you're able to get other X-clients to display (e.g., xterm pops up a new window on your other system) or do you simply mean you're able to SSH into the system and get a basic CLI prompt.
At any rate, a couple things can effect X console:
- Inability to resolve its own name, correctly
- Window manager security settings are not correct
- Improper SELinux labels (if SELinux is in Enforcing mode)
- Firewall rules are not correct
- Default init mode is not set correctly: if
who -rshows any value other than 5, the default init mode is incorrect for staring the graphical console. You might yet be able to successfully runstartxon a VC, even if in the wrong init mode ..but you'll want to reset the default init mode, if so.)
Your Xorg log files and your generic system log files should point the way.
Your log shows, "NVIDIA dlloader X Driver 340.76".
Your device is Quadro K5000 [10de:11ba].
I think you have installed a wrong version of the Nvidia driver. To find out which version supports your Nvidia card, please install and run nvidia-detect [1] from ELRepo. The easiest way to install the Nvidia driver will be to use the kmod-nvidia package [2]. Before using it, be sure to first uninstall the Nvidia driver you installed by using the file downloaded from the Nvidia site.
[1] http://elrepo.org/tiki/nvidia-detect
[2] http://elrepo.org/tiki/kmod-nvidia
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
