Re: diskless/pxe booting problem...

From: Wes Zuber (wes_at_uia.net)
Date: 10/14/03

  • Next message: Dave O: "Re: diskless/pxe booting problem..."
    Date: Tue, 14 Oct 2003 12:24:35 -0700
    To: Dave O <dso@mssystems.com>
    
    

    Are you sure that you have a kernel at /tmp ? Your config says that the
    root "/" for this boot is really at /tmp

    --Wes

    On Oct 14, 2003, at 12:09 PM, Dave O wrote:

    > I've been experiencing a problem getting a soekris to pxe boot
    > properly. I've tried this with both RELENG_4_8 and RELENG_4 and it
    > still gives me the same problem. I've read and re-read the diskless
    > operation, nfs, and freebsd booting process sections in the handbook,
    > as well as tried to read and understand both the rc.diskless[12]
    > scripts and the clone_root script.
    >
    > I'm exporting /tmp on the dhcp server since that was the only way I
    > could get the -alldirs option to work, though in retrospect, I don't
    > seem to need it. I've used both the clone_root method to create a
    > proper root to export, as well as using the method described in
    > jail(8). The soekris is able to pxe boot off of the server, but it
    > always hangs in the same spot. Does anyone have any idea what I
    > should be looking at? Here is my configuration. For the sake of
    > space, I didn't include the entire configuration files, only what I
    > believe is pertinent. If I should provide any more info, I'm welcome
    > to suggestions.
    >
    > /etc/exports
    > --------------------------------
    > /tmp -alldirs -ro -maproot=0:0 172.16.34.98 172.16.34.99
    >
    > /usr/local/etc/dhcpd.conf
    > --------------------------------
    > host soekris1 {
    > hardware ethernet 00:00:24:c1:2f:64;
    > fixed-address 172.16.34.98;
    > filename "pxeboot";
    > next-server 172.16.34.1;
    > option root-path "172.16.34.1:/tmp";
    > }
    >
    > host soekris2 {
    > hardware ethernet 00:00:24:c1:2f:84;
    > fixed-address 172.16.34.99;
    > filename "pxeboot";
    > next-server 172.16.34.1;
    > option root-path "172.16.34.1:/tmp";
    > }
    >
    >
    > /tmp/conf/base/etc/fstab && /tmp/etc/fstab
    > --------------------------------
    > # Device Mountpoint FStype Options Dump Pass#
    > 172.16.34.1:/tmp / nfs ro 0 0
    > proc /proc procfs rw 0 0
    >
    > /usr/src/sys/i386/conf/DISKLESS
    > --------------------------------
    > # Options for pxe booting
    > options BOOTP
    > options BOOTP_NFSROOT
    > options BOOTP_COMPAT
    > options NFS
    > options NFS_ROOT
    >
    > dmesg
    > --------------------------------
    > FreeBSD/i386 bootstrap loader, Revision 0.8
    > (root@stan.mssystems.com, Mon Oct 13 17:25:56 CDT 2003)
    > pxe_open: server addr: 172.16.34.1
    > pxe_open: server path: /tmp
    > pxe_open: gateway ip: 172.16.34.1
    > Loading /boot/defaults/loader.conf
    > /kernel text=0x1b91dd data=0x20a74+0x1f598 -
    > Copyright (c) 1992-2003 The FreeBSD Project.
    > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
    > 1994
    > The Regents of the University of California. All rights
    > reserved.
    >
    > [verbose dmesg snipped]
    >
    > bpf: lo0 attached
    > IPsec: Initialized Security Association Processing.
    > IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled
    > Sending DHCP Discover packet from interface sis0 (00:00:24:c1:2f:64)
    > Sending DHCP Discover packet from interface sis1 (00:00:24:c1:2f:65)
    > Sending DHCP Discover packet from interface sis2 (00:00:24:c1:2f:66)
    > Received DHCP Offer packet on sis0 from 172.16.34.1 (accepted) (no
    > root path)
    > Sending DHCP Request packet from interface sis0 (00:00:24:c1:2f:64)
    > Received DHCP Ack packet on sis0 from 172.16.34.1 (accepted) (got root
    > path)
    > DHCP timeout for interface sis1
    > DHCP timeout for interface sis2
    > sis0 at 172.16.34.98 server 172.16.34.1 boot file pxeboot
    > subnet mask 255.255.255.0 router 172.16.34.1 rootfs 172.16.34.1:/tmp
    > Adjusted interface sis0
    > Shutdown interface sis1
    > Shutdown interface sis2
    > Mounting root from nfs:172.16.34.1:/tmp
    > missing device name
    > setrootbyname failed
    > NFS ROOT: 172.16.34.1:/tmp
    >
    > _______________________________________________
    > freebsd-questions@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > To unsubscribe, send any mail to
    > "freebsd-questions-unsubscribe@freebsd.org"
    >
    >

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Dave O: "Re: diskless/pxe booting problem..."

    Relevant Pages

    • Re: 3620 boot from tftp
      ... DRAM configuration is 32 bits wide with parity disabled. ... 29K bytes of non-volatile configuration memory. ... Boot OK! ... interface FastEthernet0/0 ...
      (comp.dcom.sys.cisco)
    • Re: Is there a way to use Linux on the E450 ?
      ... have the brain damage of years of legacy crap (boot in first x cyls). ... configuration point for everything from display configuration to ... I know what some of the features are. ... probing of a given interface to delay until the device on that interface ...
      (comp.sys.sun.hardware)
    • Re: what user and password for cups
      ... If root account is not set (if you are using sudo ... All relevant configuration files are then ... I'd rather have *some* kind of restriction on who can use the cups web interface ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • RE: eth0 not starting on bootup
      ... Some times I find the simplest solution is to remove the configuration ... Use network ... the eth0 interface is now no longer ... > the interfaces that I have destined for startup will activate on boot. ...
      (RedHat)
    • Re: Proposed enhancements to MD
      ... the configuration for DM is userspace and the kernel ... You can always do the following: use a mini root fs on the partition ... bit with dd you have perfect working backups including the boot loader ...
      (Linux-Kernel)