Bug 1383082 - 4.7.6 kernel update causes system not to boot
Summary: 4.7.6 kernel update causes system not to boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-09 18:06 UTC by Edward
Modified: 2016-10-10 02:24 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-10 02:24:57 UTC
Type: Bug


Attachments (Terms of Use)
Errors displayed on screen (1.44 MB, image/jpeg)
2016-10-09 18:06 UTC, Edward
no flags Details
Going into emergency mode upon boot (1.02 MB, image/jpeg)
2016-10-09 18:06 UTC, Edward
no flags Details

Description Edward 2016-10-09 18:06:07 UTC
Created attachment 1208623 [details]
Errors displayed on screen

Upon updating system (dnf) which included the new kernel, there was an error and upon attempting to reboot afterwards, the system will now not boot up into Linux. It goes into emergency mode and states to copy run/initramfs/rdsosreport.txt into a bug report, however that file doesn't exist in that subdirectory when I checked it after booting using the Linux-rescue entry on the boot menu.

Erasing     : kernel-core-4.7.3-200.fc24.x86_64                        97/102 
warning: file /lib/modules/4.7.3-200.fc24.x86_64/kernel/net/dns_resolver/dns_resolver.ko.xz: remove failed: No such file or directory

The installed kernels show 4.7.6, 4.7.5 and 4.7.4 on the Grub menu, in addition to the rescue entry, it would not boot into 4.7.6 or 4.7.5, did not try it using 4.7.4.

I am attaching photos of the screen when the system crashed.

Comment 1 Edward 2016-10-09 18:06:48 UTC
Created attachment 1208624 [details]
Going into emergency mode upon boot

Comment 2 Edward 2016-10-10 02:24:57 UTC
Reinstalled Fedora from image, system seems to be running fine now.


Note You need to log in before you can comment on or make changes to this bug.