rhel5.6 kdump initrd problem?
Subsystems (2)
Hi all,
I have a system running 2.6.18-238.12.1.el5 kernel. The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran /etc/init.d/kdump and a new kdump initrd image was created.
A kernel crash was triggered. The kdump kernel was booted alright. However, it failed to boot when it tried to boot back the regular kernel (now with the kdump initrd image specified in the menu.lst.)
Has anyone else seen this problem?
Thanks,
Jay
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Quoted 11 lines · Jay Lan
Hi all,
I have a system running 2.6.18-238.12.1.el5 kernel. The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran
/etc/init.d/kdumpand a new kdump initrd image was created.
A kernel crash was triggered. The kdump kernel was booted alright. However, it failed to boot when it tried to boot back the regular kernel (now with the kdump initrd image specified in the menu.lst.)
I forgot to mention the failure message:
...
Saving to the local filesystem LABEL=xxxroot
findfs: Unable to resolve 'LABEL=xxxroot'
So, we did not have root fs and boot failed.
Thanks,
Jay
Quoted 6 lines
Has anyone else seen this problem?
Thanks,
Jay
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Hi Jay,
Quoted 11 lines · On Tue, 27 Sep 2011 12:38:11 -0700 Jay Lan <[email protected]> wrote:
Quoted 10 lines
I have a system running 2.6.18-238.12.1.el5 kernel. The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran
/etc/init.d/kdumpand a new kdump initrd image was created.
A kernel crash was triggered. The kdump kernel was booted alright. However, it failed to boot when it tried to boot back the regular kernel (now with the kdump initrd image specified in the menu.lst.)
Quoted 4 lines
I forgot to mention the failure message:
...
Saving to the local filesystem LABEL=xxxroot
findfs: Unable to resolve 'LABEL=xxxroot'
If specifying a dev name (ex. /dev/sda3) instead of "LABEL" in /etc/kdump.conf, what happens ?
findfs command doesn't run in the kdump initrd if specifying a dev name.
In addition, can you try findfs LABEL=xxxroot while the regular kernel runs ?
Thanks
Ken'ichi Ohmichi
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Quoted 11 lines · Jay Lan
Hi all,
I have a system running 2.6.18-238.12.1.el5 kernel. The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran
/etc/init.d/kdumpand a new kdump initrd image was created.
A kernel crash was triggered. The kdump kernel was booted alright. However, it failed to boot when it tried to boot back the regular kernel (now with the kdump initrd image specified in the menu.lst.)
Not sure why you would see the kdump initrd image in the menu.lst, it is just a parameter sent to kexec.
You might have more success filing a Red Hat bz (bugzilla.redhat.com), as the RHEL-5 kernel and kexec-tools are probably too old for discussion on this list.
Cheers,
Don
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Quoted 13 lines · Don Zickus
Quoted 11 lines · Jay Lan
Hi all,
I have a system running 2.6.18-238.12.1.el5 kernel. The kexec version is kexec-tools-1.102pre-126.el5_6.6.
The kernel was booted OK. Then it ran
/etc/init.d/kdumpand a new kdump initrd image was created.
A kernel crash was triggered. The kdump kernel was booted alright. However, it failed to boot when it tried to boot back the regular kernel (now with the kdump initrd image specified in the menu.lst.)
Quoted 3 lines
Not sure why you would see the kdump initrd image in the menu.lst, it is just a parameter sent to kexec.
Its actually not even passed to kexec, we build the initrd using the output of uname -a, or override it manually with an option in /etc/sysconfig/kdump. We don't ever mount the /boot partition, so /boot/grub/menu.lst shouldn't be accessible for re-writing.
Quoted 4 lines
You might have more success filing a Red Hat bz (bugzilla.redhat.com), as the RHEL-5 kernel and kexec-tools are probably too old for discussion on this list.
Agreed, initramfs construction is a distro specific operation, the upstream project doesn't contain bits on how to do that.
Neil
Quoted 7 lines
Cheers,
Don_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
Thanks to all who replied.
Our problem was resolved. It was caused by two different configuration issues:
1) As Don and Neil said, the kdump initrd img should not be in the menu.lst. Not sure why it was there at first place. So we changed the boot line to use the orignial initrd img.
2) We had multiple lines of "ext3 LABEL=xxx" and it guarantees at least one of them fail during mkdumprd and kdump not started properly.
All is fine now. Thanks to all who replied!
Jay
Quoted 21 lines · Neil Horman
Quoted 6 lines · Don Zickus
Quoted 5 lines · Jay Lan
Hi all,
I have a system running 2.6.18-238.12.1.el5 kernel. The kexec version is kexec-tools-1.102pre-126.el5_6.6.
Quoted 9 lines
Quoted 6 lines
The kernel was booted OK. Then it ran
/etc/init.d/kdumpand a new kdump initrd image was created.
A kernel crash was triggered. The kdump kernel was booted alright. However, it failed to boot when it tried to boot back the regular kernel (now with the kdump initrd image specified in the menu.lst.)Not sure why you would see the kdump initrd image in the menu.lst, it is just a parameter sent to kexec.
Its actually not even passed to kexec, we build the initrd using the output of uname -a, or override it manually with an option in
/etc/sysconfig/kdump. We don't ever mount the /boot partition, so/boot/grub/menu.lstshouldn't be accessible for re-writing.
Quoted 15 lines
Quoted 4 lines
You might have more success filing a Red Hat bz (bugzilla.redhat.com), as the RHEL-5 kernel and kexec-tools are probably too old for discussion on this list.
Agreed, initramfs construction is a distro specific operation, the upstream project doesn't contain bits on how to do that.
NeilQuoted 7 lines
Cheers,
Don_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec