Ignite-UX

Why "PXE-E18: Timeout. Server did not respond" trying to install through Ignite?

 
SOLVED
Go to solution
mpua
Frequent Advisor

Why "PXE-E18: Timeout. Server did not respond" trying to install through Ignite?

Hi, Im trying to install HP-UX through Ignite in a rx7620.
I've created a dbprofile in the EFI shell and then launched the "lanboot select -dn test" without problems, starting the installation.
In the middle of the installation i realized that i had configured badly the size of the filesystems so I decided to cancel it and reboot to start again.
So I acces the EFI shell again and now when executing the same command as before with the same dbprofile I get this error!:

PXE-E18: Timeout. Server did not respond

Whats happening???
3 REPLIES 3
S. Ney
Trusted Contributor
Solution

Re: Why "PXE-E18: Timeout. Server did not respond" trying to install through Ignite?

PXE-E18: Timeout. Server did not respond
That is a network timeout error. If you are running the exact same command as before and it was working the first time you tried, it may just be that for whatever reason your local network is busy.

When I had to ignite several servers I would get that error as well occasionally. I would try again and it would work. Even with specifying the MAC, IP, network etc in the db profile. I speculate its because of backend traffic and dhcp broadcasts that I couldn't see.
mpua
Frequent Advisor

Re: Why "PXE-E18: Timeout. Server did not respond" trying to install through Ignite?

Thanks, this is solved. I managed to lanboot and install HP-UX 11.31 on a SAN disk (IBM DS4800) but now i am facing another problem....

When I try to boot from this SAN disk i get a crash:

255/1/0 usb_ms_scsi
64000/0xfa00/0x6 esdisk
64000/0xfa00/0x7 esdisk
64000/0xfa00/0x8 esdisk
64000/0xfa00/0x9 esdisk
64000/0xfa00/0xa esdisk
gio: Error configuring root device using EFI hw paths

System Console is on the Built-In Serial Interface
AF_INET socket/streams output daemon running, pid 48
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - can't open device
WARNING: No swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend
VFS_MOUNTROOT error information:
0:(hfs) 6
1:(nfs) 223
9:(vxfs) 6
10:(nfs3) 223
11:(nfs4) 223
12:(autofs) 251
15:(cifs) 223
17:(dnlc_neg_fs) 251

Message buffer contents after system crash:

panic: VFS_MOUNTROOT: READ_ONLY: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000001e23420 vfs_mountroot+0x700
0xe0000000014c66c0 im_mountroot+0x40
0xe000000001e150c0 DoCalllist+0x390
End of Stack Trace

linkstamp: Wed Aug 25 03:53:05 EDT 2010
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
Calling function e0000000015c80c0 for Shutdown State 1 type 0x2
i 0 pfn 0x1 pages 0x7fffd
i 1 pfn 0x100000 pages 0x8fe000
i 2 pfn 0x4080000 pages 0x7f554
i 3 pfn 0x40ff5be pages 0x82
i 4 pfn 0x40ff67e pages 0x15e

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.


This is usually a crash due to the SCSI driver version, huh? But this is a SAN disk, not an internal disk.

What can I do?
S. Ney
Trusted Contributor

Re: Why "PXE-E18: Timeout. Server did not respond" trying to install through Ignite?