Red Hat Bugzilla – Bug 591311
RHEL6.0 Beta 1 fails to reboot after kickstart install
Last modified: 2010-10-23 11:17:25 EDT
Escalated to Bugzilla from IssueTracker
Event posted on 04-27-2010 12:42pm EDT by sandy.garza Description of problem: The install runs correctly installs the boot loader and runs the post-install scripts (we remove all of ours from the kickstart file, so there are none). The screen then goes blank and nothing happens. There is still a graphic mouse, but know mouse or keyboard action will cause it to reboot. If we telnet to the server we are in anaconda. If we power cycle the server it will boot RHEL6.0. We tried doing this using the "text" kernel parameter which tells it not to use the UI. Again this runs to completion, but then it print a line at the bottom that says "Enter Control C or Cntl-Alt-Delete to reboot the system. We have never seen this before. Using the "nomodeset" option did not help How reproducible: Steps to Reproduce: Actual results: Expected results: Additional info: Tested on DL360 G5. Sosreport forthcoming. This event sent from IssueTracker by dwa [HP-ProLiant] issue 816913
Event posted on 04-27-2010 02:58pm EDT by sandy.garza File uploaded: sosreport-Hrifkin.1001031472-20100427221505-8035.tar.bz2 This event sent from IssueTracker by dwa [HP-ProLiant] issue 816913 it_file 608923
Created attachment 413257 [details] kickstart file in use
Can you also attach /tmp/anaconda.log and /tmp/program.log? Thanks.
Sorry, I see them in the sosreport. Attaching for future convenience. They don't look helpful though.
Created attachment 413262 [details] anaconda.log
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
Could you attach the other /tmp/*log files? This sounds like there is an error right at the end of the install (hence the ctrl-c prompt). Does tty5 show anything unusual when it is done? Or is there any information right above the Ctrl-C prompt? You might also try not passing nokill to it.
This is due to passing nokill on the kernel command line.