Bug 1046129

Summary: Will not boot following first F20 update
Product: [Fedora] Fedora Reporter: William Oliver <vendor>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, michele, vendor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-17 18:43:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screen shot of boot sequence
none
Here's the lshw for the box none

Description William Oliver 2013-12-23 18:57:42 UTC 
Description of problem: Machine will not boot after the first update following clean install of F20


Version-Release number of selected component (if applicable):

F20


How reproducible:

Happened with two installs


Steps to Reproduce:
1.Install F20 KDE spin
2. Add Gnome, Development, and Office groups
3. Do "yum update" 
4. Reboot

Actual results:

Machine:  HP Pavilion D7 laptop,AMD processor. About two years old.

Boot hangs.  The first time, it seemed it couldn't find a disk, but I didn't write down the actual error.  I then reinstalled.  It will reboot fine *before* the automatic updates.  After the updates, I get the error that it fails on "Apply Kernal Variables."  I then powercycled the machine, and it hung again, though it didn't give me that error.  After about 30 mins, I took a picture of the screen (attached).

In all of these, it seems that things are happening -- about every four or five minutes a new line comes out.  If "feels" like something is continually waiting to time out.  But life is short...




Expected results:

Boot up.


Additional info:

The attached pic is from the screen after about 25 mins.
Comment 1 William Oliver 2013-12-23 19:05:42 UTC 
Created attachment 840928 [details]
Screen shot of boot sequence

Here's the screen shot
Comment 2 William Oliver 2013-12-23 19:14:41 UTC 
Created attachment 840929 [details]
Here's the lshw for the box

Here's the lshw for my box (after reinstalling F19)
Comment 3 William Oliver 2013-12-24 22:20:44 UTC 
One more note:  I reinstalled F20 and then *just* did the automatic update without any group installs -- including the kernel update.  It reboots fine.  Thus, I suspect the problem is not with the new kernel, but with one of the hundreds of programs I added when I did a bunch of group installs.

I'll see if I can isolate which group causes the problem, but I'm not sure I'm willing to install a hundred programs one by one in order to find the offender.  Looks like this needs to be a low priority issue, or just close it,  until you find someone who can figure out which program screws things up.
Comment 4 Michele Baldessari 2013-12-25 22:55:47 UTC 
Hi William,

hard to say here. If you boot in the problematic F20 box and add '3' to the boot parameters so we boot in runlevel three which does not have the graphical login
manager. Does the boot process proceed and you get to the console 'root:' prompt?

regards,
Michele
Comment 5 Justin M. Forbes 2014-03-17 18:43:00 UTC 
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.
Comment 6 William Oliver 2014-06-16 13:12:11 UTC 
I apologize for not replying.  Somehow I missed the email saying there was a reply, and *just now* saw the nastygram from bugzilla telling me that I had an outstanding request.

For what it's worth, this *was* an issue with blindly installing software groups.  I re-installed F20, and then only installed software as I needed it.  The problem never recurred, so I don't know what software incompatibility caused the issue.  Of course, at this point, we are another zillion updates down the road, so it's a moot point.