Re: PXE booting 7.0-R

I've tried also specifing the IP for root-path, but as it seems, the hosts
defaults to server-name or next-server (these are the same for me), so it's not
neccessery to specify the IP in root-path.

Also the fileserver and the dhcp server are the same. You should have seen this
in the included config I gave.

Furthermore, meanwhile we've noticed that loader fails to get the pxe variables
when the onboard raid is enabled, and it notices the PXE environment when the
disks are not included in any RAID setups. Quite strange.

On Sun, 8 Jun 2008 22:54:18 -0700 (PDT)
mohammad khatibi <mo_kh118@xxxxxxxxx> wrote:

hi again
you said you use freebsd 7.0 so I told you to do these in freebsd ( that you
install dhcp on it!!! to the end I call it pxeserver) not on your Linux
Server(and to the end I call your server that you want to boot from and mount
its / FileServer)!!! your dhcpd.conf is :
host blade1 {
  hardware ethernet 00:30:48:8d:00:36;
  fixed-address 10.0.0.32;
  server-name "10.0.0.1";
I dont use it and nothing happend
  filename "/bsd/pxeboot";
you should place pxeboot where you specify as root-path and write here
"pxeboot"
  next-server 10.0.0.1;
  option root-path "/wwwbladebsd/";
you should specify your root-path as follow : [FileServer IP]:/
I use "/" because I couldn`t use any path and admonish you not to try
anywhere else because it doesn`t work!!!
}
after these you should edit inetd in your pxeserver (freebsd)
and you should make your pxeboot again if you want to use tftp that briefly
explain in that article please do above steps exactly and I hope you make
it !!! these are my 3 months of working on freebsd for pxeboot


----- Original Message ----
From: CZUCZY Gergely <gergely.czuczy@xxxxxxxxxxx>
To: mohammad khatibi <mo_kh118@xxxxxxxxx>
Cc: CZUCZY Gergely <phoemix@xxxxxxxxxxx>
Sent: Monday, June 9, 2008 8:56:47 AM
Subject: Re: PXE booting 7.0-R

On Sun, 8 Jun 2008 21:34:57 -0700 (PDT)
mohammad khatibi <mo_kh118@xxxxxxxxx> wrote:

Hi
try using this lines in your /usr/local/etc/dhcpd.conf instead of
yours : subnet [your subnet IP] netmask [your netmask] {
  range [start range] [finish range];
  next-server [your PXE server IP];
  filename "pxeboot";
  option root-path "[your Root server IP (if you mount your server
root its obvious that your server IP)]:/"; }
Yes, I was exactly using these options.


and you should make change in your /etc/inetd.conf and comment out
this line : tftp   dgram   udp wait    root    /usr/libexec/tftpd
tftpd -l -s /tftpboot/ place your pxeboot and loader in /tftpboot/
and reboot your system it should solve your problem
Sorry, but you've failed here.
1) I stated the NFS(also tftp) server is Linux, and I'm not using it
from inetd.
2) I wasn't asking how are _you_ doing it, the question was, what's
wrong with my setup. (After I know what's wrong I can fix it myself,
thanks)
3) I've read articles, manuals, etc. I have a problem with it, it's not
working as it's supposed to.

Anyways, thanks for your efforts.

but if you want to use tftp instead of nfs you should make your
pxeboot and loader using tftp enable to do this you can read this
article : http://www.ultradesic.com/index.php?section=72 but there is
a mistake in this article : after you make new files are place here :
pxeboot : /usr/obj/usr/src/sys/boot/i386/pxeldr/
loader : /usr/obj/usr/src/sys/boot/i386/loader/
and you should export / and all its directory for successful
loading . for more information you can read this article too.
http://www.ultradesic.com/?section=144 I hope you make it
----- Original Message ----
From: CZUCZY Gergely <phoemix@xxxxxxxxxxx>
To: freebsd-questions@xxxxxxxxxxx
Sent: Friday, June 6, 2008 1:17:08 PM
Subject: PXE booting 7.0-R

Hello,

I'm trying to PXE boot 7.0-RELEASE, but it stops at a time.

At boot I see the following on the screen:
BIOS drive C: is disk0
BIOS drive D: is disk1

