Re: Running OS tftp vs. pxeboot tftp
Thanks for your feedback. I agree that separating the networks and isolating the build network thus eliminating the need for VLAN tagging is the ideal scenario. Unfortunately, influencing those changes are beyond my sphere of influence in this particular case. At the end of the day, our solution was to replace pxeboot.bs with Grub2pxe. I have a blog post detailing the scenario at https://hostileadmin.wordpress.com/2012/05/04/pxe-booting-into-a-freebsd-installation/ On Wed, Mar 14, 2012 at 9:30 AM, Erik Nørgaard norga...@locolomo.org wrote: Hi On 14/03/2012 11:44, Rick Miller wrote: I thought I would follow up on this as a couple individuals expressed an interest in it... We have isolated the configuration in which this occurs under. It occurs during the execution of pxeboot.bs on brocade switches with vlan tagging enabled. You might save yourself time and money buying a cheap switch and doing your jumpstart install on a separate closed network completely isolated from the rest of your networks, without VLAN tagging required. If you have lots of nodes to install it makes sense to maintain your own repository of freebsd and packages, and it's good practice to keep your preproduction systems separate from production, so there is no need for network access. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Running OS tftp vs. pxeboot tftp
I thought I would follow up on this as a couple individuals expressed an interest in it... We have isolated the configuration in which this occurs under. It occurs during the execution of pxeboot.bs on brocade switches with vlan tagging enabled. We have begun to review the pxeboot.bs source code in order to get more debug information out of it and have opened a support case with Brocade. On Thu, Mar 1, 2012 at 10:16 AM, Rick Miller vmil...@hostileadmin.com wrote: Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. -- Take care Rick Miller -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Running OS tftp vs. pxeboot tftp
Hi On 14/03/2012 11:44, Rick Miller wrote: I thought I would follow up on this as a couple individuals expressed an interest in it... We have isolated the configuration in which this occurs under. It occurs during the execution of pxeboot.bs on brocade switches with vlan tagging enabled. You might save yourself time and money buying a cheap switch and doing your jumpstart install on a separate closed network completely isolated from the rest of your networks, without VLAN tagging required. If you have lots of nodes to install it makes sense to maintain your own repository of freebsd and packages, and it's good practice to keep your preproduction systems separate from production, so there is no need for network access. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Running OS tftp vs. pxeboot tftp
From: Rick Miller vmil...@hostileadmin.com To: Erik Nørgaard norga...@locolomo.org; freebsd-questions@freebsd.org Sent: Sunday, March 4, 2012 3:51 PM Subject: Re: Running OS tftp vs. pxeboot tftp Hi Erik, Thanks for getting back to me. The original problem is the same issue...we are still working it, but we've isolated the configuration where the issue manifests itself. It has to do with the FreeBSD pxeboot and Brocade switches. We will continue troubleshooting in our lab. When we've identified a fix/workaround I will be sure to follow up here. On 3/4/12, Erik Nørgaard norga...@locolomo.org wrote: On 01/03/2012 16:16, Rick Miller wrote: Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I have no reason to believe there should be any difference. If you believe there is a problem with the supplied pxeboot, you can compile your own. You previusly wrote about VLAN tagging for your pxeboot nodes, but never wrote back if you solved the problem. What's your setup? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. You should have some log or other traces to debug on the problem, can't help much without. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Sent from my mobile device Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I can't speak to all the technical nuiances you reference here but I have a diskless booting system which runs 8.2-STABLE and it's been running flawless for several months. I last did make buildworld on the server's os and the diskless's boot partition in December...all is well for me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Running OS tftp vs. pxeboot tftp
Hi Erik, Thanks for getting back to me. The original problem is the same issue...we are still working it, but we've isolated the configuration where the issue manifests itself. It has to do with the FreeBSD pxeboot and Brocade switches. We will continue troubleshooting in our lab. When we've identified a fix/workaround I will be sure to follow up here. On 3/4/12, Erik Nørgaard norga...@locolomo.org wrote: On 01/03/2012 16:16, Rick Miller wrote: Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I have no reason to believe there should be any difference. If you believe there is a problem with the supplied pxeboot, you can compile your own. You previusly wrote about VLAN tagging for your pxeboot nodes, but never wrote back if you solved the problem. What's your setup? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. You should have some log or other traces to debug on the problem, can't help much without. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Sent from my mobile device Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
Hi, I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the network, to install other machines (and do fixups etc.) I set this up as we setup previous versions here - but setting up a tftp server, and nfs server - and 'dumping' the contents of the install CD to a directory on the dhcp server, which is exported via nfs (it's exported as read/write). The system kind of boots, but falls over with: Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 Entropy harvesting: interrupts ethernet point_to_pick kickstart. Starting file system checks: mount_nfs: no host:dirpath nfs-name Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: It looks like it's failing to 'remount' / promote the root file system as read/write (It's definitely exported as read/write - I've tested it by mounting it on another machine). If you start a shell at this point and run mount, you get: 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) devfs on /dev (devfs, local, multilabel) Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix this? Previous systems setup this way would always boot through to the sysinstall menu. Thanks, -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
Take a look at freebsd-hackers mailing list... I have suggested some change in some Makefile and sh script in order to unless at this moment to be able to have an unattended system built with sysinstall (the idea I think it was to maintain sysinstall in 9.0 unless) and using you're install.cfg At freebsd-hackers seems that people is pretty busy and can't look at this in order for committing or unless saying something about it... perhaps they're working on another thing or so, or don't know I assume they can't check this now... but like changes are not significant... I am going to do with the changes suggested and have tested and release builts fine and you can use Jumpstart without issues.. this way... So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! El Jue, 1 de Marzo de 2012, 11:24 am, Karl Pielorz escribió: Hi, I've got a 9.0-R amd64 system I'm trying to netboot / pxeboot from the network, to install other machines (and do fixups etc.) I set this up as we setup previous versions here - but setting up a tftp server, and nfs server - and 'dumping' the contents of the install CD to a directory on the dhcp server, which is exported via nfs (it's exported as read/write). The system kind of boots, but falls over with: Interface em0 IP-Address 192.168.0.47 Broadcast 192.168.0.255 Entropy harvesting: interrupts ethernet point_to_pick kickstart. Starting file system checks: mount_nfs: no host:dirpath nfs-name Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Mar 1 118:10 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: It looks like it's failing to 'remount' / promote the root file system as read/write (It's definitely exported as read/write - I've tested it by mounting it on another machine). If you start a shell at this point and run mount, you get: 192.168.0.37:/usr2/netboot/os/9.0-amd64 on / (nfs, read-only) devfs on /dev (devfs, local, multilabel) Is there something I have to set (e.g. in '/etc/rc.conf') in order to fix this? Previous systems setup this way would always boot through to the sysinstall menu. Thanks, -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
--On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Just commenting out that line, i.e. #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Means the boot now completes, and I get offered the Install / Shell / Live CD prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Running OS tftp vs. pxeboot tftp
Hi All, Are there significant differences in the implementation between the tftp client in FreeBSD 8.2-RELEASE and the client implementation in pxeboot.bs? I ask because I have encountered a scenario where pxeboot.bs is tftp'ing boot files from a PXE server and fails in random spots while attempting to download boot files to start a 8.2-RELEASE install. When we run the same sequence of tftp gets in a running 8.2-RELEASE instance continuously, we never received a single failure in a solid hour of attempts. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9-R pxeboot fails with 'Mounting root filesystem rw failed'...
In the new way of booting... you need to have the cd because the own cd is the root filesystem... and in fact is live filesystem too so unless you're booting from mfsroot... I assume you should have that line in /etc/fstab inside the iso image but if you're using mfsroot... I really even am not creating etc dir inside the iso image... because it's not needed and in previous releases and iso images when always booted from mfsroot (and where not livefs cds and so) it wasn't necessary... On Thu, 01 Mar 2012 12:43:58 +, Karl Pielorz wrote: --On 01 March 2012 11:53 +0100 ego...@ramattack.net wrote: So I recomend you reading last mails of mine in freebsd-hackers... Hope it helps, Bye! For what it's worth - I've resolved the issue I had (which was basically the system booted, but failed trying to re-mount root as RW, and hence wouldn't go into the installer). The fix I did was to change the '/etc/fstab' on the Netboot server (i.e. the copy of FreeBSD that you're booting). It contains: /dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Just commenting out that line, i.e. #/dev/iso9660/FREEBSD_INSTALL / cd9660 ro 0 0 Means the boot now completes, and I get offered the Install / Shell / Live CD prompt, instead of an error about not being able to remount root. I've yet to complete an install this way (so far we're just using a script to extract the new 9.x style '.txz' files). But that little change does let us netboot correctly now, enough for what we need. -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
zfs clone, nfs and pxeboot
Hi, I wanted to experiment a bit with pxeboot. Therefore I created a zfs clone of a jail filesystem. The clone was shared as via nfs. Pxeboot complained that it can't load the kernel. The pxeboot ls command gave some correct and some really messed up filenames. I then deleted the clone and copied the filesystem (in the same zpool) using zfs send ... | zfs receive ... If I share this new filesystem via nfs, pxeboot doesn't have the messed up filename problem and everything works as expected. Is there some known problems with zfs clones and nfs ? Just for information, this was tested on FreeBSD 8.2 amd64 (not the machine were I have problems in the other thread) Thanks in advance, Bye, David Arendt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: zfs clone, nfs and pxeboot
On 28 July 2011 11:41, ad...@prnet.org wrote: Hi, I wanted to experiment a bit with pxeboot. Therefore I created a zfs clone of a jail filesystem. The clone was shared as via nfs. Pxeboot complained that it can't load the kernel. The pxeboot ls command gave some correct and some really messed up filenames. I then deleted the clone and copied the filesystem (in the same zpool) using zfs send ... | zfs receive ... If I share this new filesystem via nfs, pxeboot doesn't have the messed up filename problem and everything works as expected. Is there some known problems with zfs clones and nfs ? Just for information, this was tested on FreeBSD 8.2 amd64 (not the machine were I have problems in the other thread) Thanks in advance, Bye, David Arendt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org you can get the kernel modules to be fetched via tftp, does it work with that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: zfs clone, nfs and pxeboot
Hi, yes, I know, but it would be interesing to know if there is a general problem with zfs clones shared over nfs or if it is pxeboot related. Bye, David Arendt On 07/28/11 13:10, krad wrote: On 28 July 2011 11:41,ad...@prnet.org wrote: Hi, I wanted to experiment a bit with pxeboot. Therefore I created a zfs clone of a jail filesystem. The clone was shared as via nfs. Pxeboot complained that it can't load the kernel. The pxeboot ls command gave some correct and some really messed up filenames. I then deleted the clone and copied the filesystem (in the same zpool) using zfs send ... | zfs receive ... If I share this new filesystem via nfs, pxeboot doesn't have the messed up filename problem and everything works as expected. Is there some known problems with zfs clones and nfs ? Just for information, this was tested on FreeBSD 8.2 amd64 (not the machine were I have problems in the other thread) Thanks in advance, Bye, David Arendt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org you can get the kernel modules to be fetched via tftp, does it work with that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
PXEBOOT based upgrade/install
Hi all! I'm new in these parts, but not new to *nix. I'm trying to upgrade a system with FreeBSD 5.4 to 7.2. I've gotten the pxeboot to work, but somehow the network interface isn't seen by the installer. loader.rc: === include /boot/loader.4th include /boot/beastie.4th \ Reads and processes loader.conf variables start load /boot/kernel/kernel load -t mfs_root /boot/mfsroot set vfs.root.mountfrom=ufs:/dev/md0c boot loader.conf: mfsroot_load=YES mfsroot_type=mfs_root mfsroot_name=/boot/mfsroot if_bge_load=yes I added the if_bge line at that seems to be the module used on 5.4. Any other leads? Thanks in advance Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PXEBOOT based upgrade/install
If you're going to setup a netbooting server (congrats!), why are you trying to limit yourself to what seems to be the bootonly CD? There are some people who complain about broadcom cards, in the fact that they're buggy support/nonexistant support. Maybe your NIC chipset is one of those. The loader.rc is told to mount a memory filesystem from ufs formatted disk located at /dev/md0c (a memory disk that is populated from the previous line, a file-based filesystem). So your system wouldn't be able to hit sysinstall or the /etc files (as I'm seeing the boot process) to do the install or configuration. Overall, what's to stop you from doing a diskless boot? the handbook makes it for a multi-PC setup, but for a single setup, it's quite easy. On 6/18/09, Bruce Ferrell bferr...@baywinds.org wrote: Hi all! I'm new in these parts, but not new to *nix. I'm trying to upgrade a system with FreeBSD 5.4 to 7.2. I've gotten the pxeboot to work, but somehow the network interface isn't seen by the installer. loader.rc: === include /boot/loader.4th include /boot/beastie.4th \ Reads and processes loader.conf variables start load /boot/kernel/kernel load -t mfs_root /boot/mfsroot set vfs.root.mountfrom=ufs:/dev/md0c boot loader.conf: mfsroot_load=YES mfsroot_type=mfs_root mfsroot_name=/boot/mfsroot if_bge_load=yes I added the if_bge line at that seems to be the module used on 5.4. Any other leads? Thanks in advance Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PXEBOOT based upgrade/install
Tim Judd wrote: If you're going to setup a netbooting server (congrats!), why are you trying to limit yourself to what seems to be the bootonly CD? Uh... 'cause I don't know any better? :) Point me to docs so I can do better! There are some people who complain about broadcom cards, in the fact that they're buggy support/nonexistant support. Maybe your NIC chipset is one of those. I don't know about that. This is in a Dell Power Edge 850 running FreeBSD 5.4. The loader.rc is told to mount a memory filesystem from ufs formatted disk located at /dev/md0c (a memory disk that is populated from the previous line, a file-based filesystem). So, I need to get rid of the set line? before I added that (done by rote from googeling) I was getting a panic about no init. So your system wouldn't be able to hit sysinstall or the /etc files (as I'm seeing the boot process) to do the install or configuration. Overall, what's to stop you from doing a diskless boot? the handbook makes it for a multi-PC setup, but for a single setup, it's quite easy. I need the stuff on the local disk as it runs an application that needs local postgres and other stuff. Yes, I could put it elsewhere, but it would mean flying 5 hours to do it. Rather just do an upgrade. On 6/18/09, Bruce Ferrell bferr...@baywinds.org wrote: Hi all! I'm new in these parts, but not new to *nix. I'm trying to upgrade a system with FreeBSD 5.4 to 7.2. I've gotten the pxeboot to work, but somehow the network interface isn't seen by the installer. loader.rc: === include /boot/loader.4th include /boot/beastie.4th \ Reads and processes loader.conf variables start load /boot/kernel/kernel load -t mfs_root /boot/mfsroot set vfs.root.mountfrom=ufs:/dev/md0c boot loader.conf: mfsroot_load=YES mfsroot_type=mfs_root mfsroot_name=/boot/mfsroot if_bge_load=yes I added the if_bge line at that seems to be the module used on 5.4. Any other leads? Thanks in advance Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PXEBOOT based upgrade/install
Bruce Ferrell wrote: Hi all! I'm new in these parts, but not new to *nix. I'm trying to upgrade a system with FreeBSD 5.4 to 7.2. I've gotten the pxeboot to work, but somehow the network interface isn't seen by the installer. loader.rc: === include /boot/loader.4th include /boot/beastie.4th \ Reads and processes loader.conf variables start load /boot/kernel/kernel load -t mfs_root /boot/mfsroot set vfs.root.mountfrom=ufs:/dev/md0c boot loader.conf: mfsroot_load=YES mfsroot_type=mfs_root mfsroot_name=/boot/mfsroot if_bge_load=yes I added the if_bge line at that seems to be the module used on 5.4. Any other leads? I wrote a guide years ago, it hasn't been updated since 6.2, but for this stage I don't think there are any changes. http://www.locolomo.org/pub/pxeboot/index.html It also explains how to build your own custom mfsroot. Does the kernel support tftp and/or nfs? is your mfsroot actually fetched from the server? BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: PXEBOOT based upgrade/install
As a very brief instruction to setup a single-PC diskless boot (because of the pid files, mostly. But files in /etc are also the same concern) do the following on your NFS exported filesystems.. cd /path/to/installation/medium cd 7.2-RELEASE/kernels cat generic.?? | tar --unlink -xpzf - -C /path/to/exported/mountpoint cd ../base cat base.?? | tar --unlink -xpzf - -C /path/to/exported/mountpoint Add some NFS server functionality (file locking [for editing /etc/passwd], mostly) by adding to the server's rc.conf and starting the services: rpc_statd_enable=YES rpc_lockd_enable=YES Create the client's files: /etc/fstab /etc/rc.conf The client ALSO needs statd and lockd in order for file locking to work... don't forget to add it. And create optionally the serial console ability as outlined in the handbook. My ALIX (aka new PC Engines' WRAP boards) routers both have this diskless setup. If you're running it off Compact Flash, keep in mind the limited write cycles. I have them both running off Microdrives now (1 hard disks at 3600RPM) If anyone gets stuck, as I'm writing this from memory while I'm at work, let me know. I'll double check my config at home and update it if I need to. This does not add the manpages, the source files, ports, or anything. It's the same as sysinstall's minimal config. This will boot to a Multi-User Interface (MUI) and you can run sysinstall after logging in with root with no password. On 6/18/09, Bruce Ferrell bferr...@baywinds.org wrote: Tim Judd wrote: If you're going to setup a netbooting server (congrats!), why are you trying to limit yourself to what seems to be the bootonly CD? Uh... 'cause I don't know any better? :) Point me to docs so I can do better! There are some people who complain about broadcom cards, in the fact that they're buggy support/nonexistant support. Maybe your NIC chipset is one of those. I don't know about that. This is in a Dell Power Edge 850 running FreeBSD 5.4. The loader.rc is told to mount a memory filesystem from ufs formatted disk located at /dev/md0c (a memory disk that is populated from the previous line, a file-based filesystem). So, I need to get rid of the set line? before I added that (done by rote from googeling) I was getting a panic about no init. So your system wouldn't be able to hit sysinstall or the /etc files (as I'm seeing the boot process) to do the install or configuration. Overall, what's to stop you from doing a diskless boot? the handbook makes it for a multi-PC setup, but for a single setup, it's quite easy. I need the stuff on the local disk as it runs an application that needs local postgres and other stuff. Yes, I could put it elsewhere, but it would mean flying 5 hours to do it. Rather just do an upgrade. On 6/18/09, Bruce Ferrell bferr...@baywinds.org wrote: Hi all! I'm new in these parts, but not new to *nix. I'm trying to upgrade a system with FreeBSD 5.4 to 7.2. I've gotten the pxeboot to work, but somehow the network interface isn't seen by the installer. loader.rc: === include /boot/loader.4th include /boot/beastie.4th \ Reads and processes loader.conf variables start load /boot/kernel/kernel load -t mfs_root /boot/mfsroot set vfs.root.mountfrom=ufs:/dev/md0c boot loader.conf: mfsroot_load=YES mfsroot_type=mfs_root mfsroot_name=/boot/mfsroot if_bge_load=yes I added the if_bge line at that seems to be the module used on 5.4. Any other leads? Thanks in advance Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
Wojciech Puchar wrote: I couldn't find the hostname sent by dhcp, but found a way to find the ip address. just use hostname command. I did, but the answer is empty (remember this is before /etc/rc is run). Where is kept the data received by dhcp_client during pxe boot ? The only problem i have is that the echo done and other standard outputs are not visible in /var/log/messages. How can i keep them either in dmesg or /var/log/messages ? add second echo to /var/log/messages ;) Hope not to forget one ;-) But is there a system call or configuration to do that automatically ? I can see some echo in /etc/rc without any , and their result seems to go to /var/messages. I wish to learn to do clean scripting :-) Best regards, -- Bernard DUGAS Mobile +33 615 333 770 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
add second echo to /var/log/messages ;) Hope not to forget one ;-) But is there a system call or configuration to do that automatically ? I can see some echo in /etc/rc without any , and their result seems to go to /var/messages. I wish to learn to do clean scripting :-) actually i don't know how it's done in stardard rc scripts ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
Hello, Wojciech Puchar wrote: i already did such things but with NetBSD 1.5 for my Xterminal distro. it's simple: mount / readonly, put everything here. in /etc put /etc/rc consisting only #!/bin/sh exec /systemrc in /systemrc put something like that: #!/bin/sh echo -n Mounting workstation config directory... #get your IP or MAC address using ifconfig,grep,cut,awk,how you like #put to to say MYIP /sbin/mount_nfs yournfsserver:/clients/etc/MYIP /etc echo done exec /etc/rc Thank you very much, it is now running well after some hardware adventure. I couldn't find the hostname sent by dhcp, but found a way to find the ip address. The only problem i have is that the echo done and other standard outputs are not visible in /var/log/messages. How can i keep them either in dmesg or /var/log/messages ? Best regards, -- Bernard DUGAS Mobile +33 615 333 770 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
Thank you very much, it is now running well after some hardware adventure. I couldn't find the hostname sent by dhcp, but found a way to find the ip address. just use hostname command. The only problem i have is that the echo done and other standard outputs are not visible in /var/log/messages. How can i keep them either in dmesg or /var/log/messages ? add second echo to /var/log/messages ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
On 12/16/08, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: it's simple: More simple when you tell it ;-) Thanks a lot, i will try it tonight ! it doesn't have chance - must work :) I wish it's helpful, doing this doesn't just save space but saves time - you have to upgrade software once. So preserving consistency, which is the most important when you have lot of diskless stations ! exactly. i'm using just NetBSD 1.5 (uses LITTLE memory) + Xserver, so there are almost no updates, but anyway - it's stored once. you may like to make /etc-common directory and put most of files there, and symlinks in each station's /etc In fact, it makes me think that we miss a concept in mount, or at least i don't know it currently : imagine a -tl (TransparentLayer) option for mount, allowing to mount multiple source to the same directory, for instance /etc : there is already such think - mount_unionfs but i don't use it. if you mount over some directory - it's original contents (like my /etc/rc doing exec /systemrc) gets hidden. mount -r yournfsserver:/basic/etc /etc mount -tl -r yournfsserver:/TypeX/etc /etc mount -tl -r yournfsserver:/StationY/etc /etc mount_unionfs but i don't know how stable it is. When you want to change something, you add a rw TransparentLayer : mount -tl yournfsserver:/StationYchanges/etc /etc So that changed or added files are only stored in this rw partition, thus very small and easy to manage. This would be a kind of partition inheritance, like in object languages... Dreams are allowed :-) try mount_unionfs and mount_nullfs -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
Wojciech Puchar wrote: mount_unionfs but i don't know how stable it is. Thanks to fill my dreams :-) The dream is close, but still a dream :-( http://www.freebsd.org/cgi/man.cgi?query=mount_unionfssektion=8apropos=0manpath=FreeBSD+7.0-RELEASE BUGS THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. Sad not to be a coder... Best regards, -- Bernard DUGAS Mobile +33 615 333 770 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
on NFS server. Lot of root directories can be shared and mounted in fstab, after booting process : /usr, /home... In current solution, the minimum root directories i had to keep for managing to boot are : bin libexec sbin boot etc lib i already did such things but with NetBSD 1.5 for my Xterminal distro. it's simple: mount / readonly, put everything here. in /etc put /etc/rc consisting only #!/bin/sh exec /systemrc in /systemrc put something like that: #!/bin/sh echo -n Mounting workstation config directory... #get your IP or MAC address using ifconfig,grep,cut,awk,how you like #put to to say MYIP /sbin/mount_nfs yournfsserver:/clients/etc/MYIP /etc echo done exec /etc/rc please then add: /tmp, /var/tmp, /var/run, possibly /var/log as tmpfs in fstab OR mount it with per-station directory the same way as /etc I wish it's helpful, doing this doesn't just save space but saves time - you have to upgrade software once. you may like to make /etc-common directory and put most of files there, and symlinks in each station's /etc ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Optimising pxeboot disk size
Hi, I'm working on a project to have many diskless clients PXEbooting on 1 nfs server. This works now, but i would like to have a more efficient use of disk space on NFS server. Lot of root directories can be shared and mounted in fstab, after booting process : /usr, /home... In current solution, the minimum root directories i had to keep for managing to boot are : bin libexec sbin boot etc lib But it appears that only /etc is really specific to each diskless clientX, having basically fstab and rc.conf inside. All other directories could be shared, and specifically /boot which is more that 100MO : i would prefer not to duplicate it, as 10 servers would mean 1GO for nothing. Please would anybody help find a way to share all what we can during boot process ? Another way to ask the question is : how can we mount / and then /etc at the begining of boot process instead of mounting only / with etc inside ? I have tried to do links, but no way to make the boot process follow them... Thanks a lot, Best regards, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
it's simple: More simple when you tell it ;-) Thanks a lot, i will try it tonight ! it doesn't have chance - must work :) I wish it's helpful, doing this doesn't just save space but saves time - you have to upgrade software once. So preserving consistency, which is the most important when you have lot of diskless stations ! exactly. i'm using just NetBSD 1.5 (uses LITTLE memory) + Xserver, so there are almost no updates, but anyway - it's stored once. you may like to make /etc-common directory and put most of files there, and symlinks in each station's /etc In fact, it makes me think that we miss a concept in mount, or at least i don't know it currently : imagine a -tl (TransparentLayer) option for mount, allowing to mount multiple source to the same directory, for instance /etc : there is already such think - mount_unionfs but i don't use it. if you mount over some directory - it's original contents (like my /etc/rc doing exec /systemrc) gets hidden. mount -r yournfsserver:/basic/etc /etc mount -tl -r yournfsserver:/TypeX/etc /etc mount -tl -r yournfsserver:/StationY/etc /etc mount_unionfs but i don't know how stable it is. When you want to change something, you add a rw TransparentLayer : mount -tl yournfsserver:/StationYchanges/etc /etc So that changed or added files are only stored in this rw partition, thus very small and easy to manage. This would be a kind of partition inheritance, like in object languages... Dreams are allowed :-) try mount_unionfs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
Wojciech Puchar wrote: i already did such things but with NetBSD 1.5 for my Xterminal distro. it's simple: More simple when you tell it ;-) Thanks a lot, i will try it tonight ! I wish it's helpful, doing this doesn't just save space but saves time - you have to upgrade software once. So preserving consistency, which is the most important when you have lot of diskless stations ! you may like to make /etc-common directory and put most of files there, and symlinks in each station's /etc In fact, it makes me think that we miss a concept in mount, or at least i don't know it currently : imagine a -tl (TransparentLayer) option for mount, allowing to mount multiple source to the same directory, for instance /etc : mount -r yournfsserver:/basic/etc /etc mount -tl -r yournfsserver:/TypeX/etc /etc mount -tl -r yournfsserver:/StationY/etc /etc A file is first look for in yournfsserver:/StationY/etc, then in yournfsserver:/TypeX/etc and finally in yournfsserver:/basic/etc. This means that StationX will see in its /etc firts its specific files, then the files dedicated to TypeX station (webserver, dns server, workstation,...) and then all basic files unchanged from standard distribution. When you want to change something, you add a rw TransparentLayer : mount -tl yournfsserver:/StationYchanges/etc /etc So that changed or added files are only stored in this rw partition, thus very small and easy to manage. This would be a kind of partition inheritance, like in object languages... Dreams are allowed :-) Thanks a lot, Best regards, -- Bernard DUGAS Mobile +33 615 333 770 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
Paul B. Mahol wrote: On 12/16/08, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: When you want to change something, you add a rw TransparentLayer : mount -tl yournfsserver:/StationYchanges/etc /etc So that changed or added files are only stored in this rw partition, thus very small and easy to manage. This would be a kind of partition inheritance, like in object languages... Dreams are allowed :-) try mount_unionfs and mount_nullfs Thanks Paul, FreeBSD has always hidden treasures :-) MOUNT_NULLFS(8) doc is very detailled, but i can't find how to use it for my problem : being able to go from common shared configuration to specific private configuration. unionfs looks very close to my dream, but it is currently not available for production :-( Best regards, -- Bernard DUGAS Mobile +33 615 333 770 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
MOUNT_NULLFS(8) doc is very detailled, but i can't find how to use it for my problem : being able to go from common shared configuration to specific you can't - nullfs doesn't do this. use symlinks /etc containing tons of links to /sharedetc and few files instead of symlink - for those that are different. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
On Tue, 2008-12-16 at 15:02 +0100, Bernard Dugas wrote: Wojciech Puchar wrote: i already did such things but with NetBSD 1.5 for my Xterminal distro. it's simple: More simple when you tell it ;-) Thanks a lot, i will try it tonight ! I wish it's helpful, doing this doesn't just save space but saves time - you have to upgrade software once. So preserving consistency, which is the most important when you have lot of diskless stations ! you may like to make /etc-common directory and put most of files there, and symlinks in each station's /etc In fact, it makes me think that we miss a concept in mount, or at least i don't know it currently : imagine a -tl (TransparentLayer) option for mount, allowing to mount multiple source to the same directory, for instance /etc : mount -r yournfsserver:/basic/etc /etc mount -tl -r yournfsserver:/TypeX/etc /etc mount -tl -r yournfsserver:/StationY/etc /etc A file is first look for in yournfsserver:/StationY/etc, then in yournfsserver:/TypeX/etc and finally in yournfsserver:/basic/etc. This means that StationX will see in its /etc firts its specific files, then the files dedicated to TypeX station (webserver, dns server, workstation,...) and then all basic files unchanged from standard distribution. When you want to change something, you add a rw TransparentLayer : mount -tl yournfsserver:/StationYchanges/etc /etc So that changed or added files are only stored in this rw partition, thus very small and easy to manage. This would be a kind of partition inheritance, like in object languages... Dreams are allowed :-) Apparently that sort of thing is available on plan9 OS. Everything is a file so you can mount remote and local devices- plus merge them in a single directory. Check it out on wikipedia... Dreams can come true! :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
On 12/16/08, Bernard Dugas bern...@dugas-family.org wrote: Paul B. Mahol wrote: On 12/16/08, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: When you want to change something, you add a rw TransparentLayer : mount -tl yournfsserver:/StationYchanges/etc /etc So that changed or added files are only stored in this rw partition, thus very small and easy to manage. This would be a kind of partition inheritance, like in object languages... Dreams are allowed :-) try mount_unionfs and mount_nullfs Thanks Paul, FreeBSD has always hidden treasures :-) MOUNT_NULLFS(8) doc is very detailled, but i can't find how to use it for my problem : being able to go from common shared configuration to specific private configuration. unionfs looks very close to my dream, but it is currently not available for production :-( Well, I tested unionfs on CURRENT and it did not crashed on me. Feel free to test it on 7 STABLE and report results to developers. -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Optimising pxeboot disk size
Paul B. Mahol wrote: Well, I tested unionfs on CURRENT and it did not crashed on me. Feel free to test it on 7 STABLE and report results to developers. Thanks for the feed-back, i will no more be afraid to test :-) I will tell you later, Best regards, -- Bernard DUGAS Mobile +33 615 333 770 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pxeboot
On 30/07/2008, David Collins [EMAIL PROTECTED] wrote: I have been trying to get pxeboot to work, so far with no luck. I have a dhcp/tftp server set up and I am able to push pxeboot across the network, so I assume that is all ok. NFS is also setup, at least I was getting nfs errors that I don't have anymore. I copied the contents of the 7.0 cd into the my tftpboot folder and changed the contents for loader.conf and loader.rc Hi, I have been playing around all week and I finally have some sort of result. I am trying to pxeboot an ibm transnote (thinkpad), when I try to netboot with the power plugged in it starts to load the kernel then quickly reboots everytime. I don't think this is to do with the mfsroot gzip bug since I don't get that far - I think it maybe when it is loading the kernel, I am not sure I can't see any debugging messages they disappear from the screen quickly. I noticed that when I unplug the power and run from battery I am able to pxeboot everytime! Can anyone shed some light on why this happens? It isn't really a problem it is just an annoyance! Strangly enough if I copy the contents of the 7.0 cd to my exported directory and pxe boot from that (ie with mfsroot still gzipped) it boots right into the cd - no mfsroot bug here? I have tried this with 5.1 6.2 and 7.0 and they all act the same way. What I am stuck with now is when I modify loader.rc to something like the following: /usr/local/export# cat freebsd/boot/loader.rc echo Loading /boot/loader.rc load /boot/kernel/kernel set mfsroot_type=mfs_root set mfsroot_name=/boot/mfsroot set vfs.root.mountfrom=ufs:/dev/md0c load -t mfs_root /boot/mfsroot autoboot 5 The booting computer hangs after it tries to install the acpi.ko module. Does anyone know how I can get around this? Thanks David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot
Hi, Thanks both for your replies. I think the top of that article applies to me, in that I am trying to do something that I don't fully understand! I am fairly confident that I have the DHCP and TFTP setup correctly in as much as I get pxeboot on the booted machine (and I have gotten it working in linux). So here is my understandin at the moment: At boot time the netcard does its dhcp thing, gets an ip address pulls the filename from the tftp server (which is pxeboot). At this point pxeboot executes and acts much like loader. It mounts the nfs server at option root-path specified in the dhcpd.conf on the server, then loads boot/loader.rc from the mounted drive, then all the lovelies of BSD loader begin. I think that now I have this in my head straight I am able to get it working. I tried the following in my boot/loader.rc. The main reason for the oddities in my last email was that I didn't understand what the .rc and .conf files did, the 3 read lines were mainly debugging and trying to understand what was happening. echo Loading /boot/loader.rc set mfsroot_type=mfs_root set mfsroot_name=/mfsroot set vfs.root.mountfrom=ufs:/dev/md0c load -t mfs_root /mfsroot autoboot 5 At this point I still get the compter rebooting (I have gunzipped mfsroot to avoid the bug with it).. I am not convinced that I have loader.rc setup correctly. Where are the filenames in it relative to, is it relative to the nfs mount point too, in which case should the file be /boot/mfsroot? Is it possible to see an example of someones loader.rc that works? I have also tried tftp only pxeboot by making pxeboot with make -DLOADER_TFTP_SUPPORT=YES but I don't think that I had the files correctly located. Am I correct in thinking that in this case it will search for boot/loader.rc relative to the tftp server path? I found a book in my library that had a section on pxe booting, I was sad to see that although they had described setting up the dhcp and tftp servers they completely glossed over the actual setup of and how to use pxeboot! Thanks for help, it is greatly appreciated. David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot
David Collins wrote:
Hi,
I am not sure if this is the correct list to post this to, and if it
isn't please could you point me to where it should go.
I have recently turned to freeBSD and so far I love it. I have a small
laptop that I use for playing around and general fiddling. I was using
the Debian netinstall and booting over pxe/tftp when I wanted to
reinstall. I started looking at the automated install, but it seemed
very complex. I have been looking at the freeBSD option and it seems
that the automated intall is very simple (at least from a user point
of view).
I have been trying to get pxeboot to work, so far with no luck. I have
a dhcp/tftp server set up and I am able to push pxeboot across the
network, so I assume that is all ok. NFS is also setup, at least I was
getting nfs errors that I don't have anymore. I copied the contents of
the 7.0 cd into the my tftpboot folder and changed the contents for
loader.conf and loader.rc according to here
http://www.locolomo.org/pub/pxeboot/pxeboot.html and
http://www.tnpi.biz/computing/freebsd/pxe-netboot.shtml and so far I
am able to get a prompt come up but I am unable to get any further. As
soon as I enter anything the computer immediately reboots so i am
unable to see any error messages. I assume the paths are relative to
the tftp server. Can anyone give me quick example to get me off to a
start.
http://jdc.parodius.com/freebsd/pxeboot_serial_install.html is a pretty
good guide, you can ignore the bits about rebuilding pxeboot as your not
using a serial console but the mfs_root bug could be what you are hitting.
Vince
Thanks
David Collins
Here are my config files, I think that is all of them
# cat /etc/exports
/usr/tftpboot/freeBSD7.0 -alldirs -ro -maproot=root
# cat /usr/local/etc/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
authoritative;
ddns-update-style none;
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.8 192.168.2.15;
#filename /pxelinux.0;
filename /freeBSD7.0/boot/pxeboot;
next-server 192.168.2.4;
option routers 192.168.2.4;
option root-path /usr2/tftpboot/freeBSD7.0;
}
# grep tftp /etc/inetd.conf
tftpdgram udp waitroot/usr/libexec/tftpd tftpd
-l -s /usr/tftpboot
#cat /usr/tftpboot/freeBSD7.0/boot/loader.rc
echo Loading Kernel...
set choice=freebsd-ide
read -t 5 -p Type in your selection EXACTLY: choice
include /boot/loader.rc-$choice
read -t 5 -p Type in your selection EXACTLY: choice
read -t 5 -p Type in your selection EXACTLY: choice
load /boot/kernel/kernel
load linux.ko
echo \007\007
set vfs.root.mountfrom=ufs:/dev/md0c
#cat /usr/tftpboot/freeBSD7.0/boot/loader.conf
init_path=/stand/sysinstall
rootfs_load=YES
rootfs_name=/boot/mfsroot
rootfs_type=mfs_root
vfs.root.mountfrom=ufs:/dev/md0c
autoboot_delay=5
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot
Hi,
I am not sure if this is the correct list to post this to, and if it
isn't please could you point me to where it should go.
I have recently turned to freeBSD and so far I love it. I have a small
laptop that I use for playing around and general fiddling. I was using
the Debian netinstall and booting over pxe/tftp when I wanted to
reinstall. I started looking at the automated install, but it seemed
very complex. I have been looking at the freeBSD option and it seems
that the automated intall is very simple (at least from a user point
of view).
I have been trying to get pxeboot to work, so far with no luck. I have
a dhcp/tftp server set up and I am able to push pxeboot across the
network, so I assume that is all ok. NFS is also setup, at least I was
getting nfs errors that I don't have anymore. I copied the contents of
the 7.0 cd into the my tftpboot folder and changed the contents for
loader.conf and loader.rc according to here
http://www.locolomo.org/pub/pxeboot/pxeboot.html and
http://www.tnpi.biz/computing/freebsd/pxe-netboot.shtml and so far I
am able to get a prompt come up but I am unable to get any further. As
soon as I enter anything the computer immediately reboots so i am
unable to see any error messages. I assume the paths are relative to
the tftp server. Can anyone give me quick example to get me off to a
start.
Thanks
David Collins
Here are my config files, I think that is all of them
# cat /etc/exports
/usr/tftpboot/freeBSD7.0 -alldirs -ro -maproot=root
# cat /usr/local/etc/dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
authoritative;
ddns-update-style none;
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.8 192.168.2.15;
#filename /pxelinux.0;
filename /freeBSD7.0/boot/pxeboot;
next-server 192.168.2.4;
option routers 192.168.2.4;
option root-path /usr2/tftpboot/freeBSD7.0;
}
# grep tftp /etc/inetd.conf
tftpdgram udp waitroot/usr/libexec/tftpd tftpd
-l -s /usr/tftpboot
#cat /usr/tftpboot/freeBSD7.0/boot/loader.rc
echo Loading Kernel...
set choice=freebsd-ide
read -t 5 -p Type in your selection EXACTLY: choice
include /boot/loader.rc-$choice
read -t 5 -p Type in your selection EXACTLY: choice
read -t 5 -p Type in your selection EXACTLY: choice
load /boot/kernel/kernel
load linux.ko
echo \007\007
set vfs.root.mountfrom=ufs:/dev/md0c
#cat /usr/tftpboot/freeBSD7.0/boot/loader.conf
init_path=/stand/sysinstall
rootfs_load=YES
rootfs_name=/boot/mfsroot
rootfs_type=mfs_root
vfs.root.mountfrom=ufs:/dev/md0c
autoboot_delay=5
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pxeboot via tftp problem
Hi thanks for your attention but I wrote in my last mail that when acpi.ko isn`t in the folder ,it echo error message : ACPI autoload failed - no such file or directory cheers, mohamad Try removing the acpi.ko module, or unload it from the loader's (OK) prompt OK unload OK boot /boot/kernel/kernel cheers, Ruben On Sat, May 10, 2008 at 12:12:05AM -0700, mohammad khatibi typed: Hi, I`m new to freebsd.and?I`m using freebsd 7.0? I want to load my diskless systems through pxeboot in the network so?follow the instruction that mentioned in the mail about 2 weeks ago http://www.ultradesic.com/?section=144 instruction as follow: 1.compiling pxeboot and loader using? ?LOADER_TFTP_SUPPORT=YES 2.compiling kernel with necessary options 3.copy pxeboot,loader,kernel in /tftpboot/ 4.configure dhcp , all above steps finished successfuly and each client system get IP and dhcp client information correctly and just after it loads primary services and echo the message that said kernel will load in 10 seconds and after timeout, system hangs up and nothing happend. system echo following message at the end : /boot/kernel/kernel?? text=0x37fdd8??? data=0x81340+0x1460c syms=[0x4+0x3da60+0x4+0x51d1a] Hit [Enter] to boot immediatelly, or any other key for command prompt. Booting [/boot/kernel/kernel] ... /boot/kernel/acpi.ko text=0x500ef data= 0x81340+0x1460c?? syms=[0x4+0x3da60+0x4+0x51d1a] | and in this step system hangs up please help me to solve this problem before this error (that?I solved): after the timeout it echo the error message that said ACPI autoload failed that I copy acpi.ko in the folder (/tftpboot/boot/kernel/) and this error gone my /tftpboot/ contains 4 files and 2 folder: /tftpboot/pxeboot /tftpboot/boot/loader /tftpboot/boot/kernel/kernel /tftpboot/boot/kernel/acpi.ko Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Pxeboot via tftp problem
Hi, I`m new to freebsd.and I`m using freebsd 7.0 I want to load my diskless systems through pxeboot in the network so follow the instruction that mentioned in the mail about 2 weeks ago http://www.ultradesic.com/?section=144 instruction as follow: 1.compiling pxeboot and loader using LOADER_TFTP_SUPPORT=YES 2.compiling kernel with necessary options 3.copy pxeboot,loader,kernel in /tftpboot/ 4.configure dhcp , all above steps finished successfuly and each client system get IP and dhcp client information correctly and just after it loads primary services and echo the message that said kernel will load in 10 seconds and after timeout, system hangs up and nothing happend. system echo following message at the end : /boot/kernel/kernel text=0x37fdd8 data=0x81340+0x1460c syms=[0x4+0x3da60+0x4+0x51d1a] Hit [Enter] to boot immediatelly, or any other key for command prompt. Booting [/boot/kernel/kernel] ... /boot/kernel/acpi.ko text=0x500ef data= 0x81340+0x1460c syms=[0x4+0x3da60+0x4+0x51d1a] | and in this step system hangs up please help me to solve this problem before this error (that I solved): after the timeout it echo the error message that said ACPI autoload failed that I copy acpi.ko in the folder (/tftpboot/boot/kernel/) and this error gone my /tftpboot/ contains 4 files and 2 folder: /tftpboot/pxeboot /tftpboot/boot/loader /tftpboot/boot/kernel/kernel /tftpboot/boot/kernel/acpi.ko Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot, TFTP loader/NFS root, NFS MOUNT RPC error: 60, timeout
On Thu Feb 7 19:00:11 UTC 2008, Rek Jed rekjed at gmail.com wrote: Subject was: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout Hey, I've been building FreeBSD jumpstart infrastructure and it mostly works. I'm using tftp to boot off the network in to scripted sysinstall. I compiled the boot loader with tftp support but every time I boot it will first try nfs, then timeout after around two minutes (it cannot find nfs) and finally boot from tftp. Is there any way that I can make it boot from tftp straight away rather than wait for nfs to timeout? Hi. I'm new to this list, just came across this thread as I had the same error message - but the messages posted so far didn't help me. I found a solution for my case, and I'm posting it here so maybe it can help others too. In some cases like mine, the symptoms indicate that the problem might be caused by differing ways of interpreting bootp/dhcp information by the PXE hardware, rather than than in pxeboot itself. In my case, I had a dhcp filename entry which contained slashes (/), and this was causing trouble _after_ the referenced pxeboot was correctly loaded and executed. Long story: I wanted the loader to mount root and access / and /boot from NFS, not from tftp. I did get so far that the pxeboot was found and started, but the NFS root could not be mounted correctly, therefore /boot and the kernel were not found. it stopped stating NFS MOUNT RPC error: 60, timeout after a while, throwing me back into the loader prompt. The interesting thing is, a different machine booted just fine with the same setup. In my case: a DELL PowerEdge 1750 did boot, a PowerEdge 1950 did not. My setup: One server (7.0-STABLE) was serving TFTP and NFS to the local net, and both nfs root and tftp root were the same: /pxebootroot -alldirs -rw -maproot=root -network 192.168.1 -mask 255.255.255.0 in /etc/exports as well as tftp dgram udp wait root /usr/libexec/tftpd tftpd -s /pxebootroot in /etc/inetd.conf In my dhcpd.conf on the dhcp server I had the following entries (192.168.1.61 being the tftp and nfs server): filename /boot/pxeboot; next-server 192.168.1.61; option root-path 192.168.1.61:/pxebootroot; After a few attempts with the above error message I had a look into lsdev in the loader. It listed dell's virtual disk as well as, as a last entry, a 192.168.1.61:/boot/pxeboot this made me think that something strange was going on: why should that be listed as a device? maybe it got nfsmounted already? I tried loading the kernel from there, but I didn't get far. Whatever was wrong or not with it, it gave me an idea, ant it helped, in my case (on the tftp- and nfs server machine): cp -p /pxebootroot/boot/pxeboot /pxebootroot/ change the filename in dhcpd.conf of the dhcp server: - from filename /boot/pxeboot; - to filename pxeboot; and it boots fine with NFS root. I think somehow the slashes (/) within the filename in dhcp were (mis)interpreted by the pxe hw of the 1950. I'm still finishing a setup with different pxe boot environments, so if I come across any other details for this I'll be glad to share them. Regards, Lorenzo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD pxeboot unable to mount NFSroot
Hello all,
I would like to find out if the following is a known and documented
issue, and if so, can someone please point me to a link where I can
further understand the problem and cause.
I have encountered an issue where in a certain case a diskless client
is unable to mount NFSroot. Here is the explanation:
PXE/DHCP/TFTP and NFS server - CentOS 5.1
- Multiple clients NFSroot mount exported on a per host basis. One of
the clients is an NFS root mount image of FreeBSD 7
Configuration and Summary:
PXE/Server 192.168.16.x network; subnet: 255.255.240.0
Clients
-- when clients are configured and defined in /etc/dhcpd.conf with
an assigned address in 192.168.16.x then it is able to boot
successfully - for all types of clients -(ie., FreeBSD and linux
flavors):
eg.:
host testclient1 {
hardware ethernet 00:A0:DD:EF:5B:7E;
fixed-address 192.168.16.39;
filename pxeboot;
option root-path 192.168.16.5:/export/images/00A0DDEF5B7E/freebsd7_x64;
option host-name testclient1;
-- when we attempt to assign a FreeBSD client with an IP address
within the 192.168.17.x --- it is unable to mount its NFSroot export:
host testclient2{
hardware ethernet 00:A0:DD:EF:57:CA;
fixed-address 192.168.17.2;
filename pxeboot;
option root-path 192.168.16.5:/export/images/00A0DDEF57CA/freebsd7_x64;
option host-name testclient2;
}
The clients' bootup process stops when attempting to mount the NFSroot
and drops into a mount prompt, forcing the user to enter a local
device to mount root. Other linux flavor clients are able to boot
successfully, these clients use the pxelinux binary as opposed to
pxeboot that freeBSD clients use.
My question: is there any known issue vis a vis the pxeboot
implementation so that it's unable to figure out that my 192.168.17.x
has a subnet of 255.255.240.0 and should be able to mount and talk
to its NFS server that is in 192.168.16.x?
Any advise would be greatly appreciated.
--
best,
Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Rek Jed wrote: I also tried building it like that: # cd /usr/src/sys/boot # make LOADER_TFTP_SUPPORT=YES LOADER_NFS_SUPPORT=NO This builds fine. I copied it to my jumpstart server and it booted from tftp after approx 2 min. pause and the NFS MOUNT RPC error: 60. Can anyone tell me whats the difference between -DLOADER_TFTP_SUPPORT=YES and LOADER_TFTP_SUPPORT=YES? OK, two things remain: Are you sure that it doesn't correctly fetch the kernel with tftp and then the kernel tries to mount a root device with nfs? If the kernel is compiled with the slightest mention of nfs as root device it will use nfs, no matter that you have specified otherwise in loader.conf. The generic kernel has NFS_ROOT and NFS_CLIENT, since your root device is not NFS then you can leave out both. I recall having problems leaving in NFS_CLIENT although NFS_ROOT was not included. Second, the loader is ignorant of which version of FreeBSD you use, it will just load whichever kernel you throw at it. I have a loader I used for 6.1, http://www.locolomo.org/pub/pxeboot/jumpstart.tgz Hope this helps. If you find any errors or things that have changed since I worked with this, let me know and I will update the howto. Cheers, Erik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Erik Norgaard wrote: Second, the loader is ignorant of which version of FreeBSD you use, it will just load whichever kernel you throw at it. I have a loader I used for 6.1, http://www.locolomo.org/pub/pxeboot/jumpstart.tgz Sorry, wrong. This is not a pxeloader. Gosh it's long time since I did this, don't even know where my files are. Erik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Rek Jed [EMAIL PROTECTED] writes: I've been building FreeBSD jumpstart infrastructure and it mostly works. I'm using tftp to boot off the network in to scripted sysinstall. I compiled the boot loader with tftp support but every time I boot it will first try nfs, then timeout after around two minutes (it cannot find nfs) and finally boot from tftp. Is there any way that I can make it boot from tftp straight away rather than wait for nfs to timeout? Try unsetting boot.nfsroot.server and boot.nfsroot.path although I'm not sure that it will avoid the timeout in newer FreeBSD releases. -- Christian Laursen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Erik Norgaard wrote: OK, two things remain: Are you sure that it doesn't correctly fetch the kernel with tftp and then the kernel tries to mount a root device with nfs? When I build the pxeloader with LOADER_TFTP_SUPPORT=YES it will fetch the kernel from tftp just fine, but after the NFS gracefully times out. It will also fetch mount the root device from tftp ok. It's just a bit annoying that I have to wait 2 extra minutes every time I need to install a box (I do this quite often), and look for workarounds for something that should just work. But then, I'm a sysadmin not a developer so it might be easy for me to say. I cannot actually fix it myself. If the kernel is compiled with the slightest mention of nfs as root device it will use nfs, no matter that you have specified otherwise in loader.conf. The generic kernel has NFS_ROOT and NFS_CLIENT, since your root device is not NFS then you can leave out both. I recall having problems leaving in NFS_CLIENT although NFS_ROOT was not included. I don't bother compiling a kernel for this at the moment. I just copied the contents of /boot from a FreeBSD CD to the root of my tftp server. Then I copied the custom build loader files so that I can boot from tftp instead of nfs: boot0 boot1 boot2 loader.conf loader.rc mbr pxeboot Then I mount the stock mfsroot and copy my install.cfg over to script sysinstall. I've actually got a script that I can use to easily update install.cfg when needed. The idea behind all this is to keep it as simple to setup as possible so that me and my fellow network engineers at work can use this on their laptops without spending too much time on setting it up. This way if we need to install/re-install a box on a clients site we just rock up, run a few commands or a script to set the laptop in jumpstart mode (once the main thing has been setup it's just a matter of reconfiguring an interface and starting a few services), plug it in to the box, netboot and while the box is reinstalling we can have a chat with the client, see how things are going, look good and provide a better service. This also means that we always start with a machine that is in a know state. It's something that is almost impossible to achieve when installing by hand as everyone seems to do it differently. I'm happy to share my docs once I've ironed it all out and tested properly. Cheers, Jedrek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
I confirm it. Seems to be loader bug. I`ve tried to compile it without nfs support at all... but it didn`t help. I`ve been searching for solution for about a week and found nothing. Hey, I've been building FreeBSD jumpstart infrastructure and it mostly works. I'm using tftp to boot off the network in to scripted sysinstall. I compiled the boot loader with tftp support but every time I boot it will first try nfs, then timeout after around two minutes (it cannot find nfs) and finally boot from tftp. Is there any way that I can make it boot from tftp straight away rather than wait for nfs to timeout? This is how I build the boot loader: cd /usr/src/sys/boot sudo make clean sudo make LOADER_TFTP_SUPPORT=YES sudo cp i386/pxeldr/pxeboot /jumpstart/tftpd/boot/pxeboot.0 sudo cp i386/boot0/boot0 /jumpstart/tftpd/boot/ sudo cp i386/boot2/boot1 /jumpstart/tftpd/boot/ sudo cp i386/boot2/boot2 /jumpstart/tftpd/boot/ sudo cp i386/mbr/mbr /jumpstart/tftpd/boot/ This is my loader.conf: # loader.conf init_path=/stand/sysinstall rootfs_load=YES rootfs_name=/boot/mfsroot rootfs_type=mfs_root vfs.root.mountfrom=ufs:/dev/md0c autoboot_delay=0 And loader.rc: #loader.rc echo hopping the kernel... include /boot/loader.4th start Many thanks, Jedrek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Rek Jed wrote: Hey, I've been building FreeBSD jumpstart infrastructure and it mostly works. I'm using tftp to boot off the network in to scripted sysinstall. I compiled the boot loader with tftp support but every time I boot it will first try nfs, then timeout after around two minutes (it cannot find nfs) and finally boot from tftp. Is there any way that I can make it boot from tftp straight away rather than wait for nfs to timeout? This should Just Work, and I've had it work about half a year ago on 6.2. Which version are you compiling on? The tutorial I have handy[1] says to compile with: make -DLOADER_TFTP_SUPPORT=YES I'm not sure if it makes a difference. Anyhow, the boot loader source looks like it can't cope with both TFTP and NFS at the same time, so there might be a bug in there after all. Erik [1] http://www.locolomo.org/pub/pxeboot/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Hey, I've been building FreeBSD jumpstart infrastructure and it mostly works. I'm using tftp to boot off the network in to scripted sysinstall. I compiled the boot loader with tftp support but every time I boot it will first try nfs, then timeout after around two minutes (it cannot find nfs) and finally boot from tftp. Is there any way that I can make it boot from tftp straight away rather than wait for nfs to timeout? This is how I build the boot loader: cd /usr/src/sys/boot sudo make clean sudo make LOADER_TFTP_SUPPORT=YES sudo cp i386/pxeldr/pxeboot /jumpstart/tftpd/boot/pxeboot.0 sudo cp i386/boot0/boot0 /jumpstart/tftpd/boot/ sudo cp i386/boot2/boot1 /jumpstart/tftpd/boot/ sudo cp i386/boot2/boot2 /jumpstart/tftpd/boot/ sudo cp i386/mbr/mbr /jumpstart/tftpd/boot/ This is my loader.conf: # loader.conf init_path=/stand/sysinstall rootfs_load=YES rootfs_name=/boot/mfsroot rootfs_type=mfs_root vfs.root.mountfrom=ufs:/dev/md0c autoboot_delay=0 And loader.rc: #loader.rc echo hopping the kernel... include /boot/loader.4th start Many thanks, Jedrek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Zinevich Denis wrote: It does not work. I`ve tried. But as I found in forums and mailing lists it randomly helps sometimes. Please don't top-post. I have a comment in src/sys/boot/i386/loader/conf.c v1.26 (RELENG_7) saying: #if defined(LOADER_NFS_SUPPORT) defined(LOADER_TFTP_SUPPORT) #error Cannot have both tftp and nfs support yet. #endif So at least the intent is that NFS and TFTP are mutually exclusive. Since the OP has both working at the same time, there's something wrong. Which version are you using, and which architecture? I'm not really able to help you debug further, so I suggest filing a PR if one doesn't exist already. Erik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
I tried with LOADER_TFTP_SUPPORT and LOADER_NFS_SUPPORT both enabled. Also I tried with nfs disabled and tftp enabled. All was made under 6.2 stable, i386 arch. Only once i`ve got it working without timeout, but I could not repeat this. I`ll be back to this question in about one or two month with 6.2 and amd64 arch, so may be I`ll discover something new. Zinevich Denis wrote: It does not work. I`ve tried. But as I found in forums and mailing lists it randomly helps sometimes. Please don't top-post. I have a comment in src/sys/boot/i386/loader/conf.c v1.26 (RELENG_7) saying: #if defined(LOADER_NFS_SUPPORT) defined(LOADER_TFTP_SUPPORT) #error Cannot have both tftp and nfs support yet. #endif So at least the intent is that NFS and TFTP are mutually exclusive. Since the OP has both working at the same time, there's something wrong. Which version are you using, and which architecture? I'm not really able to help you debug further, so I suggest filing a PR if one doesn't exist already. Erik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Rek Jed wrote: Hey, I've been building FreeBSD jumpstart infrastructure and it mostly works. I'm using tftp to boot off the network in to scripted sysinstall. I compiled the boot loader with tftp support but every time I boot it will first try nfs, then timeout after around two minutes (it cannot find nfs) and finally boot from tftp. Is there any way that I can make it boot from tftp straight away rather than wait for nfs to timeout? This is how I build the boot loader: cd /usr/src/sys/boot sudo make clean sudo make LOADER_TFTP_SUPPORT=YES sudo cp i386/pxeldr/pxeboot /jumpstart/tftpd/boot/pxeboot.0 sudo cp i386/boot0/boot0 /jumpstart/tftpd/boot/ sudo cp i386/boot2/boot1 /jumpstart/tftpd/boot/ sudo cp i386/boot2/boot2 /jumpstart/tftpd/boot/ sudo cp i386/mbr/mbr /jumpstart/tftpd/boot/ Hi: I wrote the howto refered to in other reply, it's a while ago I played with this, but I have no reason to think that much has changed on the 6.x branch, I have just tried 7.x and build of the loader this way fails. As I understand the documentation, enabling TFTP disables NFS, they are exclusive. When building the loader make sure that your source tree is clean and /usr/obj is empty, or it won't work. I recall this puzzled me a long time until I found the trick. I don't think it is enough to do make clean. Second, I did # cd /usr/src/sys/boot # make -DLOADER_TFTP_SUPPORT=YES ok, as said, it's a while ago I played with this, they may have introduced support for the usual way of stating options. Cheers, Erik -- Erik Nørgaard Ph: +34.666334818 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Hi Erik, I wrote the howto refered to in other reply, it's a while ago I played with this, but I have no reason to think that much has changed on the 6.x branch, I have just tried 7.x and build of the loader this way fails. I tried building it on 7.0-PRERELEASE and it builds fine for me. Haven't tested if it works yet, but will do in a moment. When building the loader make sure that your source tree is clean and /usr/obj is empty, or it won't work. I recall this puzzled me a long time until I found the trick. I don't think it is enough to do make clean. Yes, I made sure that /usr/obj was empty. # cd /usr/src/sys/boot # make -DLOADER_TFTP_SUPPORT=YES Originally I was doing this on 6.2. I tried it again on a freshly installed 6.3-RELEASE just now. I made sure /usr/obj was empty and build pxeboot using the above method, then copied it over to my jumpstart server. Unfortunately this didn't work. It sat there for a bit, then trowed NFS MOUNT RPC error: 60 as usual and then sat there forever (it never fetched the kernel). I also tried building it like that: # cd /usr/src/sys/boot # make LOADER_TFTP_SUPPORT=YES LOADER_NFS_SUPPORT=NO This builds fine. I copied it to my jumpstart server and it booted from tftp after approx 2 min. pause and the NFS MOUNT RPC error: 60. Can anyone tell me whats the difference between -DLOADER_TFTP_SUPPORT=YES and LOADER_TFTP_SUPPORT=YES? I've been playing with thinbsd (http://www.thinbsd.org/) a while back. It also boots from tftp without nfs and their boot loader works fine (boots straight away). Latest thinbsd is based on 5.4 so maybe it broke in 6.x? For a workaround I used pxeboot from thinbsd with my 6.3 jumpstart setup and it seems to work fine. However this is quite dirty. Cheers, Jedrek P.S Thanks for the howto Erik, I found it really helpful. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
It does not work. I`ve tried. But as I found in forums and mailing lists it randomly helps sometimes. This should Just Work, and I've had it work about half a year ago on 6.2. Which version are you compiling on? The tutorial I have handy[1] says to compile with: make -DLOADER_TFTP_SUPPORT=YES I'm not sure if it makes a difference. Anyhow, the boot loader source looks like it can't cope with both TFTP and NFS at the same time, so there might be a bug in there after all. Erik [1] http://www.locolomo.org/pub/pxeboot/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
I tried building it on 7.0-PRERELEASE and it builds fine for me. Haven't tested if it works yet, but will do in a moment. I can confirm that the same thing happens on 7. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, TFTP only, NFS MOUNT RPC error: 60, timeout
Rek Jed skrev: I've been playing with thinbsd (http://www.thinbsd.org/) a while back. It also boots from tftp without nfs and their boot loader works fine (boots straight away). Latest thinbsd is based on 5.4 so maybe it broke in 6.x? For a workaround I used pxeboot from thinbsd with my 6.3 jumpstart setup and it seems to work fine. However this is quite dirty. I agree that building a boot loader for TFTP should work on current sources, but what makes you think using an old boot loader is dirty? It's just a utility to load a kernel from the network. It's not like it will affect your system when it's installed. Erik (Cederstrand) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless PXEboot crashes at kernel loading.
Hi all, I can't emphasise enough how useful running a TCPDUMP on the server in question is to find out what subtle thing it is that I missed. Generally speaking a quick-crash like that is a file not being found like the modules directory or something silly like that. If you dump the NFS traffic you will probably see the client asking for a file handle for file X and getting denied by the server. If you're not familiar w/ TCPDUMP, here are some handy commands: # Avoid SSH and dump everything to the screen... tcpdump -s 1500 -X udp # Write it to a file so you can open it in ethereal later... tcpdump -s 1500 -X -w nfs.dump udp # Read in the dump file and read it through less, should you not want to us # ethereal after the last step. :) tcpdump -X -r nfs.dump |less Note that if you have a slow or missing DNS entry, give these calls a -n to just get the data and not worry about the ND entries. Hope this helps! PXE boots are never kind. :) Sam Baskinger Software Engineer Lumeta - Securing the Network in the Face of Change Lumeta Corporation And the crash happens. Note that the crash occurs for whatever option 1 to 6 I choose from the FreeBSD boot menu. Does someone understand the crash messages? Not that I understand those messages but some time ago I've had a similar case. It took me some hours to realise that I try to load amd64 kernel to i386 diskless station... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless PXEboot crashes at kernel loading.
On Thu, 15 Feb 2007 22:07:13 -0800 (PST) Rob wrote: I already described in detail what I've been doing with the FreeBSD server and the Compaq HP client PC here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-February/142116.html The Bootp exchange seems to be fine and the client gets the kernel from the server. However, during the kernel loading, the client PC implodes and starts from BIOS boot up again. The boot messages are given below. The crash messages scroll too fast over the screen to see the details with the bare eye. I recorded it with a digital camera and a snapshot of it is here: http://www.lahaye.dds.nl/pxeboot/crash.jpg The whole boot process in plain text goes as follows: -- Attempting Boot From Intel(R) Boot Agent Version 3.0.05 (PnP Device) Initializing Intel(R) Boot Agent Version 3.0.05 PXE 2.0 Build 078 (WfM 2.0), RPL V2.73 Intel(R) Boot Agent Version 3.0.05 Copyright (C) 1997-2000, Intel Corporation CLIENT MAC ADDR: 00 02 A5 93 F7 44 GUID: 67862AE2-117C-D511-BFE9-F3C48B4FB125 DHCP./ BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 PXE version 2.1, real mode entry point 09db8:8186 BIOS a573kB/268896kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 pxe_open: server addr: 192.168.123.1 pxe_open: server path: / pxe_open: gateway ip: 192.168.123.254 Welcome to FreeBSD! ;-) [ Boot option menu 1 to 7 ] FreeBSD-ascii-cartoon /boot/kernel/kernel text=0x4d568c / int=.. err= ef11= eip= -- And the crash happens. Note that the crash occurs for whatever option 1 to 6 I choose from the FreeBSD boot menu. Does someone understand the crash messages? Not that I understand those messages but some time ago I've had a similar case. It took me some hours to realise that I try to load amd64 kernel to i386 diskless station... WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Diskless PXEboot crashes at kernel loading.
Hi, I already described in detail what I've been doing with the FreeBSD server and the Compaq HP client PC here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-February/142116.html The Bootp exchange seems to be fine and the client gets the kernel from the server. However, during the kernel loading, the client PC implodes and starts from BIOS boot up again. The boot messages are given below. The crash messages scroll too fast over the screen to see the details with the bare eye. I recorded it with a digital camera and a snapshot of it is here: http://www.lahaye.dds.nl/pxeboot/crash.jpg The whole boot process in plain text goes as follows: -- Attempting Boot From Intel(R) Boot Agent Version 3.0.05 (PnP Device) Initializing Intel(R) Boot Agent Version 3.0.05 PXE 2.0 Build 078 (WfM 2.0), RPL V2.73 Intel(R) Boot Agent Version 3.0.05 Copyright (C) 1997-2000, Intel Corporation CLIENT MAC ADDR: 00 02 A5 93 F7 44 GUID: 67862AE2-117C-D511-BFE9-F3C48B4FB125 DHCP./ BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 PXE version 2.1, real mode entry point 09db8:8186 BIOS a573kB/268896kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 pxe_open: server addr: 192.168.123.1 pxe_open: server path: / pxe_open: gateway ip: 192.168.123.254 Welcome to FreeBSD! [ Boot option menu 1 to 7 ] FreeBSD-ascii-cartoon /boot/kernel/kernel text=0x4d568c / int=.. err= ef11= eip= -- And the crash happens. Note that the crash occurs for whatever option 1 to 6 I choose from the FreeBSD boot menu. Does someone understand the crash messages? Thanks, Rob. Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEboot fails at kernel (text) loading
On Sun, 11 Feb 2007 17:22:22 -0800 (PST) Rob wrote: I have a FreeBSD 6.1 PC as the server to a PXE boot of another Compaq Deskpro EN PC. The Compaq PC has the option of a Network Service Boot with the F12-key during BIOS boot up. On the server, tftpd, bootpd and dhcpd are all working well. For the diskless kernel config I have used the GENERIC one, but added: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT According to man diskless those options are not needed for PXE. Any idea what's wrong here or what I could do to further test what the actual problem is? You may consider re-reading man diskless -- all needed info is located there. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEboot fails at kernel (text) loading
Rob wrote: Is it OK to have a double kernel read at the last two lines? Any idea what's wrong here or what I could do to further test what the actual problem is? Argh. I had this same problem as recently as October, but I can't remember exactly what caused this. When I went back and re-did things according to 'man diskless' (and what Doug White told me in the first place), it all worked. Regards, BMS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PXEboot fails at kernel (text) loading
Hi, I have a FreeBSD 6.1 PC as the server to a PXE boot of another Compaq Deskpro EN PC. The Compaq PC has the option of a Network Service Boot with the F12-key during BIOS boot up. On the server, tftpd, bootpd and dhcpd are all working well. For the diskless kernel config I have used the GENERIC one, but added: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT When all this is in place, and I reboot the client PC, the PXE works fine and I get the Welcome to FreeBSD! window, that allows me to choose from a list of options: 1. Boot FreeBSD [default] 2. Boot FreeBSD with ACPI enabled 3. Boot FreeBSD in Safe Mode 4. Boot FreeBSD in single user mode 5. Boot FreeBSD with verbose logging 6. Escape to loader prompt 7. Reboot Now whatever option (1 to 5) I choose here, I always get: /boot/kernel/kernel text=0x4d568c / and the last slash is rotating for a very tiny while after which the system kind of implodes, blanks the screen and reboots from BIOS. Apparently something goes very, very wrong when loading the text part of the kernel. On the server, I've checked the /var/log/xferlog, which has entries like this: read request for //pxeboot: success read request for /boot/loader.rc: success read request for /boot/loader.4th: success read request for /boot/support.4th: success read request for /boot/beastie.4th: success read request for /boot/screen.4th: success read request for /boot/frames.4th: success read request for /boot/kernel/kernel: success read request for /boot/kernel/kernel: success Is it OK to have a double kernel read at the last two lines? Any idea what's wrong here or what I could do to further test what the actual problem is? Thanks, Rob. We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot(8) NFS code breaks PIX/ASA policy
I'm PXE booting systems using the dhcprelay feature on a PIX 525 running 7.1(2). The TFTP process of retrieval of /tftoboot/pxeboot works fine, however once loaded NFS mount requests to the server fail per the following messages. In my config, all layer 4-7 packet inspection features are turned off. Any ideas why pxeboot would set the destination UDP port number to 0? It should be UDP/111 and UDP/2049, but alas TCPdump on the server shows nothing coming through. My work-around right now is to recompile pxeboot w/o NFS support and use TFTP file retrieval...which...sort of works. TIA, ~BAS -- Sep 05 2006 17:38:15: %PIX-4-54: Invalid transport field for protocol=UDP, from 192.168.129.130/1023 to 192.168.128.40/0 Sep 05 2006 17:38:19: %PIX-4-54: Invalid transport field for protocol=UDP, from 192.168.129.130/1023 to 192.168.128.40/0 According to Cisco: %PIX-4-54: Invalid transport field for protocol=protocol, from src_addr/src_port to dest_addr/dest_port Explanation This message appears when there is an invalid transport number, in which the source or destination port number for a protocol is zero. The protocol field is 6 for TCP and 17 for UDP. --- l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ ...from back in the heady days when helpdesk meant nothing, diskquota meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot looping
Erik Nørgaard wrote: John Pettitt wrote: Help! I'm trying to set up a machine to boot using pxe and have run into an odd problem. The box (a Soekris 4510) load pxeboot via TFTP prints a few lines of text then reboots - the last text I see is: Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader There is no further net traffic after the last tftp packet. I'm stumped - I thought it might be a cpu issue (the Soekris is a 486 clone) so I rebuilt pxeboot with -march=i486 and it didn't make any difference. Do you see the pxeboot actually gets fetched? Check the logs on your server. My immediate idea is that it doesn't get as far as fetching the pxeboot loader. Erik It's fetching it - I just grabbed pxeboot from an iso image ant that one gets a lot further so I suspect something in my build environment is not right for the soekris box. I'm still investigating. John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot looping
John Pettitt wrote: It's fetching it - I just grabbed pxeboot from an iso image ant that one gets a lot further so I suspect something in my build environment is not right for the soekris box. I'm still investigating. There is a problem building pxeboot if you have /usr/obj present - it won't build. I don't remember the error if any. So before going into /usr/src/sys/boot/i386/ to build pxeboot w/o tftp support, make sure to remove or rename /usr/obj. Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F0C.crt Subject ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 Fingerprint: 7F:80:96:EA:95:92:E2:23:1F:FA:0F:98:92:C2:CC:55:6B:9A:8C:92 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot looping
Help! I'm trying to set up a machine to boot using pxe and have run into an odd problem. The box (a Soekris 4510) load pxeboot via TFTP prints a few lines of text then reboots - the last text I see is: Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader There is no further net traffic after the last tftp packet. I'm stumped - I thought it might be a cpu issue (the Soekris is a 486 clone) so I rebuilt pxeboot with -march=i486 and it didn't make any difference. At this point I'm out of ideas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot looping
John Pettitt wrote: Help! I'm trying to set up a machine to boot using pxe and have run into an odd problem. The box (a Soekris 4510) load pxeboot via TFTP prints a few lines of text then reboots - the last text I see is: Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader There is no further net traffic after the last tftp packet. I'm stumped - I thought it might be a cpu issue (the Soekris is a 486 clone) so I rebuilt pxeboot with -march=i486 and it didn't make any difference. Do you see the pxeboot actually gets fetched? Check the logs on your server. My immediate idea is that it doesn't get as far as fetching the pxeboot loader. Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F0C.crt Subject ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9 Fingerprint: 7F:80:96:EA:95:92:E2:23:1F:FA:0F:98:92:C2:CC:55:6B:9A:8C:92 smime.p7s Description: S/MIME Cryptographic Signature
pxeboot to -Install- FreeBSD...
Hi All, I've been messing about with FreeBSD 6.1-Beta#4 recently, and I'm trying to get a server setup, so that I can pxeboot and install FreeBSD on some other servers... I've gotten dhcpd, tftp, pxeboot et'al to work - and, indeed the client machine dhcp's, pxeboots - and dumps itself into an 'Amnesic' FreeBSD system, with df showing: Filesystem 1k-blocks Used Avail Capacity Mounted On 10.0.0.1:/export/pxe 26353244 4071180 20173806 17% / devfs 1 1 1100% /dev /dev/md131470 134 28820 0% /var /dev/md21956612 17990 0% /tmp Obviously, this would be great if I wanted to run FreeBSD off of nfs/pxeboot - but not so good for installing it... On the off chance - I tried logging in, and firing up 'sysinstall' - which didn't do too well, probably obviously :) What do I need to do, to turn this 'booting FreeBSD from pxeboot' into something that will dump me into sysinstall, like booting from the CD rom? I've searched the net - but the only stuff I've found is either for much earlier FreeBSD versions, or incomplete - or both :) Thanks, -Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot to -Install- FreeBSD...
--On 07 April 2006 11:40 +0100 Karl Pielorz [EMAIL PROTECTED] wrote: What do I need to do, to turn this 'booting FreeBSD from pxeboot' into something that will dump me into sysinstall, like booting from the CD rom? I've searched the net - but the only stuff I've found is either for much earlier FreeBSD versions, or incomplete - or both :) Replying to my own post :( - I fixed this in the end, I overlooked a line in 'loader.conf': vfs.root.mountfrom=ufs:/dev/md0c Kind of important that one :) -Kp ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PXEboot install failing to load kernel
Hi, I am trying to perform a netboot install of FreeBSD 6 to a Thinkpad X40 laptop from linux on my desktop. I've followed what guides I can but the info is either for older versions of FreeBSD (the CD structure has changed?) or assumes an existing FreeBSD install to work from (for dissecting floppy images etc). I have downloaded the i386 bootonly iso and I have followed portions of several guides which has got me as far as tftp serving the pxeboot. I assume the dhcp and tftp parts are working ok as the laptop gets hold of pxeboot fine but then fails to load the kernel. I have tried nfs serving the boot directory of the cd and the kernel directory within that without any luck, is the kernel passed by tftp or nfs? I have tried tailing var/log/daemons but the failure to load kernel message on the laptop is the only useful indicator I get. Any help to get me further along appreciated, Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEboot install failing to load kernel
Chris wrote: I am trying to perform a netboot install of FreeBSD 6 to a Thinkpad X40 laptop from linux on my desktop. I've followed what guides I can but the info is either for older versions of FreeBSD (the CD structure has changed?) or assumes an existing FreeBSD install to work from (for dissecting floppy images etc). The assumption that you have some other existing FreeBSD installation makes certain things easier: In particular compiling the loader with tftp support, posibly creating a custom kernel and a memory file system. If you can get hold of these from download, then you should be fine. I have downloaded the i386 bootonly iso and I have followed portions of several guides which has got me as far as tftp serving the pxeboot. I assume the dhcp and tftp parts are working ok as the laptop gets hold of pxeboot fine but then fails to load the kernel. pxeboot can either attempt to fetch the kernel with tftp or nfs, (the standard pxeboot does not support tftp). If it doesn't get the kernel then either there is a misconfiguration so it doesn't fetch it correctly with tftp or the nfs server is incorrectly setup. You should post the relevant part of your dhcpd.conf. I have tried nfs serving the boot directory of the cd and the kernel directory within that without any luck, is the kernel passed by tftp or nfs? I have tried tailing var/log/daemons but the failure to load kernel message on the laptop is the only useful indicator I get. I would recommend to go without nfs: You can have pxeboot fetch kernel, and the loader.* files as well as a memory filesystem using tftp. It's easier to setup the server part, you have to setup tftp anyway and already have it working, going for nfs just introduces an extra source for errors. I wrote down what I did when I tried to setup pxeboot, , you may have found it - and yes, I do assume that you have a working FreeBSD for some parts, but read on, it may not be relevant for you. Check out www.daemonsecurity.com/pxe/ I want to update this so let me know if there are any errors or things that could be better explained. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scripting sysinstall for pxeboot
On 11 Feb 2006, at 04:30, Christopher Cowart wrote: On a not-a-show-stopper note, is there any way to get around specifying the hostname and/or net device? I'd rather not specify the hostname so that I can have one generic script for many machines. Further, what if a some other machine has a different kind of NIC? By hardcoding these values into install.cfg, the solution becomes much less maintainable. Why can't it obtain the hostname from DHCP? Any thoughts on this? Net device, I think you're out of luck. As for the hostname, if the DHCP server actually sends a hostname, then you *can* leave it out of install.cfg. Ceri -- That must be wonderful! I don't understand it at all. -- Moliere PGP.sig Description: This is a digitally signed message part
scripting sysinstall for pxeboot
Hello- I'm working on a project to netboot servers and perform a custom installation of FreeBSD. I have pxeboot working with tftp, providing an mfs image over the network. sysinstall runs as init and attempts to follow my install.cfg. However, when running my mediaSetFTP command, sysinstall errors with: The fxp0 device is not configured. You will need to do so in the Networking configuration menu before proceeding. However, I did set tryDHCP=YES. DHCP is working because 1) it just netbooted from it; and 2) I tried with the installation CD. It doesn't appear to be honoring my request that it try DHCP. If I take sysinstall over manually, specifying the network information, it works just fine. I want the installation to work with DHCP. Does anyone have any suggestions for debugging sysinstall in this way? On a not-a-show-stopper note, is there any way to get around specifying the hostname and/or net device? I'd rather not specify the hostname so that I can have one generic script for many machines. Further, what if a some other machine has a different kind of NIC? By hardcoding these values into install.cfg, the solution becomes much less maintainable. Why can't it obtain the hostname from DHCP? Any thoughts on this? Thanks for your help, Chris === My install.cfg: # This is the installation configuration file for our rackmounted FreeBSD # cluster machines # Turn on extra debugging. debug=YES nonInteractive=YES noWarn=NO tryDHCP=YES noConfirm=YES releaseName=6.0-RELEASE # My host specific data #hostname=firefly #domainname=rescomp.berkeley.edu netDev=fxp0 hostname=firefly _ftpPath=ftp://ftp.FreeBSD.org/pub/FreeBSD/ #nameserver=169.229.70.164 #defaultrouter=169.229.70.1 #ipaddr=169.229.70.170 #netmask=255.255.254.0 # # Which installation device to use RC ##Need to set this! ## #nfs=MyNfsServer:/export/ari_scratch2/gallatin/freebsd-dist mediaSetFTP #mediaSetNFS [[SNIP]] === -- Christopher Cowart Unix Systems Administrator Residential Computing, UC Berkeley May all your pushes be popped pgpCT4ovf0iPr.pgp Description: PGP signature
Re: pxeboot fails to load acpi.ko
Hi, Have you had a look in /boot/device.hints? hint.acpi.0.disabled=1 I at the moment maintain 2 diskless images, the one for older hardware has the above setting to disable acpi(machine would hang with it enabled). I believe setting it to 0 or commenting it out could help you. A. Hey- I've been working on a project to automate FreeBSD installations over the network, using PXE boot capabilities. I've been following the howtos, as documented starting here: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/index.html and http://www.daemonsecurity.com/pxe/jumpstart.html I'm having a difficult time finding posts from other people who have experienced similar problems. Everything is setup. I'm using a tftpd that can handle large files. DHCPD is configured correctly. The client boots the PXE boot loader, as it should. It then begins loading the kernel. Upon loading the file acpi.ko, the boot hangs. Doing a tcpdump on the traffic, it looks like the machine receives the last packet of acpi.ko, and before it even has a chance to send an ACK, it's done. The twirly status bar stops spinning. The machine is doomed for a hard reboot. I've tried with two very different boxes to ensure it's not a hardware anomoly. The machines boot fine from the installation CDs -- loading acpi.ko. Further, I started with 5.3-REL, stepped up to 5.4-REL, and lastly, 6.0-REL. The problem occurs with all these versions. I'm not sure how to continue debugging this problem. Any tips in terms of troubleshooting or known workarounds would be great. Thanks, Chris -- Christopher Cowart Unix Systems Administrator Residential Computing, UC Berkeley May all your pushes be popped ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot fails to load acpi.ko
Hey- I've been working on a project to automate FreeBSD installations over the network, using PXE boot capabilities. I've been following the howtos, as documented starting here: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/index.html and http://www.daemonsecurity.com/pxe/jumpstart.html I'm having a difficult time finding posts from other people who have experienced similar problems. Everything is setup. I'm using a tftpd that can handle large files. DHCPD is configured correctly. The client boots the PXE boot loader, as it should. It then begins loading the kernel. Upon loading the file acpi.ko, the boot hangs. Doing a tcpdump on the traffic, it looks like the machine receives the last packet of acpi.ko, and before it even has a chance to send an ACK, it's done. The twirly status bar stops spinning. The machine is doomed for a hard reboot. I've tried with two very different boxes to ensure it's not a hardware anomoly. The machines boot fine from the installation CDs -- loading acpi.ko. Further, I started with 5.3-REL, stepped up to 5.4-REL, and lastly, 6.0-REL. The problem occurs with all these versions. I'm not sure how to continue debugging this problem. Any tips in terms of troubleshooting or known workarounds would be great. Thanks, Chris -- Christopher Cowart Unix Systems Administrator Residential Computing, UC Berkeley May all your pushes be popped pgpH4SPmXT1cw.pgp Description: PGP signature
Pxeboot for nfs installation woes.
Hi all, I have a lot of servers on order, so I want to be able to just network boot them as a jumpstart into the installation (which will then be scripted). I am most of the way there. I have tested my NFS shares and if I boot a boxe off a cd, I can do the nfs installation without fail. I have setup pxeboot, and if I am far enough along that when I boot off the network, it tftp's the files it needs, boots through menus, loads the generic kernel, mounts an nfs root, then errors. The errors are exec /sbin/init: error 70. One error for each attempt at an init file. Then it gives me an init: not found in path /sbin/init:/sbin/oinit.. Then it panics and reboots. There is so much I've done, I'm not sure what specifics anyone might need to offer some assistance. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pxeboot for nfs installation woes.
Christopher McGee wrote: Hi all, I have a lot of servers on order, so I want to be able to just network boot them as a jumpstart into the installation (which will then be scripted). I am most of the way there. I have tested my NFS shares and if I boot a boxe off a cd, I can do the nfs installation without fail. I have setup pxeboot, and if I am far enough along that when I boot off the network, it tftp's the files it needs, boots through menus, loads the generic kernel, mounts an nfs root, then errors. The errors are exec /sbin/init: error 70. One error for each attempt at an init file. Then it gives me an init: not found in path /sbin/init:/sbin/oinit.. Then it panics and reboots. There is so much I've done, I'm not sure what specifics anyone might need to offer some assistance. 1st: I have done it but with ftp install rather than nfs, see here: http://www.daemonsecurity.com/pxe/ I used no cd's to bootstrap or anything. 2nd: One of the first things done in the bootstrapping is to load the loader.conf, in this you can override any settings of paths to the init program. For installation usually sysinstall is used, which can be scripted - I assume you are refering to this? - you can set the path with an option in loader.conf, for example: init_path=/stand/sysinstall The option may contain a colon separated list of files and they are checked in order, the first found is run. Check the path to your init or sysinstall on the nfs-client. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pxeboot for nfs installation woes.
Erik Norgaard wrote: Christopher McGee wrote: Hi all, I have a lot of servers on order, so I want to be able to just network boot them as a jumpstart into the installation (which will then be scripted). I am most of the way there. I have tested my NFS shares and if I boot a boxe off a cd, I can do the nfs installation without fail. I have setup pxeboot, and if I am far enough along that when I boot off the network, it tftp's the files it needs, boots through menus, loads the generic kernel, mounts an nfs root, then errors. The errors are exec /sbin/init: error 70. One error for each attempt at an init file. Then it gives me an init: not found in path /sbin/init:/sbin/oinit.. Then it panics and reboots. There is so much I've done, I'm not sure what specifics anyone might need to offer some assistance. 1st: I have done it but with ftp install rather than nfs, see here: http://www.daemonsecurity.com/pxe/ I used no cd's to bootstrap or anything. 2nd: One of the first things done in the bootstrapping is to load the loader.conf, in this you can override any settings of paths to the init program. For installation usually sysinstall is used, which can be scripted - I assume you are refering to this? - you can set the path with an option in loader.conf, for example: init_path=/stand/sysinstall The option may contain a colon separated list of files and they are checked in order, the first found is run. Check the path to your init or sysinstall on the nfs-client. Cheers, Erik That is the how-to that I started with, however it jumps around a bit becaues they are also showing how to do diskless clients. Basically I have this: /tftpboot is a link to /usr/local/export/freebsd I have put the entire cd in /usr/local/export/freebsd copied pxeboot to /usr/local/export/freebsd setup nfsserver:/usr/local/export/freebsd as the root_path on the dhcp server. It appears to try to mount that share as the rootpath. the nfsserver is exporting /usr -alldirs After the kernel boots there is a line that says: NFS ROOT: 192.168.1.98:/usr/local/export/freebsd and then it errors. If that is path to the root of the cd, this should work correct? Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 5.3/5.4 - pxeboot hosting on em0 Intel 82540EM
Netboot and Installing FreeBSD over em0 GigE link I am having an issue with pxeboot/BTX loader mounting/contacting a TFTP server or NFS server that is hosted on machine with an Intel GigE em0 ethernet card. pxeboot comes over (via 82540EM bios), loader comes over, but the load says it can figure out what the root disk is. So the loader cannot find /boot/defaults/loader.conf, that is were it stops. Any ideas ? Anyone use the if_em on FreeBSD to perform netboots/ netinstalls ? [EMAIL PROTECTED]:6:0: class=0x02 card=0x002e8086 chip=0x100e8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82540EM Gigabit Ethernet Controller' class= network subclass = ethernet Two near identical machines using this card in a cross-over (as the private link). I have a third machine that I have networked booted with the same kernel and loader/pxeboot binaries, and mfsboot, but both machines in that configuration are using fxp cards. ( BTW - the pxeboot documentation needs some correction for the 5.4 release. Will post my notes later. ) - David P. Discher * http://davidpdischer.com/ * C: x [EMAIL PROTECTED] *AIM: DavidDPD* H: x - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd pxeboot problem
Hi, 10.0.0.10 is my dhcp server and 10.0.0.24 is the dynamic ip offered by the dhcp server. Below is the DHCP debug output DHCPDISCOVER from 00:07:e9:2f:45:55 via rl0 DHCPOFFER on 10.0.0.24 to 00:07:e9:2f:45:55 via rl0 DHCPREQUEST for 10.0.0.24 (10.0.0.10) from 00:07:e9:2f:45:55 via rl0 DHCPACK on 10.0.0.24 to 00:07:e9:2f:45:55 via rl0 DHCPDISCOVER from 00:07:e9:2f:45:55 via rl0 DHCPOFFER on 10.0.0.24 to 00:07:e9:2f:45:55 via rl0 DHCPREQUEST for 192.168.102.110 (192.168.102.1) from 00:07:e9:2f:45:55 via rl0: ignored (not authoritative). The first 4 lines are the communication between the rom pxe and the dhcp server. The last 3 lines are the communication between the downloaded pxeboot and the dhcp server. The downloaded pxeboot does not seem to retain the ip address offered by DHCP. Any don't know where it got 192.168.102.110 (192.168.102.1) from. Has anyone faced this problem before. Regards Sunil Sunder Raj From: Nathan Kinkade [EMAIL PROTECTED] Reply-To: Nathan Kinkade [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED], freebsd-questions@freebsd.org Subject: Re: Freebsd pxeboot problem Date: Tue, 24 May 2005 19:30:28 +0100 On Mon, May 23, 2005 at 04:52:18PM +, Sunil Sunder Raj wrote: Hi, Was trying to install freebsd 5.3 via pxeboot. The Dhcp server leases the Ip address, the tftp server is located fine and the pxeboot file gets downloaded at the client end. But this pxeboot is not getting the proper server path and gateway ip. It is always falling to the default /pxeroot server path (as programmed in the pxe.c file) and don't know where it gets the gateway ip as 192.168.102.1 Display I get pxe_open: server addr: This is proper. The Dhcp/Tftp server ip pxe_open: server path: /pxeroot --- default server path. This is not what I defined in my dhcpd.conf pxe_open: gateway ip: 192.168.102.1 --- Don't know where it got it from. This is not what I defined in my dhcpd.conf snip What is defined in your dhcpd.conf file? I think you may need two perameters: option root-path nfsserver:/diskless/root/path/ next-server yourserver You may not need next-server if it's the same machine as the DHCP server. Nathan attach3 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd pxeboot problem
Hi,
Below are all the details I can provide you.
dhcpd.conf
==
ddns-update-style none;
option routers 10.0.0.1;
subnet 10.0.0.0 netmask 255.255.255.0 {
range 10.0.0.22 10.0.0.24;
option subnet-mask 255.255.255.0;
option broadcast-address 10.0.0.255;
option domain-name-servers 202.54.1.30, 202.54.1.18;
option domain-name xyz.com;
default-lease-time 2592000;
max-lease-time 2592000;
next-server 10.0.0.10;
server-name xyz.com;
server-identifier 10.0.0.10;
option root-path /usr/local/exports/freebsd5.4;
filename boot/pxeboot;
}
/etc/exports
/usr/local/exports/freebsd5.4 -ro
/etc/inetd.conf
===
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -l
/usr/local/exports/freebsd5.4
# strings /usr/local/exports/freebsd5.4/boot/pxeboot | grep nfs
boot.nfsroot.server
boot.nfsroot.path
boot.nfsroot.nfshandle
no rootpath, no nfs
/usr/src/lib/libstand/nfs.c
nfsread: short packet, %d %ld
# ls -l /usr/local/exports/freebsd5.4
total 1292
-r--r--r-- 1 root wheel 801 May 8 07:05 .cshrc
-r--r--r-- 1 root wheel1458 May 8 10:38 .profile
dr-xr-xr-x 18 root wheel 512 May 8 10:38 5.4-RELEASE
-r--r--r-- 1 root wheel6192 May 8 07:05 COPYRIGHT
-r--r--r-- 1 root wheel 18133 May 8 10:38 ERRATA.HTM
-r--r--r-- 1 root wheel 10109 May 8 10:38 ERRATA.TXT
-r--r--r-- 1 root wheel 125891 May 8 10:38 HARDWARE.HTM
-r--r--r-- 1 root wheel 74414 May 8 10:38 HARDWARE.TXT
-r--r--r-- 1 root wheel 76334 May 8 10:38 INSTALL.HTM
-r--r--r-- 1 root wheel 56771 May 8 10:38 INSTALL.TXT
-r--r--r-- 1 root wheel 46766 May 8 10:38 MIGRATE5.HTM
-r--r--r-- 1 root wheel 31732 May 8 10:38 MIGRATE5.TXT
-r--r--r-- 1 root wheel 20445 May 8 10:38 README.HTM
-r--r--r-- 1 root wheel 14798 May 8 10:38 README.TXT
-r--r--r-- 1 root wheel 47258 May 8 10:38 RELNOTES.HTM
-r--r--r-- 1 root wheel 24167 May 8 10:38 RELNOTES.TXT
dr-xr-xr-x 2 root wheel1024 May 8 07:01 bin
dr-xr-xr-x 5 root wheel 512 May 23 01:02 boot
-r--r--r-- 1 root wheel2048 May 8 10:47 boot.catalog
-r--r--r-- 1 root wheel 39 May 8 10:38 cdrom.inf
dr-xr-xr-x 2 root wheel 512 May 8 07:00 dev
-r--r--r-- 1 root wheel2971 May 8 10:38 docbook.css
dr-xr-xr-x 17 root wheel2048 May 8 07:05 etc
-r--r--r-- 1 root wheel 685246 May 8 10:44 filename.txt
dr-xr-xr-x 2 root wheel 512 May 8 10:38 floppies
dr-xr-xr-x 3 root wheel1024 May 8 07:02 lib
dr-xr-xr-x 2 root wheel 512 May 8 07:01 libexec
dr-xr-xr-x 2 root wheel 512 May 8 07:00 mnt
dr-xr-xr-x 14 root wheel 512 May 8 10:44 packages
dr-xr-xr-x 2 root wheel 512 May 8 07:00 proc
dr-xr-xr-x 2 root wheel2560 May 8 07:02 rescue
dr-xr-xr-x 2 root wheel 512 May 8 07:05 root
dr-xr-xr-x 2 root wheel2560 May 8 07:04 sbin
lrwxrwxrwx 1 root wheel 7 May 22 19:03 stand - /rescue
lrwxrwxrwx 1 root wheel 11 May 22 19:03 sys - usr/src/sys
dr-xr-xr-x 2 root wheel 512 May 8 07:00 tmp
dr-xr-xr-x 5 root wheel1024 Jul 13 2003 tools
dr-xr-xr-x 13 root wheel 512 May 8 10:26 usr
dr-xr-xr-x 20 root wheel 512 May 8 10:26 var
# ls -l /usr/local/exports/freebsd5.4/boot
total 1668
-r--r--r-- 1 rootwheel 7007 May 8 07:03 beastie.4th
-r--r--r-- 1 rootwheel 8192 May 8 07:03 boot
-r--r--r-- 1 rootwheel 512 May 8 07:03 boot0
-r--r--r-- 1 rootwheel 512 May 8 07:03 boot0sio
-r--r--r-- 1 rootwheel 512 May 8 07:03 boot1
-r--r--r-- 1 rootwheel 7680 May 8 07:03 boot2
-r--r--r-- 1 rootwheel 1184 May 8 07:03 cdboot
dr-xr-xr-x 2 rootwheel 512 May 8 07:03 defaults
-r--r--r-- 1 rootwheel 1982 May 8 07:05 device.hints
-r--r--r-- 1 rootwheel 2249 May 8 07:03 frames.4th
dr-xr-xr-x 2 rootwheel 8192 May 8 10:21 kernel
-r-xr-xr-x 1 manage wheel 212992 May 23 23:23 loader
-r--r--r-- 1 rootwheel 7772 May 8 07:03 loader.4th
-r--r--r-- 1 rootwheel 107 May 22 19:29 loader.conf
-r--r--r-- 1 rootwheel13893 May 8 07:03 loader.help
-r--r--r-- 1 rootwheel 370 May 8 07:03 loader.rc
-r--r--r-- 1 rootwheel 512 May 8 07:03 mbr
-r--r--r-- 1 rootwheel 1082571 May 8 10:38 mfsroot.gz
dr-xr-xr-x 2 rootwheel 512 May 8 07:00 modules
-rw-r--r-- 1 manage wheel 215040 May 23 23:23 pxeboot
-r--r--r-- 1 rootwheel 692 May 8 07:03 screen.4th
-r--r--r-- 1 rootwheel36440 May 8 07:03 support.4th
# cat /usr/local/exports/freebsd5.4/boot/loader.conf
mfsroot_load=YES
mfsroot_type=mfs_root
mfsroot_name=/boot/mfsroot
vfs.root.mountfrom=ufs:/dev/md0c
Regards
Sunil Sunder Raj
From: Eric Anderson [EMAIL PROTECTED]
To: Sunil Sunder Raj [EMAIL PROTECTED]
CC: freebsd-questions@freebsd.org, [EMAIL PROTECTED]
Subject: Re: Freebsd pxeboot problem
Date: Mon, 23 May 2005 13:15:16 -0500
Sunil
Re: Freebsd pxeboot problem
On Mon, May 23, 2005 at 04:52:18PM +, Sunil Sunder Raj wrote: Hi, Was trying to install freebsd 5.3 via pxeboot. The Dhcp server leases the Ip address, the tftp server is located fine and the pxeboot file gets downloaded at the client end. But this pxeboot is not getting the proper server path and gateway ip. It is always falling to the default /pxeroot server path (as programmed in the pxe.c file) and don't know where it gets the gateway ip as 192.168.102.1 Display I get pxe_open: server addr: This is proper. The Dhcp/Tftp server ip pxe_open: server path: /pxeroot --- default server path. This is not what I defined in my dhcpd.conf pxe_open: gateway ip: 192.168.102.1 --- Don't know where it got it from. This is not what I defined in my dhcpd.conf snip What is defined in your dhcpd.conf file? I think you may need two perameters: option root-path nfsserver:/diskless/root/path/ next-server yourserver You may not need next-server if it's the same machine as the DHCP server. Nathan pgpQqaezVJa6M.pgp Description: PGP signature
Freebsd pxeboot problem
Hi, Was trying to install freebsd 5.3 via pxeboot. The Dhcp server leases the Ip address, the tftp server is located fine and the pxeboot file gets downloaded at the client end. But this pxeboot is not getting the proper server path and gateway ip. It is always falling to the default /pxeroot server path (as programmed in the pxe.c file) and don't know where it gets the gateway ip as 192.168.102.1 Display I get pxe_open: server addr: This is proper. The Dhcp/Tftp server ip pxe_open: server path: /pxeroot --- default server path. This is not what I defined in my dhcpd.conf pxe_open: gateway ip: 192.168.102.1 --- Don't know where it got it from. This is not what I defined in my dhcpd.conf \ Can't load 'kernel' Below is what I read in the pxe.c file === /* * Do a bootp/dhcp request to find out where our * NFS/TFTP server is. Even if we dont get back * the proper information, fall back to the server * which brought us to life and a default rootpath. */ if (!rootpath[1]) strcpy(rootpath, PXENFSROOTPATH); Has anyone faced this problem. Regards Sunil Sunder Raj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd pxeboot problem
Sunil Sunder Raj wrote: Hi, Was trying to install freebsd 5.3 via pxeboot. The Dhcp server leases the Ip address, the tftp server is located fine and the pxeboot file gets downloaded at the client end. But this pxeboot is not getting the proper server path and gateway ip. It is always falling to the default /pxeroot server path (as programmed in the pxe.c file) and don't know where it gets the gateway ip as 192.168.102.1 Display I get pxe_open: server addr: This is proper. The Dhcp/Tftp server ip pxe_open: server path: /pxeroot --- default server path. This is not what I defined in my dhcpd.conf pxe_open: gateway ip: 192.168.102.1 --- Don't know where it got it from. This is not what I defined in my dhcpd.conf Can you send the relevant dhcp conf section? Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology A lost ounce of gold may be found, a lost moment of time never. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Solved: Failure to initialise network infterface after pxeboot
Error in the memory file system caused the problem. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange problem with pxeboot
Hi, Sorry - I have no more descriptive subject because this is really strange: I have set up a server to serve clients booting with pxeboot and fetching kernel and a memory disk root file system with tftp. So far so good. What is strange is this: 1) If the local harddrive (which contains an old FreeBSD 4.9) is installed, the client correctly configures the ethernet card (vr0) and tries to mount a root file system using NFS - but the whole idea was to avoid using NFS at all. If I leave the root-path unset in the dhcpd.conf the client will try to mount the root file system from next-server:/pxeroot 2) If I remove the harddrive, then it mounts the memory file system as root file system and launches sysinstall (which is what I really want) - however, it fails to initialize the network card, and there is (obviously) no disk to install on. the ethernet driver is compiled into the kernel - no modules need to be loaded, these are my loader files: loader.rc: include /boot/loader.4th start loader.conf: init_path=/sbin/init:/stand/sysinstall rootfs_load=YES rootfs_name=/boot/mfsroot rootfs_type=mfs_root autoboot_delay=5 boot/ on tftp server: defaultskernel loader.gz pxeboot device.hintsloader.4th loader.rc support.4th frames.4th loader.conf mfsroot Any hints would be greatly appreciated! Thanks, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PXEBoot fails in last stage
Hi, I have set up a server (dhcp/tftp/ftp, no nfs configured) as a jumpstart server for pxeboot and compiled kernel with -DLOADER_TFTP_SUPPORT=YES. The client machine is a VIA EPIA CL1000 with a 60GB hdd with a FreeBSD 4.9, I want to reinstall to get 5.3. Kernel is compiled with option BOOTP and support for memory filesystem as root device. The client machine boots up and goes through stage 1-3, fetching kernel and memory file system with tftp. But I have problem launching into the final stage which sould launch sysinstall and run an installation script. The client correctly configures the ethernet card (vr0) but then tries to mount a root file system using NFS! - the whole idea was to avoid messing around with NFS. If I leave the root-path unset or define it as in the dhcpd.conf the client will keep requesting a root-path. From what is written on the screen it doesn't mount the local HDD. How to I force it to use the memory file system as root device? An interesting sidenote: I first had the kernel compiled without option BOOTP, then the client would correctly mount the memory file system, but only if the local harddrive was NOT present!! These are my loader files set up as described on www.m0n0.ch/wall/hack/ loader.rc: include /boot/loader.4th start loader.conf: init_path=/sbin/init:/stand/sysinstall rootfs_load=YES rootfs_name=/boot/mfsroot rootfs_type=mfs_root autoboot_delay=5 boot/ on tftp server: defaultskernel loader.gz pxeboot device.hintsloader.4th loader.rc support.4th frames.4th loader.conf mfsroot Any hints would be greatly appreciated! Thanks, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Solved: PXEBoot fails in last stage
Erik Norgaard wrote: I have set up a server (dhcp/tftp/ftp, no nfs configured) as a jumpstart server for pxeboot and compiled kernel with -DLOADER_TFTP_SUPPORT=YES. The client machine is a VIA EPIA CL1000 with a 60GB hdd with a FreeBSD 4.9, I want to reinstall to get 5.3. Kernel is compiled with option BOOTP and support for memory filesystem as root device. Aparently the loader does not respect the value of rootfs, it _will_ try nfs if it can! I removed all options related to nfs in the kernel configuration file - it was _not_ enough to remove option nfs_root. I guess this should result in a bug report. Cheers, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Failure to initialise network infterface after pxeboot
Hi, - again - sorry to bother you all, but at least I progress :-) I have a VIA C3 Nehemiah (CL1000), 256MB ram, 60GB HDD. CL1000 comes with two ethernet interfaces, both VIA Rhine III 10/100, on my system (from FreeBSD 4.10 dmesg): vr0: VIA VT6105 Rhine III 10/100BaseTX port 0xd000-0xd0ff mem 0xde00-0xdeff irq 12 at device 15.0 pci0 vr0: Ethernet address: 00:40:63:d4:89:72 miibus0: MII bus on vr0 vr1: VIA VT6102 Rhine III 10/100BaseTX port 0xe800-0xe8ff mem 0xde002000-0xde0020ff irq 11 at device 18.0 pci0 vr1: Ethernet address: 00:40:63:d4:89:71 miibus1: MII bus on vr1 VIA supports pxeboot so I wanted to use this with dhcp/tftp/ftp to reinstall the system as I have no spare cd drive. I have succesfully set up the server for dhcp, tftp and ftp. The VIA machine correctly loads the pxeboot file, fetches a memory filesystem and mounts it as root. All on vr0. The problem comes when the machine ends stage 3. It does no longer find vr0!? I previously had problems forcing the boot loader to use the memory file system as root device. I then had compiled the kernel with NFSCLIENT and NFS_ROOT options along with MD_ROOT. With this config the machine tried to nfs mount a root file system over vr0 - no problem finding the interface. I have now removed all options refering to NFS - BOOTP is still there. Now vr0 is not found. Any help would be greatly appreciated! Thanks, Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd pxeboot problem
Hi all, Am having trouble with pxeboot on freebsd 5.1. Am following procedure at http://www.tnpi.biz/computing/freebsd/pxe-netboot.shtml (relevant bit pasted at bottom). This procedure states to create an empty 25Mb file using dd, make a fs out of it (disklabel/newfs/mdconfig), then rsync the contents of mfsroot to this fs. This is then used as the rootfs on the pxeboot client (set vfs.root.mountfrom=ufs:/dev/md0c). When I try this, the client hangs forever on boot in loader.rc. However, if I simply create a fs using mdconfig and use this on the client, it boots to sysinstall ok (ie gunzip mfsroot.gz; mdconfig -a -t vnode -f mfsroot -u0). I can even mount this fs before I pxeboot and put an install.cfg file there. However, when the client reads it, it hangs when trying to mount server:/usr/local/export/freebsd to install the distribution (Mounting x.x.x.x:/usr/local/export/freebsd over NFS on /dist). I tried exporting the /usr without -ro but no difference. Suspect there is no room on the mfsroot fs more mounting nfs (since I haven't got a 25Mb file). Has anybody set this up before. I have seen somebody else had this problem on freebsd list, but no response. Any help would be appreciated. (Do I summarise back to this list?). Thanks === cd /usr/local/export/pxe dd if=/dev/zero of=mfsroot bs=1k count=25000 mdconfig -a -t vnode -f mfsroot -u0 disklabel -r -w md0 auto newfs /dev/md0c mkdir -p /mnt/mfs mount /dev/md0 /mnt/mfs There, now we've got 25 megs of space mounted on /mnt to play with. The basic rule of thumb here to keep in mind is that you are building a root file system for FreeBSD. Everything the kernel, sysinstall, and your install programs needs from the root file system is what you need to have in your /mnt directory. To get started we'll copy the contents of the distribution mfsroot.flp to our new mfsroot: mkdir /mnt/floppy mdconfig -a -t vnode -u 1 -f /usr/local/export/freebsd5.1/floppies/mfsroot.flp mount /dev/md1 /mnt/floppy cp /mnt/floppy/mfsroot.gz /tmp umount /mnt/floppy mdconfig -d -u 1 gunzip /tmp/mfsroot.gz mdconfig -a -t vnode -u 1 -f /tmp/mfsroot mount /dev/md1 /mnt/floppy rsync -avzH /mnt/floppy/ /mnt/mfs umount /mnt/floppy mdconfig -d -u 1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using pxeboot for installation (bug in pxeboot - tftp)
Hi I have used pxeboot to load freebsd 5.2.1 through tftp. It seems as the tftp client in pxeboot fails to send an data acknowledge after the last datapacket in each tftp transfer. (not very nice for server which resends last datapacket several times) BTW: Does anybody know a way to specify freebsd to retrieve an install.cfg from outside mfs_root ? -- Kasper Fock EasySpeedy ApS Høsterkøbvej 33 2970 Hørsholm ___ European Dedicated Server Hosting Extremely low prices, secure, and reliable Linux distributions only ___ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
question about pxeboot.
hey folks.. hope yall dont mind 2 questions in the same day.. ;) trying to set up pxe server on my freebsd box. I have installed isc-dhcp3-3.0.1.r11_1 (from ports) the default tftp server in inetd.conf pxe-1.3 (from ports) im pxe client is an ibm t30 laptop and when I tell it to boot pxe, it gets a dhcp address.. It appears to tftp download the pxeboot file (which is a big ole linux initrd created with http://pxes.sourceforge.net) then after a short while it bombs with tftp: too many packages exiting intel boot agent I searched and it seems that there is a 512K limitation for booting images? The only option that Ive found is using http://syslinux.zytor.com/pxe.php does this sound about right? regards, Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
