Hi - After a recent set of updates, one of my computers, running openSuSE Leap 42.2 x64 can no longer boot up and is having troubles loading the kernel. I get the following error message when Grub is running -
Loading Linux 4.4.74-18.20-default Can't read kernel /boot/vmlinuz-4.4.74-18.20-default. Loading initial Ramdisk error: you need to load the kernel first.
I think I have seen this sort of error before, sometime in the distant past, but don't remember how I solved it... I can go into the Advance Options for loading openSuSE (in the GRUB menu) and select an older version of openSUSE Leap 42.2, with Linux 4.4.73-18.17-default and get the system to run. So I suspect this is probably something simple like a missing link or some config file error?
So can some kind guru tell me how to fix this? Thanks in advance... Marc...
18.07.2017 21:35, Marc Chamberlin пишет:
Hi - After a recent set of updates, one of my computers, running openSuSE Leap 42.2 x64 can no longer boot up and is having troubles loading the kernel. I get the following error message when Grub is running -
Loading Linux 4.4.74-18.20-default Can't read kernel /boot/vmlinuz-4.4.74-18.20-default.
It means size of file as reported by filesystem does not match size that was read. One possibility is that filesystem was not properly flushed to disk. There was rather long thread about precisely this issue recently (not SUSE specific).
Does file look OK after you booted previous kernel? Does it pass verification (rpm -V)? If yes, simply rebooting will probably fix it.
On 07/18/2017 11:49 AM, Andrei Borzenkov wrote:
18.07.2017 21:35, Marc Chamberlin пишет:
Hi - After a recent set of updates, one of my computers, running openSuSE Leap 42.2 x64 can no longer boot up and is having troubles loading the kernel. I get the following error message when Grub is running -
Loading Linux 4.4.74-18.20-default Can't read kernel /boot/vmlinuz-4.4.74-18.20-default.
It means size of file as reported by filesystem does not match size that was read. One possibility is that filesystem was not properly flushed to disk. There was rather long thread about precisely this issue recently (not SUSE specific).
Does file look OK after you booted previous kernel? Does it pass verification (rpm -V)? If yes, simply rebooting will probably fix it.
Thanks Andrei, the rpm -V command did show a file size problem and also some sort of issue with permissions. (though I couldn't see anything wrong with the vmlinuz file using ls -al) Anywise I had YaST re-update the kernel-default package and that solved this issue....
Marc..
Marc Chamberlin wrote:
Thanks Andrei, the rpm -V command did show a file size problem and also some sort of issue with permissions. (though I couldn't see anything wrong with the vmlinuz file using ls -al) Anywise I had YaST re-update the kernel-default package and that solved this issue....
Is your kernel/boot/root partition quite full? Maybe it hit 100% during install, before purge-kernels removed older ones?
-
Andrei Borzenkov -
Marc Chamberlin -
Peter Suetterlin