Red Hat Bugzilla – Bug 646720
localboot syntax is unusable under some new servers
Last modified: 2013-09-29 21:08:34 EDT
Description of problem:
After the timeout value passed cannot boot up the local hard disk. The system will hang or repeat PXE boot procedure endlessly.
Version-Release number of selected component (if applicable):
Just import a distro and using the default settings.
Steps to Reproduce:
1.Import a distro.
2.Restart the machine as the Cobbler client.
3.After timeout value passed.
The system will hang or repeat PXE boot procedure endlessly.
The system is booting up with the hard disk.
Actually this problem is due to LOCALBOOT 0 this syntax. Some servers we have test like IBM x3850 X5 and HP DL585 G7 server even some RHTS servers in the Beaker. We have found the solution, using chain.c32 module.
Here's instruction we did for this solution.
1.Using the latest syslinux package and using the latest NBP pxelinux.0.
2.Copy menu.c32 and chain.c32 to /tftpboot folder.
3.Modify the server specific configuration file under pxelinux.cfg/ and replace
APPEND hd0 0
Then the system will boot up the hard disk successfully.
However, we suppose that it's only a temporary solution by now 'cause after cobbler sync executed the cobbler template will recover the good configuration file. So is it possible to modify Cobbler codes then using chain.c32 to boot up the hard disk? Because "LOCALBOOT 0" really has a serious incompatibility problem with servers and that unable to add new servers to Beaker. Otherwise we can only modify some templates manually.
The template file that generates this should be /etc/cobbler/pxe/pxedefault.template and a few others in this directory. So this should be user modifiable.
Also, can we be sure that the new syntax works properly on all systems? From a quick read of the PXE standard and the syslinux documentation, it seems that localboot 0 should work on all boards that truly support PXE. It is supposed to unload the PXE environment and then continue on with the next boot device. So this seems like a bug with the BIOS of the boards that don't boot.
Considering the above, I think a documentation note and no change in the defaults that we ship. Does anyone disagree?
Actually we have changed all /etc/cobbler/pxe/pxedefault.template in our lab controller within module chain.c32. And the whole environment is running for about 2 months and no error reported at all.
So I suppose this way is a right method to handle some incompatibly problem.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.