big crash after kernel update to 244 (initrd cannot find any executables)
Hi, this problem seems to be on ppc and intel based hosts. After the kernel update from 201 to 244 (done as usual) and the reboot, initrd is failing completely, mentioning that it cannot find and executables. It leaves me with a shell prompt. Unfortunately the shell prompt is unusable, because even /bin/ls does not work (funny, the shell scripts are executed anyway, so /bin/sh is ok) ... The Servers are unusable after the kernel update ! I need urgently a solution for this, because all our Servers wants to update (or have to, according to our security policies) and I'm not willing to fix 100 machines by hand ! Regards marco hoehle
On Tue, Jan 03, Marco Hoehle wrote:
Hi,
this problem seems to be on ppc and intel based hosts. After the kernel update from 201 to 244 (done as usual) and the reboot, initrd is failing completely, mentioning that it cannot find and executables. It leaves me with a shell prompt. Unfortunately the shell prompt is unusable, because even /bin/ls does not work (funny, the shell scripts are executed anyway, so /bin/sh is ok) ...
The Servers are unusable after the kernel update !
Have you any more details on it? Also run this command to get a list of the initrd content: gzip -cd < /boot/initrd | cpio -tv -- short story of a lazy sysadmin: alias appserv=wotan
Olaf,
I'm still debugging. I think i got an idea what caused the problem . It's
because we're using yum to update the Hosts and it seems like if the
mkinitrd was still the old one while the kernel was updated.
have: mkinitrd-1.2-27.9
must: mkinitd-1.2-27.21
I think that this is the problem, so it is not 100% Novell related ;-) so
i'll try to verify this and give you feedback than.
Is it possible that this "old" mkinitrd is building a bad initrd with the
new kernel version (it worked until 201, in 202.7/244 it seems not to work)
?
Regards
marco
Olaf Hering
Hi,
this problem seems to be on ppc and intel based hosts. After the kernel update from 201 to 244 (done as usual) and the reboot, initrd is failing completely, mentioning that it cannot find and executables. It leaves me with a shell prompt. Unfortunately the shell prompt is unusable, because even /bin/ls does not work (funny, the shell scripts are executed anyway, so /bin/sh is ok) ...
The Servers are unusable after the kernel update !
Have you any more details on it? Also run this command to get a list of the initrd content: gzip -cd < /boot/initrd | cpio -tv -- short story of a lazy sysadmin: alias appserv=wotan
On Tue, Jan 03, Marco Hoehle wrote:
Olaf,
I'm still debugging. I think i got an idea what caused the problem . It's because we're using yum to update the Hosts and it seems like if the mkinitrd was still the old one while the kernel was updated.
have: mkinitrd-1.2-27.9 must: mkinitd-1.2-27.21
I think that this is the problem, so it is not 100% Novell related ;-) so i'll try to verify this and give you feedback than.
Is it possible that this "old" mkinitrd is building a bad initrd with the new kernel version (it worked until 201, in 202.7/244 it seems not to work) ?
I dont know what yum is. But either initrd files should work ok. All you can get is a 'insmod failed due to kernel version mismatch'. Maybe something did corrupt the initrd. the only thing that could cause this is a SP2 mkinitrd.rpm with a SP3 glibc. The ldd output changed in SP3, mkinitrd is parsing that output to find the required libraries. The dynamic linker is missing. Just upgrade the mkinitrd pacakge manually and rerun mkinitrd. -- short story of a lazy sysadmin: alias appserv=wotan
participants (2)
-
Marco Hoehle -
Olaf Hering