ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled

== Comment: #0 - Sowmya G. Parvathi <email address hidden> - 2015-01-29 12:43:30 ==
I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`".

Steps to recreate:

1. Install ubuntu 15.04 (netboot)
2. sudo passwd root
3. apt-get update, apt-get install openssh-server, apt-get nfs-common
4. service ssh restart
5. apt-get install linux-crashdump:

 ??????????????????????????? Configuring kexec-tools ??????????????????????????
 ? ?
 ? If you choose this option, a system reboot will trigger a restart into a ?
 ? kernel loaded by kexec instead of going through the full system boot ?
 ? loader process. ?
 ? ?
 ? Should kexec-tools handle reboots? ?
 ? ?
 ? <Yes> <No> ?
 ? ?
 ?????????????????????????????????????????????????????????????????????????????

Selected "Yes"

6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M)
7. update-grub
8. reboot

 .wait-for-state stop/waiting
 * Starting userspace bootsplash utility [ OK ]
Cannot open `/boot/vmlinuz': No such file or directory
 * Loading new kernel image into memory... [fail]
 * Stopping uuidd generator uuidd [ OK ]
 * Asking all remaining processes to terminate... [ OK ]
 * All processes ended within 1 seconds... [ OK ]
 * Stopping NSM status monitor [ OK ]
rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
 * Stopping RPC portmapper replacement [ OK ]
 * Stopping D-Bus system message bus [ OK ]
 * Stopping NFSv4 id <-> name mapper [ OK ]
 * Stopping configure virtual network devices [ OK ]
 * Stopping configure network device security [ OK ]
 * Deactivating swap... [ OK ]
 * Will now restart
[ 20.328664] reboot: Restarting system

lpar will be up, but i am not sure of this error.

uname -a
Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

Contact Info: <email address hidden>

== Comment: #2 - David Heller <email address hidden> - 2015-01-29 14:19:43 ==
On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64.

Can you try editing the grub.cfg to see if that fixes it?

if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched

== Comment: #3 - Sowmya G. Parvathi <email address hidden> - 2015-01-30 05:50:32 ==
I think the issue is with /etc/default/kexec file and not grub.cfg.
----------------------------------------------------------------------------------------------------
kexec:

# Defaults for kexec initscript
# sourced by /etc/init.d/kexec and /etc/init.d/kexec-load

# Load a kexec kernel (true/false)
LOAD_KEXEC=true

# Kernel and initrd image
KERNEL_IMAGE="/boot/vmlinuz"
INITRD="/boot/initrd.img"

# If empty, use current /proc/cmdline
APPEND=""

# Load the default kernel from grub config (true/false)
USE_GRUB_CONFIG=false

----------------------------------------------------------------------------------------------------

Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur.