bproc-users

[BProc] file unavailable: /var/bowulf/boot.img

[jeremy a. <arc...@co...>]

So I have been able to compile and install bproc-3.2.6, cmtools-1.2, and
beoboot-cm.1.5 with kernel 2.4.21.

But now I can't get beoboot to get the phase 2 image.

The error from the slave:
RARP: BPROC 2223; File 4711; file:/var/beowulf/boot.img
recv: <someline about backoff was here>
recv: resend listing on port 1024
recv: requesting /var/beowulf/boot.img from 192.168.36.110:4711
recv: response from server: /var/beowulf/boot.img : File unavailable
Boot image download failure


The error from the master:
> sudo beoserv -v
eth0: data socket 192.168.36.110:1847
beoserv: node_up listening at: /tmp/.node_up
beoserv: RARP: 00:C0:4F:6B:8C:7E == 192.168.36.50
192.168.36.50:1024 request filename=/var/beowulf/boot.img depth=0
resend_port=1024 fail=0.0.0.0:0
192.168.36.50:1024 response: status=100 addr=0.0.0.0:0 depth=0


Here are the commands to create the phase 1 and phase 2 images:
sudo beoboot -1 -f -k /boot/vmlinuz-2.4.21 -o /dev/fd0
sudo beoboot -2 -n -k /boot/vmlinuz-2.4.21 -o /var/beowulf/boot.img

I have not modified any of the /etc/beowulf/ files, nor exporting any NFS
directories from the master because I can't tell if I need to or not.

Any help would be appreciated.

-Jeremy

Re: [BProc] file unavailable: /var/bowulf/boot.img

[Joshua A. <lu...@ln...>]

On Tue, Sep 16, 2003 at 12:42:34AM +0100, jeremy archuleta wrote:
> 
> The error from the slave:
> RARP: BPROC 2223; File 4711; file:/var/beowulf/boot.img
> recv: <someline about backoff was here>
> recv: resend listing on port 1024
> recv: requesting /var/beowulf/boot.img from 192.168.36.110:4711
> recv: response from server: /var/beowulf/boot.img : File unavailable
> Boot image download failure

The one that usually bites me when I get this error is either the file
(in this case /var/beowulf/boot.img) doesn't exist (or can't be read).

> Here are the commands to create the phase 1 and phase 2 images:
> sudo beoboot -1 -f -k /boot/vmlinuz-2.4.21 -o /dev/fd0
> sudo beoboot -2 -n -k /boot/vmlinuz-2.4.21 -o /var/beowulf/boot.img

Try an ls -l /var/beowulf/boot.img to make sure it is there and readable
by the beoserv process.  Also, just beoboot -2 -n -k /boot/vmlinuz-2.4.21
should suffice assuming that the default config files specify the
bootfile.
ie:
bootfile /var/beowulf/phase2.img

Josh

Re: [BProc] file unavailable: /var/bowulf/boot.img

[Jeremy A. <arc...@co...>]

On Monday, Sep 15, 2003, at 17:34 US/Pacific, Joshua Aune wrote:

> On Tue, Sep 16, 2003 at 12:42:34AM +0100, jeremy archuleta wrote:
>>
>> The error from the slave:
>> RARP: BPROC 2223; File 4711; file:/var/beowulf/boot.img
>> recv: <someline about backoff was here>
>> recv: resend listing on port 1024
>> recv: requesting /var/beowulf/boot.img from 192.168.36.110:4711
>> recv: response from server: /var/beowulf/boot.img : File unavailable
>> Boot image download failure
>
> The one that usually bites me when I get this error is either the file
> (in this case /var/beowulf/boot.img) doesn't exist (or can't be read).
>
>> Here are the commands to create the phase 1 and phase 2 images:
>> sudo beoboot -1 -f -k /boot/vmlinuz-2.4.21 -o /dev/fd0
>> sudo beoboot -2 -n -k /boot/vmlinuz-2.4.21 -o /var/beowulf/boot.img
>
> Try an ls -l /var/beowulf/boot.img to make sure it is there and 
> readable
> by the beoserv process.

I know that exists. I am curious to know if I also need to set up a 
tftp server. In case I do, I have set one up with boot.img in both 
/tftpboot/ and /tftpboot/var/beowulf/ but this didn't help either. 
Tomorrow I will try again...

Thanks.
-J

Re: [BProc] file unavailable: /var/bowulf/boot.img

[<er...@he...>]

On Mon, Sep 15, 2003 at 07:35:37PM -0700, Jeremy Archuleta wrote:
> 
> 
> On Monday, Sep 15, 2003, at 17:34 US/Pacific, Joshua Aune wrote:
> 
> > On Tue, Sep 16, 2003 at 12:42:34AM +0100, jeremy archuleta wrote:
> >>
> >> The error from the slave:
> >> RARP: BPROC 2223; File 4711; file:/var/beowulf/boot.img
> >> recv: <someline about backoff was here>
> >> recv: resend listing on port 1024
> >> recv: requesting /var/beowulf/boot.img from 192.168.36.110:4711
> >> recv: response from server: /var/beowulf/boot.img : File unavailable
> >> Boot image download failure
> >
> > The one that usually bites me when I get this error is either the file
> > (in this case /var/beowulf/boot.img) doesn't exist (or can't be read).
> >
> >> Here are the commands to create the phase 1 and phase 2 images:
> >> sudo beoboot -1 -f -k /boot/vmlinuz-2.4.21 -o /dev/fd0
> >> sudo beoboot -2 -n -k /boot/vmlinuz-2.4.21 -o /var/beowulf/boot.img
> >
> > Try an ls -l /var/beowulf/boot.img to make sure it is there and 
> > readable
> > by the beoserv process.
> 
> I know that exists. I am curious to know if I also need to set up a 
> tftp server. In case I do, I have set one up with boot.img in both 
> /tftpboot/ and /tftpboot/var/beowulf/ but this didn't help either. 
> Tomorrow I will try again...

try adding the line

bootfile /var/beowulf/boot.img

to /etc/beowulf/config and restart beoserv.

- Erik

Re: [BProc] file unavailable: /var/bowulf/boot.img

[jeremy a. <arc...@co...>]

> try adding the line
> 
> bootfile /var/beowulf/boot.img
> 
> to /etc/beowulf/config and restart beoserv.
> 
> - Erik


Great. Thanks for the help.
The bootfile line in /etc/beowulf/config was the trick.

Now another error ; )

finished retransmitting
monte: kernel setup : 2650 bytes at 0x90000)
monte: kernel code : 1006138 bytes at 0x100000
couldn't find symbol real_mode_conf


any thoughts? bad kernel compile?
will try again from scratch....

-J

Re: [BProc] file unavailable: /var/bowulf/boot.img

[jeremy a. <arc...@co...>]

Quoting jeremy archuleta <arc...@co...>:

> > try adding the line
> > 
> > bootfile /var/beowulf/boot.img
> > 
> > to /etc/beowulf/config and restart beoserv.
> > 
> > - Erik
> 
> 
> Great. Thanks for the help.
> The bootfile line in /etc/beowulf/config was the trick.
> 
> Now another error ; )
> 
> finished retransmitting
> monte: kernel setup : 2650 bytes at 0x90000)
> monte: kernel code : 1006138 bytes at 0x100000
> couldn't find symbol real_mode_conf
> 
> 
> any thoughts? bad kernel compile?
> will try again from scratch....
> 
> -J


I found the following in the release notes:

beoboot-lanl 1.2 -----------------------------------------------------
This version should be used with BProc version 3.1.6+

There are some monte MONTE_PROTECTED related cleanups which require
that you patch the phase 1 beoboot kernel.  This is necessary because
the kernel normally throws away the information from the real mode
code after reading it.  It used to be possible to just find it at
90000h but boot loaders have begun putting that information at other
addresses.


and I have found a patch for kernel 2.4.17
monte/linux-2.4.17-save_real_mode_conf.patch

does this patch apply to 2.4.17 and newer, and thus be used for 2.4.21 (my
kernel)? If so, I assume 
"patch -p0 < beoboot-cm.1.5/monte/linux-2.4.17-save_real_mode_conf.patch" will work.

-J

Re: [BProc] file unavailable: /var/bowulf/boot.img

[Joshua A. <lu...@ln...>]

On Tue, Sep 16, 2003 at 06:38:50PM +0100, jeremy archuleta wrote:
> > Great. Thanks for the help.
> > The bootfile line in /etc/beowulf/config was the trick.
> > 
> > Now another error ; )
> > 
> > finished retransmitting
> > monte: kernel setup : 2650 bytes at 0x90000)
> > monte: kernel code : 1006138 bytes at 0x100000
> > couldn't find symbol real_mode_conf
> > 
> > 
> > any thoughts? bad kernel compile?
> > will try again from scratch....

Like you discovered, probably missing the 2k monte stuff.
> 
> 
> I found the following in the release notes:
> 
> and I have found a patch for kernel 2.4.17
> monte/linux-2.4.17-save_real_mode_conf.patch
> 
> does this patch apply to 2.4.17 and newer, and thus be used for 2.4.21 (my
> kernel)? If so, I assume 
> "patch -p0 < beoboot-cm.1.5/monte/linux-2.4.17-save_real_mode_conf.patch" will work.
> 

I have one from 2.4.20 that I am currently using with 2.4.21 and higher
kernels.  Attached.  Also remember to select the save real mode option
in your phase1 kernel .config file after patching.

Josh