PXE version 2.1, real mode entry point @9188:0106
BIOS 517kB/3406144kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
(toor@myplace, date)
pxe_open: server addr: 10.0.0.1
pxe_open: serve path: /wwwbladebsd/
pxe_open: gateway ip: 10.0.0.1
Consoles: internal video/keybaord
BIOS drive C: is disk0
BIOS drive D: is diskl
BIOS 517kB/3406144kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
(toor@myplace, date)
Can't work out which disk we are booting from.
Guessed BIOS device 0xffffffff not found by probes, defaulting to
disk0

can't loader 'kernel'

Type '?' for a list of commands, 'help' for more detailed help.
OK lsdev
cd devices:
disk devices:
disk0: BIOS drive C:
disk1: BIOS drive D:
pxe devices:

on the server I see t serving pxeboot via tftp, and mounting the root
via NFS: Jun  6 11:38:22 nfs dhcpd: DHCPDISCOVER from
00:30:48:8d:00:36 via eth1 Jun  6 11:38:22 nfs dhcpd: DHCPOFFER on
10.0.0.32 to 00:30:48:8d:00:36 via eth1 Jun  6 11:38:24 nfs dhcpd:
DHCPREQUEST for 10.0.0.32 (10.0.0.1) from 00:30:48:8d:00:36 via eth1
Jun  6 11:38:24 nfs dhcpd: DHCPACK on 10.0.0.32 to 00:30:48:8d:00:36
via eth1 Jun  6 11:38:24 nfs atftpd[2221]: Serving /bsd/pxeboot to
10.0.0.32:2070 Jun  6 11:38:24 nfs atftpd[2222]: Serving /bsd/pxeboot
to 10.0.0.32:2071 Jun  6 11:38:25 nfs dhcpd: DHCPDISCOVER from
00:30:48:8d:00:36 via eth1 Jun  6 11:38:25 nfs dhcpd: DHCPOFFER on
10.0.0.32 to 00:30:48:8d:00:36 via eth1 Jun  6 11:38:25 nfs dhcpd:
DHCPREQUEST for 10.0.0.32 (10.0.0.1) from 00:30:48:8d:00:36 via eth1
Jun  6 11:38:25 nfs dhcpd: DHCPACK on 10.0.0.32 to 00:30:48:8d:00:36
via eth1 Jun  6 11:38:25 nfs mountd[2120]: authenticated mount
request from 10.0.0.32:1023 for /wwwbladebsd (/wwwbladebsd) (around
30-40 from these NFS mount messages in the log).

The NFS server is a linux box right now.

The dhcpd.conf:
host blade1 {
  hardware ethernet 00:30:48:8d:00:36;
  fixed-address 10.0.0.32;
  server-name "10.0.0.1";
  filename "/bsd/pxeboot";
  next-server 10.0.0.1;
  option root-path "/wwwbladebsd/";
}

i'm using "atftpd" with /tftpboot as root directory. /tftpboot/bsd/
is a symlink to the root system's /boot .

I've NFS-exported /wwwbladebsd/, and that seems to work.

The question is, why loader is unable to load the kernel?
How could I force the loader to use tftp instead of NFS?

Or using any other solutions, how can I make this box boot?
If I've left out outsomething from here, please tell me, I will post
it.

Thanks in advance.






--
Üdvölettel,

Czuczy Gergely
Harmless Digital Bt
mailto: gergely.czuczy@xxxxxxxxxxx
Tel: +36-30-9702963

Attachment: signature.asc
Description: PGP signature

Relevant Pages

  • Re: PXE booting 7.0-R
    ... you said you use freebsd 7.0 so I told you to do these in freebsd (that you install dhcp on it!!! ... Subject: PXE booting 7.0-R ... I stated the NFS(also tftp) server is Linux, ... FreeBSD/i386 bootstrap loader, Revision 1.1 ...
    (freebsd-questions)
  • Re: diskless XPE by a PXE boot - HowTo?
    ... I guess startrom only knows "ntldr" file name. ... It downloads the loader from TFTP server. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Tftp server problem
    ... Actually we used this tftp server for IOS image coping in to routers ... Does your IP traffic go through a router? ...
    (comp.os.linux.hardware)
  • Re: Diskless Workstation Setup
    ... Diskless machine bios-> config to enable PXE booting. ... Server DHCP set up to give client appropriate IP addres and which file to ... get the pxeboot binary from the tftp server. ...
    (comp.unix.bsd.freebsd.misc)
  • PXE boot with TFTP
    ... I am trying to set up a jumpstart server using only dhcp/tftp/ftp to ... My tftp root is /var/tftp where I have created the boot ... load boot/kernel/acpi.ko ... Building the boot loader arguments ...
    (freebsd-questions)
Loading