Description of problem: Kernel panic: cannot mount fs It worked with kernel-server-4.4.5-1.mga5 Is this a known problem? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Additional information: Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0) CPU:2 PID: 1 Comm: swapper/0 Not tainted 4.4.5-server-2.mag5 #1 Hardware name /DQ35MP, BIOS JOQ35/OJ.86A.1056.2009.0427.2004 Root file system: btrfs It is only the i686 server kernel that has this problem. I have booted 3 x86_64 desktop versions without any problems.
(In reply to Bjarne Thomsen from comment #1) > Additional information: > Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0) > CPU:2 PID: 1 Comm: swapper/0 Not tainted 4.4.5-server-2.mag5 #1 > Hardware name /DQ35MP, BIOS JOQ35/OJ.86A.1056.2009.0427.2004 > > Root file system: btrfs > It is only the i686 server kernel that has this problem. And there is no problem on the same system with an older kernel? > I have booted 3 x86_64 desktop versions without any problems. On different systems, I assume?
Keywords: (none) => NEEDINFOCC: (none) => marja11Assignee: bugsquad => tmb
No problem with older server kernels on this system. yes, x86_64 on 3 different systems. One uses ext4, the other 2 use btrfs for / .
But the hardware is different on the 4 systems.
I dont really see how the 3 security fixes that were the only changes between -1.mga5 and -2.mga5 would do this... Could there have been some temporary issues during kernel install ? Have you tried to re-install the kernel. either by removing it and reinstalling it, ro by telling urpmi to reinstall/overwrite it with: urpmi --media "Core Updates Testing" kernel-server-4.4.5-2.mga5 --replacepkgs
I removed kernel-server-4.4.5-2.mga5 Selected a new media mirror. Installed kernel-server-4.4.5-2.mga5 again. Rebooted. It came up without the panic. I rebooted onece more to be sure. It came up without a panic.It seems to work. Yes. Something must have gone wrong during the first install.
Exactly the same panic happened again after an update to kernel-server-4.4.6-1. I then removed it, and changed the repository to ftp.acc.umu.se and installed it again. Now it works. The first time around I used rpmi --auto-update.
Mass-reassigning all bugs with "kernel" in the summary that are still assigned to tmb (or wrongly assigned to someone with "tmb" in his e-mail address) to the kernel packagers group, but without adding "kernel" to the SRPM field. Please reassign if needed, or add kernel to the SRPM field if this is correct.
Assignee: tmb => kernel
Bug 19460 is a duplicate of this one, but it contains more recent information. Therefore closing this one and leaving that report open. *** This bug has been marked as a duplicate of bug 19460 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE