This concerns kexec-tools 1:2.0.1-2ubuntu4 in Ubuntu Natty.
I am trying to get a kernel crash dump. Instead of getting a nice vmcore file in /var/crash/, I get a vmcore.log file with the following:
/root/usr/bin/makedumpfile: error while loading shared libraries: libdw.so.1: cannot open shared object file: No such file or directory
Problem number 1: /usr/bin/makedumpfile is a dynamically-linked executable. Not the kind of thing you want to run in an initramfs environment.
There is, however, a "makedumpfile-static" package, which not only provides /bin/makedumpfile-static, but also an initramfs-tools hook so that this statically-linked binary is copied in as /bin/makedumpfile in the initrd.
Problem number 2: The 0_kdump script is hard-coded to use the dynamic binary in root:/usr/bin/. It is not at all aware of initrd:/bin/makedumpfile .
Binary package hint: kexec-tools
This concerns kexec-tools 1:2.0.1-2ubuntu4 in Ubuntu Natty.
I am trying to get a kernel crash dump. Instead of getting a nice vmcore file in /var/crash/, I get a vmcore.log file with the following:
/root/usr/ bin/makedumpfil e: error while loading shared libraries: libdw.so.1: cannot open shared object file: No such file or directory
Problem number 1: /usr/bin/ makedumpfile is a dynamically-linked executable. Not the kind of thing you want to run in an initramfs environment.
There is, however, a "makedumpfile- static" package, which not only provides /bin/makedumpfi le-static, but also an initramfs-tools hook so that this statically-linked binary is copied in as /bin/makedumpfile in the initrd.
Problem number 2: The 0_kdump script is hard-coded to use the dynamic binary in root:/usr/bin/. It is not at all aware of initrd: /bin/makedumpfi le .