Remote boot problem : can not load file

This is a discussion on Remote boot problem : can not load file within the Linux Networking forums, part of the Linux Forums category; Hi ! I and my Colleage are trying out to implement diskless Linux clinets i.e remote booting linux using BPbatch ...


Go Back   Usenet Forums > Linux Forums > Linux Networking

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 11-25-2005
tralsi@gmail.com
 
Posts: n/a
Default Remote boot problem : can not load file

Hi !
I and my Colleage are trying out to implement diskless Linux clinets
i.e remote booting linux using BPbatch

We have RedHat Linux 9, We are using built in DHCP & TFTP.

we have our files bpbtach (without .p extension as we are using ISC
based built-in DHCP server), and .ovl file & .hlp file available in
/tftpboot.

on client side we have Intel PXE 2.0 available.

Problem is : it connects to DHCP server fetches the IP address it
detects bootProm but it says can not open remote file. the exact
message on the client while booting is as under...

starting BpBatch - PXE BootROM detected.
BpBatch overlay loader v1.1 (February 11, 2000) overlay file
successfully loaded.

Mr. Batch Pre-boot batch processor v1.1 (February 11, 2000)

(c) .....

-BootProm detected using 132.147.160.151 (our Linux server address) as
standard TFTP server
- Advanced Poer Management V1.2
- Using upto 342K of conventional memory the heap
- Using upto 15296K of extended memory
- Direct disk write access enabled

EROR : [Open FILE] can not open remote file
Error in Bootstrap loader , line 1: can not load file


help me to deal with this. For better understanding the contents of my
dhcpd.conf are as under

not authoritative;
ddns-update-style none;

option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option PXE.discovery-control code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr code 7 = ip-address;

subnet 132.147.160.0 netmask 255.255.255.0
{

class "pxeclients"
{
match if substring (option vendor-class-identifier, 0,
9) = "PXEClient";
option vendor-class-identifier "PXEClient";
vendor-option-space PXE;
option PXE.mtftp-ip 0.0.0.0;

next-server 132.147.160.151;
}

host phobos
{
hardware ethernet 00:0D:61:6E:CC:97;
fixed-address 132.147.160.155;
filename "bpbatch";
}
}

Ultimately i can't boot. somehow it is not loading the file it wants to
boot..

Reply With Quote
  #2 (permalink)  
Old 11-25-2005
Hans-Juergen Lange
 
Posts: n/a
Default Re: Remote boot problem : can not load file

tralsi@gmail.com wrote:
> Hi !
> I and my Colleage are trying out to implement diskless Linux clinets
> i.e remote booting linux using BPbatch
>
> We have RedHat Linux 9, We are using built in DHCP & TFTP.
>
> we have our files bpbtach (without .p extension as we are using ISC
> based built-in DHCP server), and .ovl file & .hlp file available in
> /tftpboot.
>
> on client side we have Intel PXE 2.0 available.
>
> Problem is : it connects to DHCP server fetches the IP address it
> detects bootProm but it says can not open remote file. the exact
> message on the client while booting is as under...
>
> starting BpBatch - PXE BootROM detected.
> BpBatch overlay loader v1.1 (February 11, 2000) overlay file
> successfully loaded.
>
> Mr. Batch Pre-boot batch processor v1.1 (February 11, 2000)
>
> (c) .....
>
> -BootProm detected using 132.147.160.151 (our Linux server address) as
> standard TFTP server
> - Advanced Poer Management V1.2
> - Using upto 342K of conventional memory the heap
> - Using upto 15296K of extended memory
> - Direct disk write access enabled
>
> EROR : [Open FILE] can not open remote file
> Error in Bootstrap loader , line 1: can not load file
>

Hello,

you should find an entry in the logfiles giving the name of the file
that has been requested by the client.
Be aware that tftd runs in a directory and sees only the filesystem
from that point on. So dont use links to your kernel which point out of
the tree.
I did configured several diskless clients with different ways of
booting. But never used bpbatch.

BR
Hans-Juergen Lange
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 06:04 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0