Target Server Continuously Reboots To PXE And May Not Complete The Job
Article: 155
Applies to: All releases
This occurs when the target server is trying to local boot to the hard
drive but no bootable partition exists.
The reasons why this issue may occur are:
| • |
The target server was waiting on instructions from the Deployment Server
at initial deploy. Then the target server or the Deployment Server was
rebooted causing the connection between the target server
and Deployment Server to be broken. When the target server boots to PXE
again and reconnects to the Deployment Server, the server is now in
the Deployment Server database and considered a managed server. To
resolve this issue, schedule a job to install an operating system on
the target server or remove the target server from the Deployment Server
Console to allow it to connect back as a new server.
|
| • |
A job with a task to be run under automation followed by a task to be run under
the production operating system was executed on the target server. The job did
not complete and waited to execute the task under the production operating system.
To resolve this issue, from the Deployment Server console delete the running job,
schedule a job that installs an operating system on the target server, and
rerun the original job.
|
IMPORTANT: The target server may time out after a number of PXE boot attempts
and displays the message:
Non-System disk or disk error
replace and strike any key when ready
If this message is displayed, then press any key at the target server to
allow the server to boot to PXE and start the operating system installation job.
IMPORTANT: If the target platform is a VMware ESX virtual machine,
the virtual machine will halt and display the message:
Operating System not found
If this message is displayed, then the virtual machine will require a manual
reset to allow it to boot to PXE and start the operating system installation
job.
|
Printable version
