Today I ran “zypper update” on one of our servers, and all went well untill kernel update (from default 3.0.51-0.7.9 to 3.0.58-0.6.6). After I stupidly tried to re-install the kernel, I now have a running system without a bootable kernel. Any pointers?
Kernel image: /boot/vmlinuz-3.0.58-0.6.6-default
Initrd image: /boot/initrd-3.0.58-0.6.6-default-kdump
Root device: /dev/disk/by-id/scsi-SServeRA_raid1_58D4D505-part3 (/dev/sda3) (mounted on / as ext3)
Resume device: /dev/disk/by-id/scsi-SServeRA_raid1_58D4D505-part2 (/dev/sda2)
Boot device: /dev/disk/by-id/scsi-SServeRA_raid1_58D4D505-part1 (/dev/sda1)
find: `/lib/modules/3.0.58-0.6.6-default/kernel/drivers/scsi/device_handler’: No such file or directory
modprobe: Module thermal not found.
WARNING: no dependencies for kernel module ‘thermal’ found.
modprobe: Module processor not found.
WARNING: no dependencies for kernel module ‘processor’ found.
modprobe: Module fan not found.
WARNING: no dependencies for kernel module ‘fan’ found.
modprobe: Module aacraid not found.
WARNING: no dependencies for kernel module ‘aacraid’ found.
modprobe: Module ata_generic not found.
WARNING: no dependencies for kernel module ‘ata_generic’ found.
modprobe: Module piix not found.
WARNING: no dependencies for kernel module ‘piix’ found.
modprobe: Module ide_pci_generic not found.
WARNING: no dependencies for kernel module ‘ide_pci_generic’ found.
modprobe: Module usbhid not found.
WARNING: no dependencies for kernel module ‘usbhid’ found.
modprobe: Module pci:v000014E4d0000164Csv00001014sd00000342bc02sc00i00 not found.
WARNING: no dependencies for kernel module ‘pci:v000014E4d0000164Csv00001014sd00000342bc02sc00i00’ found.
modprobe: Module nls_utf8 not found.
WARNING: no dependencies for kernel module ‘nls_utf8’ found.
Kernel Modules: scsi_mod libata ata_piix jbd mbcache ext3 edd usb-common usbcore ohci-hcd uhci-hcd ehci-hcd af_packet crc-t10dif sd_mod
Features: acpi block usb network resume.userspace resume.kernel kdump
44977 blocks
Don’t refresh the bootloader. You may have to do that manually!
Have a look in /etc/sysconfig/kernel, there should be a line for “INITRD_MODULES”, where these are referenced. Looking at a current SLES11SP2 system, I see
OK, no error messages now! Turns out, both the old and the new module names were mentioned in the INITRD_MODULES -list. I’ll try booting the server tomorrow. Thanks!