Bug 199629 - kernel panic not syncing: vfs:unable to mount root fs on unknown block(0,0)
Summary: kernel panic not syncing: vfs:unable to mount root fs on unknown block(0,0)
Status: CLOSED INVALID
Alias: None
Product: File System
Classification: Unclassified
Component: ext4 (show other bugs)
Hardware: Intel Linux
: P1 blocking
Assignee: fs_ext4@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-05 21:14 UTC by schmitt
Modified: 2018-05-18 17:50 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.16.4 and higher
Subsystem:
Regression: No
Bisected commit-id:

Attachments
kernel panic not syncing: vfs:unable to mount root fs on unknown block(0,0) (1018.34 KB, image/jpeg)
2018-05-05 21:14 UTC, schmitt 		Details
Picture of screen (123 bytes, text/plain)
2018-05-18 15:27 UTC, Andre 		Details
Add an attachment (proposed patch, testcase, etc.)

Description schmitt 2018-05-05 21:14:08 UTC 
Created attachment 275783 [details]
kernel panic not syncing: vfs:unable to mount root fs on unknown block(0,0)

hi,


i use ukuu kernel update utility to update kernel.


the kernel 4.16 to kernel 4.16.3 boot with no Problem.


the kernel 4.16.4 to kernel 4.16.7 boot with kernel panic



kernel panic not syncing: vfs:unable to mount root fs on unknown block(0,0)

See attachment.

Mathieu
Comment 1 Andre 2018-05-18 15:27:31 UTC 
Created attachment 276041 [details]
Picture of screen

When installing result I get from Update utility
Comment 2 schmitt 2018-05-18 17:45:07 UTC 
hi,


ukuu dont download linux-modules-4.16.x-----.deb and dont install it.(x >=4 and x<=7)
it's the same for 4.17rc1 to 4.17rc5


i have manually donwloaded:

linux-headers-4.17.0-041700rc5_4.17.0-041700rc5.201805132030_all.deb
linux-headers-4.17.0-041700rc5-generic_4.17.0-041700rc5.201805132030_amd64.deb
linux-image-unsigned-4.17.0-041700rc5-generic_4.17.0-041700rc5.201805132030_amd64.deb
linux-modules-4.17.0-041700rc5-generic_4.17.0-041700rc5.201805132030_amd64.deb

and install all deb files. no kernel panic 

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